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
    OverviewNeverBounceMillionVerifierBounceBanBouncerKickboxHunterZeroBounceEmailableClearoutDeBounce
Email finders
Phone finders
Email verifiers

Migrate from Emailable

This guide maps the Emailable API v1 (single verification, batch verification, and account info) to the Tomba Email Verifier and bulk verifier jobs. Emailable API behavior checked on 2026-09-30 against the Emailable API reference.

Before you begin

  • Get your API key (ta_…) and secret (ts_…); see Authentication.
  • Check what a verification 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, so there is no 249 response to retry.

Endpoint mapping

Replace the base URL https://api.emailable.com/v1 with https://api.tomba.io/v1.

EmailableTomba
GET /v1/verify (or POST)GET /v1/email-verifier
POST /v1/batchPOST /v1/bulk/verifier, then PUT /v1/bulk/verifier/{id} to launch
GET /v1/batch?id=GET /v1/bulk/verifier/{id}/progress, then GET /v1/bulk/verifier/{id}/download
GET /v1/accountGET /v1/me

Authentication changes

Emailable reads the key from the api_key parameter (or an OAuth access_token), or from an Authorization: Bearer header. Tomba needs two headers, X-Tomba-Key and X-Tomba-Secret, and doesn't accept credentials in the query string or body:

TerminalCode
# Emailable curl "https://api.emailable.com/v1/verify?email=jane.doe@stripe.com" \ -H "Authorization: Bearer $EMAILABLE_API_KEY" # Tomba curl "https://api.tomba.io/v1/email-verifier?email=jane.doe@stripe.com" \ -H "X-Tomba-Key: $TOMBA_API_KEY" \ -H "X-Tomba-Secret: $TOMBA_SECRET_KEY"

If you call Emailable from browser code with a public API key, move the call to your server and keep the Tomba key and secret there (Security). Tomba API keys expire; plan their rotation with Key expiry.

Parameter mapping

EmailableTombaNotes
api_key, access_tokenX-Tomba-Key and X-Tomba-Secret headers
emailemailRequired. A malformed address returns 422 params_invalid instead of a result.
smtpNo equivalent
accept_allNo equivalentEvery Tomba response includes data.email.accept_all.
timeoutNo equivalentSet the timeout in your HTTP client.
captcha_responseNo equivalent
Batch emailslistA newline-separated string, instead of a comma-separated string or JSON array. Also send name.
Batch urlwebhook_urlReceives a signed event when the job ends. See Bulk job events.
Batch response_fields, retries, simulateNo equivalent
Batch status id{id} in the path
Batch status partialNo equivalentResults are available only as a CSV download once the job is completed.

Response field mapping

Emailable returns a flat object. Tomba nests the checks in data.email and lists the public pages where the address appears in data.sources. Field definitions are in Email verifier response.

EmailableTombaNotes
emaildata.email.emailAn empty string when the domain is disposable.
statedata.email.status, data.email.resultSee Status mapping.
reasonNo equivalentTomba reports greylisted, block, and mx_check as separate fields.
scoredata.email.scoreComputed differently.
accept_alldata.email.accept_all
disposabledata.email.disposable
freedata.email.webmail
mx_recorddata.email.mx.recordsAn array of MX host names instead of one string.
smtp_providerdata.email.smtp_provider
role, no_reply, mailbox_fullNo equivalent
did_you_meanNo equivalent
user, domain, tagNo equivalentSplit the address yourself.
first_name, last_name, full_name, gender, birth_yearNo equivalent
durationNo equivalent
messageerrors.messageReturned with an HTTP error status; see Error mapping.

Tomba also returns block, greylisted, gibberish, regex, and whois, which have no Emailable counterpart. Read your remaining balance, Emailable's available_credits, from the X-Verify-Remaining header or GET /v1/me; see Check usage.

Status mapping

Emailable stateTomba statusTomba result
deliverablevaliddeliverable
undeliverableinvalidundeliverable
riskyaccept_all for a catch-all domain; disposable for a disposable domainrisky; an empty string for disposable
unknownunknownrisky

An address that Emailable returns as undeliverable with the reason invalid_email fails syntax checks; Tomba rejects it with 422 params_invalid instead of returning a status.

Tomba's result uses the same words as Emailable's state for deliverable, undeliverable, and risky, but an inconclusive check is risky, not unknown. Branch on status to tell them apart, and compare it case-insensitively. Each value is defined in Status values.

Error mapping

Both APIs signal failures with HTTP status codes. Emailable's error body is {"message": "…"}; Tomba's is an errors object with type, message, and code.

EmailableTombaWhat to do
249 Try AgainNot returnedRemove the retry loop.
400 Bad Request422 params_invalidFix the parameter named in the message.
401 no API key400 authentication_failedSend both headers.
403 invalid API key401 authentication_failed (wrong key or secret), 400 api_key_expiredCheck both headers; rotate an expired key.
402 Payment Required402 quota_exceededWait for your usage window to renew or add credits.
404 batch not foundGET /v1/bulk/verifier/{id} returns 404 unknown_recordCheck the job ID.
429 Too Many Requests429 rate_limitRetry after the Retry-After delay; see Handle 429 responses.
500, 503500 api_errorRetry with backoff.
No equivalent408 proxy_errorThe mailbox check failed. Retry later.
No equivalent451 claimed_emailThe owner of the address asked Tomba to stop processing it. Remove it from your list.

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

Bulk and async jobs

EmailableTomba
POST /v1/batch with emailsPOST /v1/bulk/verifier with name and a newline-separated list, or a CSV file
Verification starts on creationLaunch the job: PUT /v1/bulk/verifier/{id}
Poll GET /v1/batch for processed and totalPoll GET /v1/bulk/verifier/{id}/progress for status and progress until status is completed
The url callbackwebhook_url. See Bulk job events.
emails array (up to 1,000 addresses) or a download_file ZIPGET /v1/bulk/verifier/{id}/download?file=full returns a CSV for every job size
total_counts, reason_countsNo equivalent. Count the rows of the CSV.
TerminalCode
curl -X POST "https://api.tomba.io/v1/bulk/verifier" \ -H "X-Tomba-Key: $TOMBA_API_KEY" \ -H "X-Tomba-Secret: $TOMBA_SECRET_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "Newsletter list", "list": "jane.doe@stripe.com\njohn.smith@shopify.com"}'

The launch, progress, and download requests are shown in Lifecycle. Row limits and daily job limits are in Limits, and a job is charged when you first download its results; see Billing.

Code example

This function replaces a call to /v1/verify and returns Emailable's field names for the values Tomba supplies. 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, }; // Tomba status -> Emailable state const STATES = { valid: "deliverable", invalid: "undeliverable", accept_all: "risky", disposable: "risky", unknown: "unknown", }; async function verify(email) { const url = new URL("https://api.tomba.io/v1/email-verifier"); url.searchParams.set("email", email); const res = await fetch(url, { headers: TOMBA_HEADERS }); const body = await res.json(); if (body.errors) { // Tomba never returns 249; a response is always final. throw new Error( `${res.status} ${body.errors.type}: ${body.errors.message}`, ); } const check = body.data.email; return { email: check.email || email, state: STATES[check.status.toLowerCase()] ?? "unknown", score: check.score, accept_all: check.accept_all, disposable: check.disposable, free: check.webmail, mx_record: check.mx?.records?.[0] ?? null, smtp_provider: check.smtp_provider, }; } console.log(await verify("jane.doe@stripe.com"));

Cutover checklist

  1. Store the Tomba key and secret as TOMBA_API_KEY and TOMBA_SECRET_KEY, send them as X-Tomba-Key and X-Tomba-Secret, and remove api_key and bearer tokens from your requests and logs.
  2. Point single verifications at GET https://api.tomba.io/v1/email-verifier, drop smtp, accept_all, and timeout, and set a client timeout of at least 180 seconds.
  3. Remove the 249 retry loop and swap error handling: 400 for a missing key, 401 for a wrong one, 422 for bad parameters, and 408 and 451 as new cases.
  4. Translate state with the status mapping, branching on status rather than result, and compare it case-insensitively.
  5. Replace batches with verifier bulk jobs: create with list or file, launch, receive the webhook_url event instead of the url callback, and download the CSV.
  6. Verify the same sample list with both services and compare the mapped results before you switch production traffic.
Last modified on September 30, 2026
ZeroBounceClearout
On this page
  • Before you begin
  • Endpoint mapping
  • Authentication changes
  • Parameter mapping
  • Response field mapping
  • Status mapping
  • Error mapping
  • Bulk and async jobs
  • Code example
  • Cutover checklist
Javascript