A REST API for your stock and webhooks for your leads
List vehicles on your own website, build apps on top of your CRM data and receive every lead and order event where you want it. Stock is sourced from Wayke for Sweden and Drive for Norway.
$ curl https://api.dealercrm.se/v1/vehicles?branch=gbg-1 \ -H "Authorization: Bearer sk_live_…" { "data": [{ "id": "veh_4d21", "registration": "ABC123", "make": "Volvo", "model": "XC60", "year": 2022, "mileage_km": 31200, "price": { "amount": 449900, "currency": "SEK" }, "images": ["https://cdn.dealercrm.se/…"], "source": "wayke" }], "next_cursor": "eyJvZmZzZXQiOjUwfQ" }
Vehicle API
Your inventory with photos, specs, equipment and prices. Filter by branch, make, fuel or price. Cursor pagination, ETags, JSON.
Webhooks
Lead, order and vehicle events pushed to your HTTPS endpoint. HMAC-SHA256 signed, retried with backoff for 24 hours.
Leads API
Create leads from your own forms, read and update status, assign owners, add comments. Same model as the app.
Three ways to connect DealerCRM to what you already run
Most dealers use one or two of these. All of them work with the same API keys and the same vehicle, lead and order models you see in the app.
Show your stock on your own website
Your website or agency fetches vehicles from DealerCRM instead of maintaining a separate feed. Photos, specs, equipment and prices come from the same source as your marketplace listings: Wayke in Sweden, Drive in Norway. Filter by branch, make, fuel or price, and cache with ETags so pages stay fast.
- JSON over HTTPS, cursor pagination
- Read-only keys per website or agency
- Drop-in listing components if you prefer not to code
GET /vehicles?branch=gbg-1&fuel=electric Authorization: Bearer <read key> → 200 OK · ETag: "a81f…" { "data": [ { "registration": "ABC123", … } ], "next_cursor": "…" }
POST https://your-system.example/dealercrm
DealerCRM-Signature: sha256=…
{ "type": "lead.created",
"data": { "source": "finn", "type": "test_drive",
"vehicle": { "registration": "EL48211" },
"customer": { "name": "Ole K. Berg" } } }
Get every lead and order where you want it
Register an HTTPS endpoint and pick the events you care about: new leads, status changes, messages, online orders, signed contracts. Each delivery is signed so you can verify it came from us, and retried with backoff for 24 hours until you answer 2xx. Typical uses are a DMS, a BI tool or a group-level CRM.
- HMAC-SHA256 signature on every delivery
- Delivery log and replay from the app
- Separate endpoints per branch or per system
Send leads in from your own forms and partners
A contact form on your site, a campaign landing page or a partner marketplace can create leads directly. They land in the same inbox, follow the same routing rules and count in the same reports as everything else. Marketplaces and lead providers integrate the same way, with their own keys.
- Match to a vehicle by registration number or your own ID
- Idempotency keys so retries never create duplicates
- Consent and source recorded on every lead
POST /leads
Idempotency-Key: form-7f21
{ "type": "contact", "source": "website",
"vehicle": { "registration": "ABC123" },
"customer": { "name": "Maria Lindqvist",
"phone": "+46701234567" },
"consent": true }
Full reference and sandbox for customers and partners
The complete API reference, sandbox keys with sample stock and a webhook inspector are provided when you become a customer or integration partner. Tell us what you are building and we will set you up.
Sweden via Wayke, Norway via Drive. One normalised vehicle model regardless of market.
Scoped keys per integration, TLS only, signed webhooks, audit log on every write.
Uptime and incidents at status.dealercrm.se.