Build LeadVector into your own workflows.
A REST API at api.leadvector.app/v1, authenticated with your personal access key. Find, verify, and look up contacts, manage campaigns and leads, control mailboxes, and read the inbox.
POST /v1/find-email
cURL
curl -X POST https://api.leadvector.app/v1/find-email \ -H "x-api-key: $LEADVECTOR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "fullName": "Emily Turner", "domain": "lumenanalytics.com" }'
Response · 200 OK
{ "success": true, "message": "EMAIL_RESULT", "data": [{ "uuid": "3f6d2c1e-8b7a-4f0e-9c2d-1a5b7e9f4c21", "email": "emily@lumenanalytics.com", "firstName": "Emily", "lastName": "Turner", "domain": "lumenanalytics.com", "emailStatus": "valid" }] }
https://api.leadvector.app/v1
POST
/find-email · /find-mobile · /verify-email · /reverse-email-lookup
GET · POST
/campaigns · /campaigns/:uuid/sequences
GET · POST
/leads/:uuid · /leads/:uuid/manual
GET · PATCH
/email-accounts · /email-accounts/:id/pause · /resume
GET · PATCH · POST
/inbox · /inbox/:id · /inbox/messages/:id/forward
Header
x-api-key
How it works
Create an access key
Each user creates one access key in their account and can see usage analytics for it. The key is shown once; send it as the x-api-key header on every request.
Call the same endpoints the app uses
Data, campaigns, leads, mailboxes, and inbox, all under /v1.
Stay inside your limits
Per-key, per-route rate limits with standard rate-limit headers. Credits come from your account.
Data endpoints.
Email finding, mobile finding, verification, and reverse lookup behave exactly as they do in the app: results are found in real time across multiple providers, verified, saved to the contact, and only charged when valid.
find-email, find-mobile, verify-email, reverse-email-lookup
Credits only on valid results
Verification cached for 30 days
POST /v1/verify-email
cURL
curl -X POST https://api.leadvector.app/v1/verify-email \ -H "x-api-key: $LEADVECTOR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "email": "emily@lumenanalytics.com" }'
Response · 200 OK
{ "success": true, "message": "EMAIL_VERIFIED", "data": { "email": "emily@lumenanalytics.com", "status": "valid", "mxFound": true, "mxRecord": "aspmx.l.google.com", "provider": "leadvector" } }
https://api.leadvector.app/v1
POST
/find-email · /find-mobile · /verify-email · /reverse-email-lookup
GET · POST
/campaigns · /campaigns/:uuid/sequences
GET · POST
/leads/:uuid · /leads/:uuid/manual
GET · PATCH
/email-accounts · /email-accounts/:id/pause · /resume
GET · PATCH · POST
/inbox · /inbox/:id · /inbox/messages/:id/forward
Header
x-api-key
Campaign and inbox endpoints.
Everything a campaign needs, from creation to leads to sequences, and everything a reply needs, from listing to forwarding.
Create, update, and archive campaigns and manage sequences
Add and upsert leads with custom variables
List, read, update, sync, and forward inbox conversations
Questions
Common questions about the API.
Create your access key in your account settings and send it as the x-api-key header. Each user has one key, with usage analytics in the app. The raw key is shown only once, so store it safely.
Yes. Data lookups allow 5 requests per second per key, with bursts of up to 20; campaign, lead, inbox, and mailbox endpoints allow 120 requests per minute per key; and an account is capped at 10 requests per second across all its keys. Every response carries rate-limit headers so you can back off cleanly.
Yes. API calls draw from the same credit pool as the app, including your team's shared pool.
