/docs/modules/embed-api
Embed & API
One inventory source for your website, partners, and automation — with honest scope boundaries.
Purpose
FlashFender exposes read-mostly inventory and desk data through embed widgets and authenticated API keys so your marketing site and tools stay in sync with the lot — without duplicate spreadsheets.
Setup
- Settings → Website — copy embed snippet, allowed domains, and preview.
- Settings → API keys — create scoped keys (read inventory, leads webhook, etc.).
- Settings → Integrations — optional OAuth/partner hooks as they ship.
- Read the in-app embed reference for live examples: app.flashfender.com/embed/docs.
Daily workflow
- Website — paste embed on dealer site or landing pages; verify VDP links resolve.
- Lead capture — embed forms POST into CRM when configured (see Website embed).
- Partners — rotate API keys on staff change; never commit keys to git.
- Monitoring — check audit logs for failed webhook deliveries (Settings → Audit).
Key surfaces
| Surface | Use |
|---|---|
| Inventory embed | Live grid/VDP on your site |
| JSON-LD helper | AI/search-friendly vehicle markup (Vehicle JSON-LD) |
| Open API | CRUD within key scope (Open API) |
| Webhooks | Push events to your endpoint |
| Embed docs (in app) | Interactive field reference at /embed/docs |
Permissions
- Admin — create/revoke API keys and set allowed origins.
- Website vendor — receive read-only key scoped to inventory only.
- Developers — use separate keys per environment (prod vs staging).
Canadian notes
- Price shown on embed should match Active inventory asking price — regulatory advertising is your responsibility.
- Do not expose customer PII through public embed endpoints.
- BC/Ontario disclosure text on VDPs should match in-app inventory notes (Compliance).