How is Tomba different from other email finders?

Tomba builds its data from public web pages across 80M+ company domains, verifies every address before you send, and lists the public sources behind each one. Confirmed hard bounces on valid results are credited back under the data-quality guarantee.

Do I pay credits if you can't find an email?

No. A request is charged only when it returns a result; errors and empty searches cost nothing, and repeating a search in the same usage window is free.

What are catch-all emails and why should I care?

Catch-all domains accept mail for any address, so a standard check can't confirm that a specific mailbox exists. Tomba flags them, and the Catch-all Verifier checks those addresses further before you send.

Can I find phone numbers too?

Yes. Tomba finds direct phone numbers from company websites, email addresses and LinkedIn profiles, for contacts outside the EU. A phone search costs 5 search credits, or 1 when you pass a domain.

How accurate is the data?

Every address is verified before you send. In our public 5,000-lead benchmark Tomba found 4,015 valid emails, the most of the nine tools tested, and confirmed hard bounces on valid results are credited back under the data-quality guarantee.

What integrations and SDKs do you support?

13 official SDKs (C#, Dart, Deno, Elixir, Go, Lua, Node.js, Perl, PHP, Python, R, Ruby and Rust), a CLI and a remote MCP server. No-code: Zapier, Make and n8n, the Google Sheets and Excel add-ons, and Tomba for Salesforce on the Enterprise plan.

Is Tomba compliant with GDPR?

Tomba processes publicly available business contact data on a legitimate-interest basis, and anyone can remove their data at app.tomba.io/claim, free and without an account. A DPA with EU Standard Contractual Clauses is available.

// trusted by 150,000+ professionals

B2B email and phone data, one API call away

Find a work email from a name and a domain, verify it before you send, and enrich it with the person's role and company. Call it over REST, in bulk, from a spreadsheet or from an AI agent; every address comes with the public pages it was found on.

Get free API key Read the docs

25 free searches a monthNo card required13 SDKsMCP server for AI agents

GET /email-finder

curl "https://api.tomba.io/v1/email-finder?domain=piedpiper.com&first_name=Richard&last_name=Hendricks" \
  -H "X-Tomba-Key: $TOMBA_API_KEY" \
  -H "X-Tomba-Secret: $TOMBA_SECRET_KEY"

const res = await fetch("https://api.tomba.io/v1/email-finder?domain=piedpiper.com&first_name=Richard&last_name=Hendricks", {
  headers: {
    "X-Tomba-Key": process.env.TOMBA_API_KEY,
    "X-Tomba-Secret": process.env.TOMBA_SECRET_KEY
  }
});
const { data } = await res.json();

import os, requests

res = requests.get(
    "https://api.tomba.io/v1/email-finder?domain=piedpiper.com&first_name=Richard&last_name=Hendricks",
    headers={
        "X-Tomba-Key": os.environ["TOMBA_API_KEY"],
        "X-Tomba-Secret": os.environ["TOMBA_SECRET_KEY"],
    },
)
data = res.json()["data"]

Example response from the API reference

email: richard@piedpiper.com
full_name: Richard Hendricks
position: CEO
company: Pied Piper
score: 100
verification.status: valid
type: personal
accept_all: false
sources: 1 item

// teams at these companies use tomba

Based on verified reviews

verified contacts: 450M+
company domains indexed: 80M+
professionals use Tomba: 150,000+
email finders in our public 5,000-lead benchmark: #1 of 9

Counts: Tomba's internal database, October 2026. Benchmark: Tomba's own test, February 2026, with the raw exports published.

// 01 · endpoints

One API to find, verify and enrich contacts

Every tool on this site is an endpoint. Calls are paid in credits; finders and verifiers charge only when they return a result, and errors cost nothing.

EndpointReturnsCost

GET/email-finderA person's work email from their name and company domain1 search credit

GET/domain-searchThe email addresses at a company, with names, roles and the company profile1 per 10 search credits

GET/email-verifierWhether an address is deliverable: syntax, MX, SMTP, catch-all and greylisting checks1 verification credit

GET/enrichThe person behind an email address: name, role, company and profiles1 search credit

GET/linkedinThe work email of the person behind a LinkedIn profile URL1 search credit

GET/phone-finderA person's phone number from their email, domain or LinkedIn URL5 search credits

POST/reveal/searchCompanies that match a plain-language query or filters1 search credit

GET/combined/findThe person and their company from one email address2 search credits

GET/email-sourcesThe public pages where an address was found, with first and last seen dates1 sources credit

GET/technologyThe technologies a website runs, by categoryFree

Base URL https://api.tomba.io/v1 · Send X-Tomba-Key and X-Tomba-Secret with every request.Every endpoint in the API reference

// 02 · data

People and companies as clean JSON

The records the app shows, field for field, with null where Tomba isn't sure rather than a guess.

GET/enrichThe person behind an email address: name, role, company and profiles1 search credit

GET/enrichField

data.emailstring | null: The address, or null when none is found
data.scoreinteger: Confidence from 0 to 100
data.verification.statusstring | null: valid, accept_all, invalid or unknown, with verification.date
data.full_name, data.position, data.departmentstring | null: Name, job title and team
data.typestring | null: personal or generic (a role address such as sales@)
data.linkedin, data.twitterstring | null: Public profiles
data.sources[]array | null: Up to 20 public pages where the address was found, with dates
data.company, data.website_urlstring | null: The company and its domain
data.disposable, data.webmailboolean: The address is on a disposable or webmail domain
data.accept_allboolean | null: The domain accepts mail for any address (catch-all)
data.phone_numberboolean: Tomba holds a phone number for the person
data.phone_data[]array: The numbers, when you send enrich_mobile (each as in Phone Finder)

API reference

GET /enrich

200 OK· 1 search credit

{
  "data": {
    "email": "richard@piedpiper.com",
    "first_name": "Richard",
    "last_name": "Hendricks",
    "full_name": "Richard Hendricks",
    "website_url": "piedpiper.com",
    "company": "Pied Piper",
    "pattern": "{first}",
    "department": "executive",
    "type": "personal",
    "position": "CEO",
    "country": "US",
    "gender": "male",
    "twitter": null,
    "linkedin": "https://www.linkedin.com/in/richard-hendricks",
    "score": 100,
    "accept_all": false,
    "phone_number": true,
    "verification": {
      "date": "2025-01-15T10:32:00+01:00",
      "status": "valid"
    },
    "sources": [
      {
        "uri": "https://piedpiper.com/blog/engineering",
        "website_url": "piedpiper.com",
        "extracted_on": "2024-06-01T09:14:07+01:00",
        "last_seen_on": "2025-01-10T17:02:44+01:00",
        "still_on_page": true
      }
    ],
    "disposable": false,
    "webmail": false,
    "phone_data": []
  }
}

GET/companies/findA company profile from its domain: industry codes, size, location, socials1 search credit

GET/companies/findField

data.name, data.legalName, data.domainstring | null: Who the company is
data.description, data.foundedYear, data.typestring | null: What it does, when it was founded, its ownership
data.categoryobject: Sector, industry, SIC and NAICS codes
data.geoobject: Street address, city, state, country, coordinates
data.metricsobject: Employees, traffic rank, revenue, funding
data.linkedin, data.twitter, data.facebookobject: Social handles
data.tech[], data.techCategories[]array | null: Technologies the website runs
meta.domainstring | null: The domain you sent
errorsobject: When nothing is found the response is still 200, with errors {type, message, code} instead of data

API reference

GET /companies/find

200 OK· 1 search credit

{
  "data": {
    "name": "Pied Piper",
    "legalName": "Pied Piper, Inc.",
    "domain": "piedpiper.com",
    "domainAliases": [],
    "site": {
      "phoneNumbers": [],
      "emailAddresses": [
        "hello@piedpiper.com"
      ]
    },
    "category": {
      "sector": "Information Technology",
      "industryGroup": "Software & Services",
      "industry": "Internet Software & Services",
      "subIndustry": "Internet Software & Services",
      "sicCode": "73",
      "sic4Codes": [
        "7372"
      ],
      "naicsCode": "51",
      "naics6Codes": [
        "511210"
      ],
      "naics6Codes2022": [
        "513210"
      ]
    },
    "tags": [
      "Compression",
      "Decentralized internet"
    ],
    "description": "Pied Piper builds middle-out compression for files, video and a decentralized internet.",
    "foundedYear": "2014",
    "location": "5230 Newell Road, Palo Alto, CA 94303, United States",
    "timeZone": "America/Los_Angeles",
    "utcOffset": -8,
    "geo": {
      "streetNumber": "5230",
      "streetName": "Newell Road",
      "subPremise": null,
      "streetAddress": "5230 Newell Road",
      "city": "Palo Alto",
      "postalCode": "94303",
      "state": "California",
      "stateCode": "CA",
      "country": "United States",
      "countryCode": "US",
      "lat": 37.4419,
      "lng": -122.143
    },
    "logo": "https://logo.tomba.io/piedpiper.com",
    "facebook": {
      "handle": null,
      "likes": null
    },
    "linkedin": {
      "handle": "company/pied-piper"
    },
    "twitter": {
      "handle": null,
      "id": null,
      "bio": null,
      "followers": null,
      "following": null,
      "location": null,
      "site": null,
      "avatar": null
    },
    "whois": {
      "registrar_name": null,
      "created_date": null,
      "referral_url": null
    },
    "emailProvider": "Google",
    "type": "private",
    "ticker": null,
    "identifiers": {
      "usEIN": null
    },
    "metrics": {
      "alexaUsRank": null,
      "alexaGlobalRank": null,
      "trafficRank": null,
      "employees": "11-50",
      "marketCap": null,
      "raised": null,
      "annualRevenue": null,
      "estimatedAnnualRevenue": null,
      "fiscalYearEnd": null
    },
    "indexedAt": "2025-01-15T10:32:00+01:00",
    "tech": [
      "google_apps",
      "intercom"
    ],
    "techCategories": [
      "email_hosting_service",
      "live_chat"
    ],
    "parent": {
      "domain": null
    },
    "ultimateParent": {
      "domain": null
    }
  },
  "meta": {
    "domain": "piedpiper.com"
  }
}

// 03 · delivery

Call it the way your team works

The same endpoints and the same credits behind the API, bulk jobs, spreadsheets, the browser extension and AI agents.

// 04 · 5,000-lead benchmark

More valid emails than the eight other tools we tested

Real data. Same input. No human touch. Full transparency. We ran a head-to-head test using the same 5,000-line input file across multiple email-finding tools. No manual cleanup. No tweaks. Just raw results exported as full sheets.

Tomba.io found 4,015 valid emails from 5,000 leads: #1 of 9 tools tested.
Rank	Tool	From websites	From company names	Total
1	Tomba.io	2,02681%	1,98979.6%	4,015
2	Anymailfinder	1,91876.7%	1,95778.3%	3,875
3	Findymail	1,88075.2%	1,87775.1%	3,757
4	GetProspect	1,48359.3%	1,61364.5%	3,096
5	Skrapp	1,00140%	1,14145.6%	2,142
6	Hunter	88735.5%	99539.8%	1,882
7	VoilaNorbert	1,05142%	74930%	1,800
8	Snov	98839.5%	Under 1% found from company names: the tool needs a website or domain:190.8%	1,007
9	Prospeo	82433%	Under 1% found from company names: the tool needs a website or domain:220.9%	846

Tomba.io found 4,015 valid emails from 5,000 leads: #1 of 9 tools tested.

Tomba’s own test, February 2026. One file of 5,000 leads, 2,500 with the company website and 2,500 with only the company name, ran through each tool with no manual cleanup. Only addresses a tool labelled valid or verified count; percentages are of the 2,500 inputs of each kind.

Under 1% found from company names: the tool needs a website or domain.

View raw data spreadsheet

// 05 · compliance

Every record carries its receipts

Public sources with dates, a verification you can read, and opt-outs enforced by the API itself. GDPR and CCPA aligned, with a DPA under the EU's standard contractual clauses.

GET/email-finderOne record, with its receipts

richard@piedpiper.com

position

CEO

company

Pied Piper

score

100

verification.status

valid

verification.date

2025-01-15

twitter

null

sources[0]

https://piedpiper.com/blog/engineering

extracted_on 2024-06-01 · last_seen_on 2025-01-10

Sources listed: the public pages where the address was found, with dates
Verified on a date you can read: syntax, MX and SMTP checks
Opted-out people return 451, never the address
null when Tomba isn't sure, never a guess

// 06 · teams and access

Roles, limits and single sign-on for the whole workspace

One credit pool, four roles, monthly limits per member, and SAML SSO with SCIM provisioning on Enterprise. What each role can do is enforced by the API, not just hidden in the app.

Roles, limits and single sign-on for the whole workspace
Capability	Owner	Admin	Member	Guest
Search, verify and enrich from the shared credits	Allowed	Allowed	Allowed	Allowed
Run bulk jobs and export results	Allowed	Allowed	Allowed	Not allowed
Set each member's monthly search and verification limits	Allowed	Allowed	Not allowed	Not allowed
Invite, edit and remove members	Allowed	Allowed	Not allowed	Not allowed
See every member's usage	Allowed	Allowed	Not allowed	Not allowed
Manage workspace settings and domains	Allowed	Allowed	Not allowed	Not allowed
Configure SAML SSO and SCIM (Enterprise)	Allowed	Allowed	Not allowed	Not allowed
Delete the workspace	Allowed	Not allowed	Not allowed	Not allowed

seats and 2,000 API keys on Enterprise: 5,000
SSO with just-in-time provisioning; enforcement off, optional or required: SAML 2.0
users provisioned and removed from your identity provider: SCIM 2.0
maximum API key lifetime; OAuth 2.0 with read, search, verify, enrich, leads and account scopes: 365 days

Roles as enforced by the Tomba API, October 2026. SAML SSO and SCIM are Enterprise features.Invite your team

Don't take our word for it

Real reviews from real sales professionals.

Tomba finding the contacts for the perfect prospects at scale is game changing in helping us promote our data-based research studies.
Nicholas RizzoSenior Digital Manager, Vizme
Tomba.io is very fast with lots of features. I run leads from Apollo into Tomba and grab prospect info in record time. I'm saving at least 5 hours a week. No joke.
Julian M.Account Executive, Insight
The data is always fresh, and the n8n integration is excellent. Support is very responsive. I'd rate it 9/10.
Benjie MalinaoCo-Founder & CTO, Channel Automation
Tomba is my go-to to validate emails. Even in a waterfall process with multiple tools, Tomba is usually the top choice.
Nuno PoçoSales Automation Architect, clickworks.io
Stellar product and amazing support. I have tested many tools and this one is far superior by far. I highly recommend it.
Martin EbonguéEntrepreneur, Genius Data Flow
I've been using Tomba.io for nearly three years. I've run multiple side-by-side tests against other tools and Hunter. Tomba.io delivered better results every time.
Aristotle MalichettyBusiness Intelligence Analyst
Tomba.io keeps getting better every day. I've been using it since 2021. It's now a leading solution for email finding, verification, and easily finding mobile numbers.
Osama AhmedSEO Ninja, BYTEBEX
Since years, Tomba has provided the most results per search, and it keeps getting better. It recently became one of the most feature-rich tools for our list building.
Steffen BurandtHead of Business Development, Chandler Orchards
I've tested over a dozen email finder tools, and Tomba.io stands out as the best. It consistently delivers accurate results. The SDK and docs make integration fast.
Andrei KholkinFounder, Superpage.io