AM
Fictional demo data · Apex Motors

Apex Motors

Installation center

Connect lead sources, verify intake and clear go-live blockers.

Fictional demo examples. No real endpoints exist and no secrets are shown. Sign in to a dealership workspace to connect a real lead source.

Readiness

64%9 of 14 required checks passed · 5 open
  • Integration not tested — run an isolated test intake
  • Endpoint configured, not yet proven — no live lead received yet (test intakes do not count)
  • 3 required checklist items incomplete

Recommended, not blocking basic email

  • • Scheduler not configured — due emails send only when processed manually
  • • Delivery webhook not configured — sent emails are not updated to delivered/bounced (sending still works)
  • • Reply capture not configured — replies go to the reply-to inbox and do not cancel follow-ups automatically

Implementation checklist

Lead intake endpoints

Configured, not yet proven

/api/public/intake/<endpoint-public-id>

Live OK: neverTest OK: neverAccepted 1 · Dup 1Rejected 1 · Test 1

Connection guide · Apex website form (demo)

curl -X POST '/api/public/intake/<endpoint-public-id>' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <ENDPOINT_SECRET>' \
  -H 'Idempotency-Key: <unique-submission-id>' \
  -d '{"external_lead_id":"web-10421","first_name":"Jane","last_name":"Doe","email":"jane@example.com","message":"Is this car available?","vehicle_external_ref":"STOCK-123"}'

Example canonical body:

{
  "external_lead_id": "web-10421",
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "jane@example.com",
  "message": "Is this car available?",
  "vehicle_external_ref": "STOCK-123"
}

Secrets must never be placed in browser JavaScript or public website code. Browser forms should post to the dealership’s own server or automation tool, which forwards to REVDRIVE.

Responses: 201 accepted · 200 duplicate · 401 bad secret · 403 disabled · 413 too large · 415 not JSON · 422 invalid fields · 429 rate limited (Retry-After). IP allowlisting uses the edge-provided client IP only.

Mapping preview & isolated test · Apex website form (demo)

Validate runs the endpoint’s mapping and checks without saving anything. Isolated test intake stores a TEST-tagged lead through the real path — it never enrolls automation. No email will be sent.

Admins and managers can run tests.

Canonical fields

FieldTypeRequiredNotes
external_lead_idstringRecommendedYour system’s lead ID — repeats never create duplicates
first_namestringOptionalMax 100 chars
last_namestringOptionalMax 100 chars
namestringOptionalFull name, split when first/last are missing
emailstringEmail or phone requiredLower-cased and trimmed
phonestringEmail or phone requiredDigits, spaces, + ( ) - . only; country is not guessed
messagestringOptionalMax 5000 chars
sourcestringOptionalLead source name, e.g. Website
vehicle_external_refstringOptionalLinks to inventory only if that stock ref exists
vehicle_makestringOptional
vehicle_modelstringOptional
vehicle_variantstringOptional
vehicle_yearnumberOptional1950 – next year
finance_interestbooleanOptional
consent_statusopted_in | unknown | opted_outOptionalDefaults to unknown; opted_out never gets automated follow-ups
preferred_contactemail | phone | sms | whatsapp | unknownOptional
metadataobjectOptionalSafe extras, max 4 KB and 3 levels deep

At least one of email or phone is required. Idempotency-Key header and external_lead_id each prevent duplicate leads and duplicate follow-ups.

Outbound email

Fictional demo sender, sequence and deliveries. No provider is contacted in demo mode.

Sender identities

Apex Motors Sales

sales@apexmotors.example · resend

verified

Replies: set to REVDRIVE, but reply capture is not live — falls back to the direct reply-to

Fictional demo sender — domain shown as verified for illustration · checked 20 Sept, 08:00

Basic outbound email readiness

  • Outbound email ready — verified sender and active sequence

Recommended for closed-loop automation

  • • Scheduler not configured — due emails send only when processed manually
  • • Delivery webhook not configured — sent emails are not updated to delivered/bounced (sending still works)
  • • Reply capture not configured — replies go to the reply-to inbox and do not cancel follow-ups automatically

Provider key

Present

Scheduled sending

Not configured

Delivery webhook

Not configured

Reply capture

Not configured

Scheduler last successful run: never

Delivery webhook last event: none received yet

Receiving domain: not set · Current reply behaviour: replies go to the direct reply-to inbox (not visible to REVDRIVE)

Email queue

Pending

1

Blocked

1

Sent

1

Failed

0

Cancelled

1

Last send attempt

20 Sept, 09:15

Process due emails

Verified outbound email is connected. Due jobs send only when processed manually until the scheduler is live. Stop conditions are re-checked before every send.

Due now: 2 · Scheduled sending: Not configured

Send a test email

Only test leads (created with “Send test lead”) can be chosen. The email goes to that lead's stored address through the same queue.

How to connect Resend
  1. Create a Resend account and an API key with sending access.
  2. Add it as the server secret RESEND_API_KEY (never in the browser).
  3. Add and verify the dealership's sending domain in the Resend dashboard (DNS records).
  4. Add the sender here with an address on that domain, then press “Check verification”.
  5. Create templates and an active new-lead sequence on the Automation page.

Recent inbound events

ReceivedEndpointKeyStatusDetails
20 Sept, 09:14Apex website form (demo)web-1042
processed
—
20 Sept, 09:16Apex website form (demo)web-1042
duplicate
—
19 Sept, 16:40TESTApex website form (demo)—
rejected
payload: email or phone is required

Integration health

Apex website form (demo)

lead source · last activity 20 Sept, 09:14

connected
CRM

crm · no activity recorded

not connected
Email

email · no activity recorded

not connected

Status reflects stored records only. Nothing is shown as connected unless it has actually been configured or received data.