Automate the whole pipeline.
Find and verify contacts, manage campaigns and leads, control mailboxes, and read the inbox through the API and the CLI, with your personal access key.
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" }] }
Terminal
$
leadvector leads search --title "Head of Sales" --location "United States" --industry software --verified
Searching 1,240 companies 247 contacts found · 231 verified
$
leadvector campaigns add-leads "Founder Outreach" --from last-search
Added 231 leads · 2 mailboxes · first step scheduled Mon 09:00
How it works
1
Create an access key
Each team member creates their own key, with usage analytics for it, and sends it as the x-api-key header. Rate limits apply per key and per route.
2
Call the same endpoints the app uses
Data, campaigns, leads, mailboxes, and inbox under /v1. Or use the CLI for the same actions.
3
Automate
Enrich on signup, launch campaigns from your CRM, sync replies back. Credits come from your account.
Same endpoints as the app.
There is no reduced API. Data, campaigns, leads, mailboxes, and inbox are all under /v1 with the same behaviour as the interface.
find-email, find-mobile, verify-email, reverse-email-lookup
Campaign, sequence, and lead management
Email account control and inbox read, update, forward
https://api.leadvector.app/v1
POST
GET · POST
GET · POST
GET · PATCH
GET · PATCH · POST
Header
Terminal
$
leadvector leads verify --list "UK Seed Founders"
214 checked · 203 valid · 8 catch-all · 3 invalid
Scriptable from the terminal.
The CLI wraps the API with structured output and exit codes, so it fits shell scripts, cron, and CI.
Same access key as the API
Structured output for piping
Per-key rate limits, shared credits
Works with
Questions
Common questions from GTM engineers.
Is there anything the API cannot do?
The public /v1 API covers data, campaigns, leads, mailboxes, and inbox. Bulk file jobs and account administration stay in the app.
How are rate limits applied?
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.
Do API calls use the same credits?
Yes. The API and the CLI draw from the same credit pool as the app.