Finder
Find email addresses by domain, name, article, or LinkedIn profile, and enrich them
Domain Search
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.
query Parameters
domainCompany domain, such as stripe.com. Send domain or company.
companyCompany 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.
pagePage number, starting at 1. On the Free plan outside a workspace, every request returns page 1.
limitNumber of addresses per page. On the Free plan outside a workspace, a value above 10 fails with 400.
countryTwo-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.
departmentReturn 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.
typepersonal returns only addresses that belong to one person, generic only role addresses such as support@.
enrich_mobileSet to true to also get each person's phone numbers in phone_data. Phone numbers cost extra credits; see Credits and usage.
webhook_urlOptional 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.
The company and its email addresses.
Paging for the email addresses, and the request as the API read it.
Email Finder
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.
query Parameters
domainCompany 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.
companyCompany name, such as Stripe. Send domain or company. A domain gives better results.
first_nameThe person's first name. Send first_name and last_name, or full_name.
last_nameThe person's last name.
full_nameThe 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_mobileSet to true to also get the person's phone numbers in data.phone_data. Phone numbers cost extra credits; see Credits and usage.
webhook_urlOptional 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.
The person and their email address.
Email Count
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.
query Parameters
domainCompany domain, such as stripe.com.
typeCount only personal or only generic addresses in total and in the department and seniority counts. personal_emails and generic_emails are always returned.
Email Count › Responses
The counts for the domain.
The counts.
website_idTomba's internal ID for the domain's company record. 0 when Tomba has no record of the domain.
Email Format
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.
query Parameters
domainCompany domain, such as stripe.com.
Email Format › Responses
The domain's email formats.
Up to 20 formats, in no particular order. An empty array when Tomba has no formats for the domain.
Location
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.
query Parameters
domainCompany domain, such as stripe.com.
Location › Responses
Address counts by country.
One entry per country, in no particular order. An empty array when Tomba has no location data for the domain.
Author Finder
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.
query Parameters
urlURL of the article. The scheme is optional.
webhook_urlOptional 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.
The article's author and their email address.
Linkedin Finder
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.
query Parameters
urlLinkedIn profile URL, such as https://www.linkedin.com/in/jane-doe.
enrich_mobileSet to true to also get the person's phone numbers in data.phone_data. Phone numbers cost extra credits; see Credits and usage.
fullSet 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.
webhook_urlOptional 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.
One result, or an array of results with full=true.
Email Enrichment
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.
query Parameters
emailThe email address to enrich.
enrich_mobileSet to true to also get the person's phone numbers in data.phone_data. Phone numbers cost extra credits; see Credits and usage.
webhook_urlOptional 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.
The person and their email address.