// tomba cli
Email intelligence from your terminal
Search domains, find emails, verify addresses, and enrich contacts: all without leaving your terminal. Install in one command. Works on macOS, Linux, and Windows.
$ tomba verify --target richard@piedpiper.com --json
{
"data": {
"email": {
"email": "richard@piedpiper.com",
"result": "deliverable",
"status": "valid",
"score": 99
}
}
}// 01 · install
One binary for macOS, Linux and Windows
The install scripts check the release's SHA-256 checksum and set up shell completion. Releases are on GitHub.
curl -sSL https://releases.tomba.io/install.sh | shbrew install --cask tomba-io/tap/tombairm https://releases.tomba.io/install.ps1 | iexscoop bucket add tomba https://github.com/tomba-io/scoop-bucket.git
scoop install tombasudo snap install tomba// 02 · commands
Every endpoint from the terminal
Pass the input with --target; add --json, --yaml or --csv for machine-readable output and --output to write a file.
tomba searchEmail addresses Tomba has for a domain
GET /v1/domain-searchtomba finderA person's email from their name and company domain
GET /v1/email-findertomba authorThe email of an article's author
GET /v1/author-findertomba enrichThe person behind an email address
GET /v1/enrichtomba enrichment personA person profile from an email
GET /v1/people/findtomba enrichment companyA company profile from a domain
GET /v1/companies/findtomba enrichment combinedPerson and company in one request
GET /v1/combined/findtomba verifyWhether an email address is deliverable
GET /v1/email-verifiertomba linkedinThe email for a LinkedIn profile
GET /v1/linkedintomba sourcesThe public pages where an address was found
GET /v1/email-sourcestomba countAddresses for a domain, by department and seniority
GET /v1/email-counttomba statusWhether a domain is webmail or disposable
GET /v1/domain-statustomba formatThe address patterns a domain uses
GET /v1/email-formattomba locationA company's employee counts by location
GET /v1/locationtomba autocompleteCompanies and domains from part of a name
GET /v1/domain-suggestionstomba phone-finderPhone numbers from an email, domain or LinkedIn profile
GET /v1/phone-findertomba phone-validatorWhether a phone number is valid, its formats and carrier
GET /v1/phone-validatortomba revealCompanies from a natural-language query or filters
POST /v1/reveal/searchtomba similarCompanies similar to a domain
GET /v1/similartomba technologyThe technologies on a domain's website
GET /v1/technologytomba lead · leads-list · attributeManage leads, lead lists and custom attributes
/v1/leads, /v1/leads_lists, /v1/attributestomba flag create · listReport wrong data and list your reports
POST /v1/flag, GET /v1/flagtomba key list · get · create · deleteManage your workspace's API keys
/v1/keystomba whoami · usage · logsYour account, daily usage and recent requests
GET /v1/me, /v1/usage, /v1/logs
| Command | Returns | Calls |
|---|---|---|
| tomba search | Email addresses Tomba has for a domain | GET /v1/domain-search |
| tomba finder | A person's email from their name and company domain | GET /v1/email-finder |
| tomba author | The email of an article's author | GET /v1/author-finder |
| tomba enrich | The person behind an email address | GET /v1/enrich |
| tomba enrichment person | A person profile from an email | GET /v1/people/find |
| tomba enrichment company | A company profile from a domain | GET /v1/companies/find |
| tomba enrichment combined | Person and company in one request | GET /v1/combined/find |
| tomba verify | Whether an email address is deliverable | GET /v1/email-verifier |
| tomba linkedin | The email for a LinkedIn profile | GET /v1/linkedin |
| tomba sources | The public pages where an address was found | GET /v1/email-sources |
| tomba count | Addresses for a domain, by department and seniority | GET /v1/email-count |
| tomba status | Whether a domain is webmail or disposable | GET /v1/domain-status |
| tomba format | The address patterns a domain uses | GET /v1/email-format |
| tomba location | A company's employee counts by location | GET /v1/location |
| tomba autocomplete | Companies and domains from part of a name | GET /v1/domain-suggestions |
| tomba phone-finder | Phone numbers from an email, domain or LinkedIn profile | GET /v1/phone-finder |
| tomba phone-validator | Whether a phone number is valid, its formats and carrier | GET /v1/phone-validator |
| tomba reveal | Companies from a natural-language query or filters | POST /v1/reveal/search |
| tomba similar | Companies similar to a domain | GET /v1/similar |
| tomba technology | The technologies on a domain's website | GET /v1/technology |
| tomba lead · leads-list · attribute | Manage leads, lead lists and custom attributes | /v1/leads, /v1/leads_lists, /v1/attributes |
| tomba flag create · list | Report wrong data and list your reports | POST /v1/flag, GET /v1/flag |
| tomba key list · get · create · delete | Manage your workspace's API keys | /v1/keys |
| tomba whoami · usage · logs | Your account, daily usage and recent requests | GET /v1/me, /v1/usage, /v1/logs |
// 03 · bulk
Process a CSV from your machine
tomba bulk sends one API request per row and writes the results to a new CSV as rows complete. Each row is billed and rate-limited like a single request; for server-side jobs, use the Bulk API.
# One API request per row, from your machine
tomba bulk --file leads.csv --type verify --column "Email Address"
tomba bulk --file prospects.csv --type finder --domain-col company_domain --first-col first --last-col last
tomba bulk --file domains.csv --type search --domain-col domain --output domain-search.csv- tomba bulk
- Runs on your machine, one request per row, each billed like a single call
- POST /v1/bulk/{type}
- Runs on Tomba's servers as one job, billed at the first download
// 04 · sign in
Browser sign-in or an API key
tomba login uses the OAuth 2.0 device flow, so it works over SSH; for scripts, sign in with a key. Credentials are saved in ~/.tomba.json.
tomba logintomba login --api-key
tomba whoamitomba verify --target richard@piedpiper.com --key "$TOMBA_API_KEY" --secret "$TOMBA_SECRET_KEY"--json, --yaml, or --csv flags for machine-readable output. Pipe to jq for filtering, redirect to files, or use in shell scripts, cron jobs, and CI/CD pipelines.