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
Clearbit
Email verifiers
Email finders
    OverviewHunterSnov.ioProspeoFindymailApollo.ioVoila NorbertSkrapp
Phone finders
Email finders

Migrate from Hunter (email finder)

This guide maps the Hunter API v2 Domain Search, Email Finder, Email Count, Account, and People, Companies, and Combined enrichment endpoints to Tomba. Hunter's Email Verifier is covered in Migrate from Hunter (email verifier). Hunter API behavior checked on 2026-09-29 against the Hunter API v2 reference.

Before you begin

  • Get your API key (ta_…) and secret (ts_…); see Authentication.
  • Check what each endpoint costs in Credit costs and your plan's throttling in Limits by plan.
  • Set your HTTP client timeout to at least 180 seconds. Tomba returns the finished result in the response.

Endpoint mapping

Replace the base URL https://api.hunter.io/v2 with https://api.tomba.io/v1.

HunterTombaNotes
GET /domain-searchGET /v1/domain-searchSee Domain search.
GET /email-finderGET /v1/email-finderSee Email finder.
GET /email-finder with linkedin_handleGET /v1/linkedin
GET /email-countGET /v1/email-count
GET /people/findGET /v1/people/find
GET /companies/findGET /v1/companies/find
GET /combined/findGET /v1/combined/find
GET /accountGET /v1/meSee Check usage.

Authentication changes

Hunter accepts the key as the api_key parameter, the X-API-KEY header, or a bearer token. Tomba needs two headers, X-Tomba-Key and X-Tomba-Secret, and doesn't accept credentials in the query string:

TerminalCode
# Hunter curl "https://api.hunter.io/v2/email-finder?domain=stripe.com&first_name=Jane&last_name=Doe" \ -H "X-API-KEY: $HUNTER_API_KEY" # Tomba curl "https://api.tomba.io/v1/email-finder?domain=stripe.com&first_name=Jane&last_name=Doe" \ -H "X-Tomba-Key: $TOMBA_API_KEY" \ -H "X-Tomba-Secret: $TOMBA_SECRET_KEY"

Tomba API keys expire; plan their rotation with Key expiry.

Domain search

Parameters

HunterTombaNotes
domaindomain
companycompany
limitlimitTomba accepts a fixed set of values; see the API reference. The cost depends on limit; see Credit costs.
offsetpageTomba pages start at 1: page = offset / limit + 1.
typetype
departmentdepartmentComma-separated in both APIs, but the department names differ. The values are in the API reference.
location with a countrycountryA two-letter country code. Continent, region, state, and city filters have no equivalent.
seniority, verification_statusNo equivalentEach result carries seniority and verification.status; filter the results in your code.
decision_maker, required_field, job_titlesNo equivalent
aggregationsNo equivalentUse GET /v1/email-count for counts by department and seniority.

Response fields

HunterTombaNotes
data.domaindata.organization.website_url
data.organizationdata.organization.organization
data.patterndata.organization.pattern
data.accept_all, data.disposable, data.webmaildata.organization.accept_all, .disposable, .webmail
data.linked_domainsNo equivalent
data.emails[].valuedata.emails[].email
data.emails[].confidencedata.emails[].scoreComputed differently. Recalibrate any threshold you apply to it.
data.emails[].type, first_name, last_name, position, seniority, departmentSame namesDepartment values differ.
data.emails[].twitter, linkedinSame namesTomba returns full profile URLs; Hunter returns the Twitter handle.
data.emails[].phone_numberdata.emails[].phone_numberA boolean in Tomba. Request numbers with enrich_mobile=true, at an extra cost.
data.emails[].position_raw, decision_makerNo equivalent
data.emails[].verificationdata.emails[].verificationSame date and status keys.
data.emails[].sources[].domaindata.emails[].sources[].website_urluri, extracted_on, last_seen_on, and still_on_page keep their names.
meta.resultsmeta.total
meta.limit, meta.offsetmeta.pageSize, meta.currentmeta.current is the page number. meta.total_pages gives the page count.
meta.results_approximateNo equivalent

Tomba also returns company details in data.organization, such as industries, company_size, location, and social_links.

Email finder

Parameters

HunterTombaNotes
domaindomainTomba returns 400 unknown_record for a disposable or webmail domain.
companycompany
first_name, last_namefirst_name, last_name
full_namefull_name
linkedin_handleurl on GET /v1/linkedinSend the profile URL.
max_durationNo equivalentSet the timeout in your HTTP client.

Response fields

HunterTombaNotes
data.emaildata.emailnull when no address is found; the status is still 200.
data.first_name, last_name, position, company, accept_allSame names
data.scoredata.scoreComputed differently.
data.domaindata.website_url
data.twitterdata.twitterA full URL in Tomba.
data.linkedin_urldata.linkedin
data.phone_numberdata.phone_numberA boolean in Tomba.
data.verificationdata.verificationSame date and status keys. Tomba can also return invalid, or null when the address hasn't been verified; see Status values.
data.sources[]data.sources[]domain is website_url.
meta.paramsNo equivalent

Tomba also returns full_name, pattern, department, type, country, and gender.

Email count and enrichment

HunterTombaNotes
Email Count domain, typedomain, typeTomba doesn't accept company here.
Email Count data.total, personal_emails, generic_emails, department, senioritySame pathsThe department keys differ; see Email count.
People emailemailTomba doesn't accept linkedin_handle.
Companies domaindomain
clearbit_formatNo equivalentTomba's enrichment responses always use the Clearbit-style shape; see Enrichment.
404 when nothing is found200 with an errors body, type not_foundCheck the body for errors.

Error mapping

Hunter returns errors as an array of {id, code, details}. Tomba returns a single errors object with type, message, and code. The meaning of 403 and 429 also changes:

HunterTombaWhat to do
400 wrong_params or another invalid_* id422 params_invalidFix the parameter named in the message.
400 invalid_domain400 unknown_record for a disposable or webmail domainUse a company domain.
401 no valid API key400 authentication_failed (missing or malformed), 400 api_key_expired, 401 authentication_failed (wrong key or secret)Check both headers; rotate an expired key.
403 rate limit reached429 rate_limitRetry after the Retry-After delay; see Handle 429 responses.
429 usage limit reached402 quota_exceededWait for your usage window to renew or add credits.
429 restricted_account401 authentication_failedContact support.
451 claimed_email451 claimed_emailSame meaning. Remove the address from your data.
5xx500 api_errorRetry with backoff.

Error responses don't consume credits. Every type is listed in Errors.

Bulk and async jobs

Hunter runs bulk Domain Search and Email Finder lists from its dashboard, and its API endpoints take one item per request. Tomba runs lists through the API as bulk jobs:

Hunter taskTomba bulk type
Domain Search over many domainssearch: a JSON list of domains. See Domain search.
Email Finder over a list of peoplefinder: a CSV file with name and company columns. See Email finder.

Each job is created, launched, polled, and downloaded as CSV; see Lifecycle. A job is charged when you first download its results; see Billing.

Code example

This function replaces a call to Hunter's Email Finder and returns Hunter's field names, or null when no address is found. It needs Node.js 18 or later.

Code
const TOMBA_HEADERS = { "X-Tomba-Key": process.env.TOMBA_API_KEY, "X-Tomba-Secret": process.env.TOMBA_SECRET_KEY, }; // Accepts Hunter's parameters: domain or company, and first_name + last_name or full_name. async function emailFinder(params) { const url = new URL("https://api.tomba.io/v1/email-finder"); for (const key of [ "domain", "company", "first_name", "last_name", "full_name", ]) { if (params[key]) url.searchParams.set(key, params[key]); } const res = await fetch(url, { headers: TOMBA_HEADERS }); const body = await res.json(); if (body.errors) { throw new Error( `${res.status} ${body.errors.type}: ${body.errors.message}`, ); } const found = body.data; if (!found.email) return null; return { first_name: found.first_name, last_name: found.last_name, email: found.email, score: found.score, domain: found.website_url, accept_all: found.accept_all, position: found.position, twitter: found.twitter, linkedin_url: found.linkedin, company: found.company, sources: (found.sources ?? []).map(({ website_url, ...source }) => ({ domain: website_url, ...source, })), verification: found.verification ?? null, }; } console.log( await emailFinder({ domain: "stripe.com", first_name: "Jane", last_name: "Doe", }), );

Cutover checklist

  1. Store the Tomba key and secret as TOMBA_API_KEY and TOMBA_SECRET_KEY, and send them as X-Tomba-Key and X-Tomba-Secret instead of api_key, X-API-KEY, or a bearer token.
  2. Change the base URL, convert offset to page, send linkedin_handle lookups to /v1/linkedin, and filter results in code where Tomba has no filter.
  3. Update response parsing: value becomes email, source domain becomes website_url, and the domain search company fields move under data.organization.
  4. Swap error handling: 402 replaces Hunter's 429, 429 replaces Hunter's 403, and errors is an object, not an array.
  5. Move list processing to bulk jobs.
  6. Run the same sample of domains and people through both services and compare the results before you switch production traffic.
Last modified on November 6, 2026
OverviewSnov.io
On this page
  • Before you begin
  • Endpoint mapping
  • Authentication changes
  • Domain search
    • Parameters
    • Response fields
  • Email finder
    • Parameters
    • Response fields
  • Email count and enrichment
  • Error mapping
  • Bulk and async jobs
  • Code example
  • Cutover checklist
Javascript