Receiving leads

Messages reach Leadveyor through sources. Every workspace has an API source; add email and form sources to receive leads without writing code. Each source can use its own profile.

Through the API

Send any message with POST /v1/inbounds. Give it free text, an email, or form fields exactly as you received them — no mapping needed.

curl -X POST https://core.leadveyor.com/v1/inbounds \
  -H "Authorization: Bearer lv_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "fields": { "name": "Tom Baker", "email": "tom@example.com", "message": "Bathroom renovation in Queens, budget 15k" },
    "externalId": "form-submission-48213",
    "metadata": { "crmId": "C-1029" }
  }'
  • The message is queued and processed in the background; the response (202) has the inbound's id and status. Add ?wait=true to wait up to 30 seconds for the result.
  • externalId makes sending idempotent: the same ID returns the same inbound instead of processing it twice.
  • metadata is copied to the leads — use it to keep your own IDs.
  • Failed AI calls are retried automatically (5 attempts). The final error is on the inbound.
  • A message wrongly marked as junk can be processed again: POST /v1/inbounds/{id}/reprocess with { "notJunk": true }.

Email

Create an email source and Leadveyor gives you an address. Forward your enquiries to it — from Gmail, Outlook or any mailbox — and every email is processed.

curl -X POST https://core.leadveyor.com/v1/sources \
  -H "Authorization: Bearer lv_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "type": "email", "name": "Website enquiries" }'

Response (shortened)

{ "object": "source", "id": "src_4Hd8Kq2Lm7Xp1Vz9Rt3Bc6Nw", "type": "email",
  "config": { "address": "acme-renovations-k3x9qp@in.leadveyor.com" } }
  • Forwarded emails are understood: the customer is the original sender inside the forwarded message, not the person who forwarded it.
  • When Gmail asks to confirm a forwarding address, the confirmation email shows up on the source so you can click the link.
  • The same email is never processed twice.

Web forms

Create a form source and post your forms to its URL. It needs no API key and accepts JSON, classic HTML forms, and Unbounce webhooks.

curl -X POST https://core.leadveyor.com/v1/sources \
  -H "Authorization: Bearer lv_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "type": "form", "name": "Contact form", "redirectUrl": "https://acme.example/thanks" }'

Response (shortened)

{ "object": "source", "id": "src_7Lm2Qx9Kd4Wz1Vt8Rc3Nb6H", "type": "form",
  "config": { "url": "https://core.leadveyor.com/f/frm_9Kx2Lq7Vt4Wz8Nb3Pc6Rd1Hm5Jy0Gs", "redirectUrl": "https://acme.example/thanks" } }

A plain HTML form only needs the URL as its action. Field names can be anything:

<form action="https://core.leadveyor.com/f/frm_9Kx2Lq7Vt4Wz8Nb3Pc6Rd1Hm5Jy0Gs" method="POST">
  <input name="name" placeholder="Your name" />
  <input name="email" type="email" placeholder="Email" />
  <textarea name="message"></textarea>
  <!-- Spam trap: hidden from people, filled in by bots -->
  <input name="_hp" style="display:none" tabindex="-1" autocomplete="off" />
  <button type="submit">Send</button>
</form>
  • After a classic form submit the visitor is redirected to redirectUrl. JavaScript fetch calls (any origin) get a JSON response instead.
  • Submissions with the _hp field filled in are bots: they are accepted silently and dropped.
  • Each form accepts up to 120 submissions a minute.
  • For Unbounce, paste the URL as the page's webhook — its data.json format is unpacked automatically.

Choosing a profile

A message is scored with the first profile set on: the request (profileId), its source, or the workspace default. Pause an email or form source with PATCH /v1/sources/{id} and { "status": "paused" } — it refuses new messages until you set it back to active.

Was this page helpful?