TombaTomba
Start free
  • Documentation
  • API reference
  • SDKs & CLI
  • AI & MCP
  • Integrations
  • Enterprise
  • Migration guides

Find, verify and enrich B2B contacts from public sources, in the app, your spreadsheet or through the API.

GDPR & CCPA

// docs

  • API changelog
  • Support options
  • Security

// platform

  • Dashboard
  • Pricing
  • API status

// resources

  • Help center
  • Product updates
  • TombaBot crawler

// company

  • Website
  • Contact us
  • Edit or remove your data

© 2021–2026 Tomba.io

  • Terms of service
  • Privacy policy
  • Cookie policy
  • Security policy
  • GDPR
  • CCPA
Information
Finder
    Domain SearchgetEmail FindergetEmail CountgetEmail FormatgetLocationgetAuthor FindergetLinkedin FindergetEmail Enrichmentget
Verifier
Enrichment
Phone
Domain
Email
Domain Suggestions
Reveal
Bulks
Scrape Campaigns
Leads
Lead Lists
Lead Attributes
Account
Keys
Flag
MCP Server
Schemas
Tomba
Tomba

Finder

Download schema

Find email addresses by domain, name, article, or LinkedIn profile, and enrich them


Domain Search

GET
https://api.tomba.io/v1
/domain-search
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Returns the company behind a domain and one page of the email addresses Tomba has for it, with each person's name, job title, department, and verification status.

A domain with no known addresses, and a disposable or webmail domain such as gmail.com, returns 200 with an empty data.emails array. The credit cost depends on limit, not on the number of addresses returned; see Credits and usage.

Domain Search › query Parameters

domain
​string

Company domain, such as stripe.com. Send domain or company.

company
​string · minLength: 3 · maxLength: 75

Company name, such as Stripe. When Tomba knows the company, its domain is searched, even if you also send domain. An unknown company fails with 422 unless you also send domain.

page
​integer

Page number, starting at 1. On the Free plan outside a workspace, every request returns page 1.

Default: 1
limit
​integer · enum

Number of addresses per page. On the Free plan outside a workspace, a value above 10 fails with 400.

Enum values:
1
5
10
20
50
100
150
200
Default: 10
country
​string · minLength: 2 · maxLength: 2

Two-letter country code (ISO 3166-1 alpha-2), such as US, to return only people in that country. GET /location lists the countries that have addresses.

department
​string

Return only people in these departments. Separate several with commas, such as engineering,sales. Values: accounting, administrative, communication, diversity, education, engineering, executive, facilities, finance, healthcare, hr, it, legal, management, marketing, operations, pr, sales, security, software, support, warehouse. Unknown values are ignored.

type
​string · enum

personal returns only addresses that belong to one person, generic only role addresses such as support@.

Enum values:
all
personal
generic
Default: all
enrich_mobile
​boolean

Set to true to also get each person's phone numbers in phone_data. Phone numbers cost extra credits; see Credits and usage.

Default: false
webhook_url
​string · uri

Optional URL that also receives the result in a POST request when the result qualifies. The response body is returned either way. See Webhooks.

Domain Search › Responses

The company and one page of its email addresses.

Domain search response: the company in `data.organization`, one page of its email addresses in `data.emails`, and paging in `meta`. See [Company response](https://docs.tomba.io/attributes/company) and [Person response](https://docs.tomba.io/attributes/person).
DomainSearch
​object · required

The company and its email addresses.

​object · required

Paging for the email addresses, and the request as the API read it.

GET/domain-search
curl https://api.tomba.io/v1/domain-search \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "organization": { "website_url": "stripe.com", "organization": "Stripe", "location": { "country": "US", "city": "South San Francisco", "state": "California", "street_address": "354 Oyster Point Blvd", "postal_code": "94080" }, "social_links": { "twitter_url": "https://twitter.com/stripe", "facebook_url": "https://www.facebook.com/StripeHQ", "linkedin_url": "https://www.linkedin.com/company/stripe", "instagram_url": null, "github_url": "https://www.github.com/stripe", "youtube_url": null, "pinterest_url": null, "tiktok_url": null }, "disposable": false, "webmail": false, "phone_number": true, "industries": "financial services", "founded": "2010", "company_size": "5K-10K", "company_type": "private", "revenue": "$1B-$10B", "accept_all": false, "description": "Stripe is a financial infrastructure platform for businesses.", "pattern": "{first}.{last}", "total_similar": 25, "keywords": [ "payments", "billing", "fintech" ], "ranking": 310, "whois": { "registrar_name": "SafeNames Ltd.", "created_date": "1995-09-12T04:00:00Z", "referral_url": "http://www.safenames.net" }, "last_updated": "2025-04-03T13:23:24+02:00" }, "emails": [ { "email": "jane.doe@stripe.com", "first_name": "Jane", "last_name": "Doe", "full_name": "Jane Doe", "gender": "female", "phone_number": false, "type": "personal", "country": "US", "position": "Software Engineer", "department": "engineering", "seniority": "senior", "twitter": null, "linkedin": "https://www.linkedin.com/in/jane-doe", "score": 100, "verification": { "date": "2025-01-15T10:32:00+01:00", "status": "valid" }, "phone_data": [], "sources": [ { "uri": "https://stripe.com/blog/engineering", "website_url": "stripe.com", "extracted_on": "2024-06-01T09:14:07+01:00", "last_seen_on": "2025-01-10T17:02:44+01:00", "still_on_page": true } ] }, { "email": "john.smith@stripe.com", "first_name": "John", "last_name": "Smith", "full_name": "John Smith", "gender": "male", "phone_number": false, "type": "personal", "country": "US", "position": "Product Manager", "department": "management", "seniority": null, "twitter": null, "linkedin": null, "score": 76, "verification": { "date": "2024-11-02T15:04:31+01:00", "status": "accept_all" }, "phone_data": [], "sources": [ { "uri": "https://stripe.com/newsroom", "website_url": "stripe.com", "extracted_on": "2024-05-15T08:00:00+01:00", "last_seen_on": "2025-01-08T12:30:00+01:00", "still_on_page": true } ] } ] }, "meta": { "total": 1250, "pageSize": 10, "current": 1, "total_pages": 125, "params": { "domain": "stripe.com", "company": "", "page": 1, "limit": 10, "department": null, "country": null, "type": "all", "live": false, "enrich_mobile": false, "webhook_url": null } } }
json
application/json

Email Finder

GET
https://api.tomba.io/v1
/email-finder
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Finds a person's professional email address from their name and their company's domain or name. Tomba returns a stored address when it has one; otherwise it generates candidate addresses and checks them against the company's mail servers.

When no address is found, the response is still 200 and data.email is null. A disposable or webmail domain, such as gmail.com, fails with 400 and type unknown_record. See Credits and usage for when a request is charged.

Email Finder › query Parameters

domain
​string

Company domain, such as stripe.com. Send domain or company; when you send both, domain is used. A link shortener or bio-link domain, such as bit.ly, is rejected with 422 unless you also send company.

company
​string · minLength: 3 · maxLength: 75

Company name, such as Stripe. Send domain or company. A domain gives better results.

first_name
​string · minLength: 1 · maxLength: 40

The person's first name. Send first_name and last_name, or full_name.

last_name
​string · minLength: 1 · maxLength: 40

The person's last name.

full_name
​string · minLength: 5 · maxLength: 80

The person's full name, used when first_name and last_name aren't both sent. The request fails with 422 when no name can be read from the name parameters.

enrich_mobile
​boolean

Set to true to also get the person's phone numbers in data.phone_data. Phone numbers cost extra credits; see Credits and usage.

Default: false
webhook_url
​string · uri

Optional URL that also receives the result in a POST request when the result qualifies. The response body is returned either way. See Webhooks.

Email Finder › Responses

The person's address, or data.email null when none is found.

Email finder and email enrichment response. When no address is found, `data.email` is `null`, the other fields are `null`, `false`, or `0`, `sources` is `null`, and `verification` is left out. See [Person response](https://docs.tomba.io/attributes/person).
EmailFinder
​object · required

The person and their email address.

GET/email-finder
curl https://api.tomba.io/v1/email-finder \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "email": "jane.doe@stripe.com", "first_name": "Jane", "last_name": "Doe", "full_name": "Jane Doe", "website_url": "stripe.com", "company": "Stripe", "pattern": "{first}.{last}", "department": "engineering", "type": "personal", "position": "Software Engineer", "country": "US", "gender": "female", "twitter": null, "linkedin": "https://www.linkedin.com/in/jane-doe", "score": 100, "accept_all": false, "phone_number": false, "verification": { "date": "2025-01-15T10:32:00+01:00", "status": "valid" }, "sources": [ { "uri": "https://stripe.com/blog/engineering", "website_url": "stripe.com", "extracted_on": "2024-06-01T09:14:07+01:00", "last_seen_on": "2025-01-10T17:02:44+01:00", "still_on_page": true } ], "phone_data": [] } }
json
application/json

Email Count

GET
https://api.tomba.io/v1
/email-count
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Returns how many email addresses Tomba has for a domain, by email type, department, and seniority. Use it to size a domain before a domain search. An unknown, webmail, or disposable domain returns 0 in every count.

This endpoint uses the email count balance, and every successful call is charged; when the balance is used up it returns 429. See Credits and usage.

Email Count › query Parameters

domain
​string · required

Company domain, such as stripe.com.

type
​string · enum

Count only personal or only generic addresses in total and in the department and seniority counts. personal_emails and generic_emails are always returned.

Enum values:
all
personal
generic
Default: all

Email Count › Responses

The counts for the domain.

How many email addresses Tomba has for a domain, by email type, department, and seniority. An unknown, webmail, or disposable domain returns `0` in every count. See [Email count response](https://docs.tomba.io/attributes/email-count).
EmailCount
​object · required

The counts.

website_id
​integer · required

Tomba's internal ID for the domain's company record. 0 when Tomba has no record of the domain.

GET/email-count
curl 'https://api.tomba.io/v1/email-count?domain=stripe.com' \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "total": 1250, "personal_emails": 1100, "generic_emails": 150, "department": { "engineering": 410, "finance": 35, "hr": 22, "it": 18, "marketing": 64, "operations": 51, "management": 88, "sales": 120, "legal": 12, "support": 47, "communication": 9, "executive": 15, "accounting": 6, "administrative": 4, "diversity": 0, "facilities": 2, "pr": 5, "security": 14, "software": 30, "warehouse": 0, "healthcare": 0, "education": 1 }, "seniority": { "junior": 180, "senior": 420, "executive": 37 } }, "website_id": 1024 }
json
application/json

Email Format

GET
https://api.tomba.io/v1
/email-format
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Returns the formats that a domain's email addresses follow, such as {first}.{last}, with the share of known addresses that use each one. data is an empty array when Tomba has no formats for the domain.

This endpoint uses the email count balance, and every successful call is charged, including one with an empty result; when the balance is used up it returns 429. See Credits and usage.

Email Format › query Parameters

domain
​string · required

Company domain, such as stripe.com.

Email Format › Responses

The domain's email formats.

The formats that a domain's email addresses follow, with the share of known addresses that use each one. See [Email format response](https://docs.tomba.io/attributes/format).
EmailFormat
​object[] · required

Up to 20 formats, in no particular order. An empty array when Tomba has no formats for the domain.

GET/email-format
curl 'https://api.tomba.io/v1/email-format?domain=stripe.com' \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": [ { "format": "{first}.{last}", "percentage": 66 }, { "format": "{first}", "percentage": 34 } ] }
json
application/json

Location

GET
https://api.tomba.io/v1
/location
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Returns, for each country, how many of a domain's email addresses belong to people in that country. To list the addresses for one country, pass its code to domain search in country. data is an empty array when Tomba has no location data for the domain.

This endpoint uses the email count balance, and every successful call is charged, including one with an empty result; when the balance is used up it returns 429. See Credits and usage.

Location › query Parameters

domain
​string · required

Company domain, such as stripe.com.

Location › Responses

Address counts by country.

For each country, the number of a domain's email addresses that belong to people in that country. See [Location response](https://docs.tomba.io/attributes/location).
Location
​object[] · required

One entry per country, in no particular order. An empty array when Tomba has no location data for the domain.

GET/location
curl 'https://api.tomba.io/v1/location?domain=stripe.com' \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": [ { "name": "US", "total": 450 }, { "name": "IE", "total": 120 }, { "name": "SG", "total": 35 } ] }
json
application/json

Author Finder

GET
https://api.tomba.io/v1
/author-finder
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Finds the email address of the author of an article or blog post from its URL. Tomba reads the page, identifies the author, and returns their address with the article and every author candidate in data.info.

When no address is found, the response is still 200: data.email is null, and data.info is returned if the page could be read. See Credits and usage for when a request is charged.

Author Finder › query Parameters

url
​string · required

URL of the article. The scheme is optional.

webhook_url
​string · uri

Optional URL that also receives the result in a POST request when the result qualifies. The response body is returned either way. See Webhooks.

Author Finder › Responses

The author's address, or data.email null when none is found.

Author finder response. When no address is found, `data.email` is `null`, the other fields are `null`, `false`, or `0`, `sources` is `null`, and `verification` is left out; `info` is still returned when the page could be read. See [Person response](https://docs.tomba.io/attributes/person#author-finder).
AuthorFinder
​object · required

The article's author and their email address.

GET/author-finder
curl 'https://api.tomba.io/v1/author-finder?url=https://stripe.com/blog/online-payments-guide' \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "email": "jane.doe@stripe.com", "first_name": "Jane", "last_name": "Doe", "full_name": "Jane Doe", "website_url": "stripe.com", "company": "Stripe", "pattern": null, "department": null, "type": null, "position": "Product Marketing Manager", "country": "US", "gender": "female", "twitter": null, "linkedin": "https://www.linkedin.com/in/jane-doe", "score": 100, "accept_all": false, "phone_number": false, "info": { "url": "https://stripe.com/blog/online-payments-guide", "title": "A guide to online payments", "og_image": "https://stripe.com/img/blog/online-payments-guide.png", "description": "How businesses accept payments online.", "article_domain": "stripe.com", "publisher_name": "Stripe", "publish_date": "2025-03-04", "candidates": [ { "full_name": "Jane Doe", "first_name": "Jane", "last_name": "Doe", "linkedin": "jane-doe", "job_title": "Product Marketing Manager", "sources": [ "json-ld", "byline" ], "name_confidence": 0.98, "score": 0.95, "count": 3 } ] }, "verification": { "date": "2025-03-10T09:15:00Z", "status": "valid" }, "sources": [ { "uri": "https://stripe.com/blog/online-payments-guide", "website_url": "stripe.com", "extracted_on": "2025-03-10T09:15:00Z", "last_seen_on": "2025-06-02T14:40:00Z", "still_on_page": true } ] } }
json
application/json

Linkedin Finder

GET
https://api.tomba.io/v1
/linkedin
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Finds the professional email address of the person behind a LinkedIn profile URL. Tomba returns a stored address when it has one; otherwise it may read the profile and search for the address live.

When no address is found, the response is still 200 and data.email is null. See Credits and usage for when a request is charged.

Linkedin Finder › query Parameters

url
​string · required

LinkedIn profile URL, such as https://www.linkedin.com/in/jane-doe.

enrich_mobile
​boolean

Set to true to also get the person's phone numbers in data.phone_data. Phone numbers cost extra credits; see Credits and usage.

Default: false
full
​boolean

Set to true to get an array of the addresses Tomba has stored for the profile, up to two, instead of the single most likely one. phone_data isn't included in this mode. When Tomba has no stored address, the response is a single object as without full.

Default: false
webhook_url
​string · uri

Optional URL that also receives the result in a POST request when the result qualifies. The response body is returned either way. See Webhooks.

Linkedin Finder › Responses

The person's address, an array of addresses with full=true, or data.email null when none is found.

LinkedIn finder response. `data` is one person, or an array of up to two addresses stored for the profile when you set `full=true`. When no address is found, `data` is a single object whose `email` is `null`, even with `full=true`.
LinkedinFinder
​required

One result, or an array of results with full=true.

GET/linkedin
curl 'https://api.tomba.io/v1/linkedin?url=https://www.linkedin.com/in/jane-doe' \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "email": "jane.doe@stripe.com", "first_name": "Jane", "last_name": "Doe", "full_name": "Jane Doe", "website_url": "stripe.com", "company": "Stripe", "pattern": "{first}.{last}", "department": "management", "type": "personal", "position": "Product Manager", "country": "US", "gender": "female", "twitter": null, "linkedin": "https://www.linkedin.com/in/jane-doe", "score": 100, "accept_all": false, "phone_number": false, "verification": { "date": "2025-01-15T10:32:00+01:00", "status": "valid" }, "sources": [ { "uri": "https://stripe.com/about", "website_url": "stripe.com", "extracted_on": "2024-01-10T12:00:00+01:00", "last_seen_on": "2025-01-10T17:02:44+01:00", "still_on_page": true } ], "phone_data": [] } }
json
application/json

Email Enrichment

GET
https://api.tomba.io/v1
/enrich
X-Tomba-Key (header)
+X-Tomba-Secret (header)

Returns the person behind an email address, with their name, company, job title, social profiles, and the address's verification status, in Tomba's own format. For Clearbit's format, use the Person API.

When Tomba has no data for the address, the response is still 200: data.email is null, and data.disposable and data.webmail describe the address's domain. See Credits and usage for when a request is charged.

Email Enrichment › query Parameters

email
​string · email · required

The email address to enrich.

enrich_mobile
​boolean

Set to true to also get the person's phone numbers in data.phone_data. Phone numbers cost extra credits; see Credits and usage.

Default: false
webhook_url
​string · uri

Optional URL that also receives the result in a POST request when the result qualifies. The response body is returned either way. See Webhooks.

Email Enrichment › Responses

The person, or data.email null when Tomba has no data for the address.

Email finder and email enrichment response. When no address is found, `data.email` is `null`, the other fields are `null`, `false`, or `0`, `sources` is `null`, and `verification` is left out. See [Person response](https://docs.tomba.io/attributes/person).
EmailFinder
​object · required

The person and their email address.

GET/enrich
curl 'https://api.tomba.io/v1/enrich?email=jane.doe@stripe.com' \ --header 'X-Tomba-Key: <api-key>' \ --header 'X-Tomba-Secret: <api-key>'
Example Responses
{ "data": { "email": "jane.doe@stripe.com", "first_name": "Jane", "last_name": "Doe", "full_name": "Jane Doe", "website_url": "stripe.com", "company": "Stripe", "pattern": "{first}.{last}", "department": "marketing", "type": "personal", "position": "Marketing Manager", "country": "US", "gender": "female", "twitter": null, "linkedin": "https://www.linkedin.com/in/jane-doe", "score": 100, "accept_all": false, "phone_number": true, "disposable": false, "webmail": false, "verification": { "date": "2025-01-20T08:45:12+01:00", "status": "valid" }, "sources": [ { "uri": "https://stripe.com/newsroom", "website_url": "stripe.com", "extracted_on": "2023-05-12T11:20:00+02:00", "last_seen_on": "2025-08-28T06:12:45+02:00", "still_on_page": true } ], "phone_data": [] } }
json
application/json

Verifier