Operate LeadVector from the terminal.
Search, verify, build lists, and manage campaigns and mailboxes from the command line, on the same account and credits as the app.
Terminal
$
leadvector leads search --title "Head of Growth" --location "United States" --size 20-100 --verified
1,240 companies matched 247 verified contacts
$
leadvector campaigns add-leads "Founder Outreach" --from last-search
Added 247 leads · 2 mailboxes · first step scheduled Mon 09:00
How it works
1
Install and sign in
Authenticate once with your account. The CLI uses the same access key as the API.
2
Run the same actions as the app
Find and verify contacts, manage lists, launch and pause campaigns, check mailbox health.
3
Script it
Pipe results into your own tooling, schedule jobs, or wire LeadVector into CI.
Every action, scriptable.
Anything you can do in the app has a command. Output is structured so it can be piped, filtered, and stored.
Contacts: search, find, verify, reverse lookup
Lists and campaigns: create, add leads, launch, pause, resume
Mailboxes: list, pause, resume, health
Terminal
$
leadvector email-accounts list --status active
maya@northstar.io Warmup active 98 alex@northstar.io Warmup active 94
How it connects
Auth
Access key
Base URL
https://api.leadvector.app/v1
Rate limit
Per key, per route
Credits
Shared with your team
One account, one set of credits.
The CLI is a client of the public API. Rate limits, credits, and team access all work exactly the same way.
Same access key as the API
Per-key, per-route rate limits
Credits shared with your team
Questions
Common questions about the CLI.
Do I need a separate account for the CLI?
No. Sign in with your LeadVector account. The CLI uses the same access key as the API and draws from the same credits.
Can I use it in scripts and CI?
Yes. Commands return structured output and exit codes, so they work in shell scripts, cron jobs, and CI pipelines.
Where is the reference?
The documentation lists every command and flag.