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 MillionVerifier

This guide maps the MillionVerifier API (single verification v3, the bulk file API v2, and credits) to the Tomba Email Verifier and bulk verifier jobs. MillionVerifier API behavior checked on 2026-09-29 against the MillionVerifier 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.

Endpoint mapping

MillionVerifier uses two hosts, api.millionverifier.com and bulkapi.millionverifier.com. Tomba serves everything from api.tomba.io.

MillionVerifierTomba
GET https://api.millionverifier.com/api/v3/GET /v1/email-verifier
POST https://bulkapi.millionverifier.com/bulkapi/v2/uploadPOST /v1/bulk/verifier, then PUT /v1/bulk/verifier/{id} to launch
GET /bulkapi/v2/fileinfoGET /v1/bulk/verifier/{id}/progress
GET /bulkapi/v2/filelistGET /v1/bulk/verifier
GET /bulkapi/v2/downloadGET /v1/bulk/verifier/{id}/download
GET /bulkapi/stopNo equivalent
GET /bulkapi/v2/deleteDELETE /v1/bulk/verifier/{id}/delete
GET https://api.millionverifier.com/api/v3/creditsGET /v1/me

Authentication changes

MillionVerifier reads the key from the query string: api on the single and credits endpoints, key on the bulk endpoints. Tomba needs two headers, X-Tomba-Key and X-Tomba-Secret, and doesn't accept credentials in the query string:

TerminalCode
# MillionVerifier curl "https://api.millionverifier.com/api/v3/?api=$MILLIONVERIFIER_API_KEY&email=jane.doe@stripe.com&timeout=10" # 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"

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

Parameter mapping

MillionVerifierTombaNotes
api, keyX-Tomba-Key and X-Tomba-Secret headers
emailemailRequired. A malformed address returns 422 params_invalid instead of a result.
timeoutNo equivalentSet the timeout in your HTTP client.
Upload file_contentsfileAlso send name, and email_field_index (zero-based) if the header doesn't name the address column.
Download filter=allfile=full
Download filter=okfile=valid
Download filter ok_and_catch_all, unknown, invalid, customNo equivalentDownload file=full and filter the rows.
file_id{id} in the path

Response field mapping

MillionVerifier 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.

MillionVerifierTombaNotes
emaildata.email.emailAn empty string when the domain is disposable.
result, resultcodedata.email.status, data.email.resultSee Status mapping.
qualitydata.email.resultThe closest field; see Result values.
subresultNo equivalentTomba reports greylisted, block, and mx_check as separate fields.
freedata.email.webmail
roleNo equivalent
didyoumeanNo equivalent
creditsX-Verify-Remaining header, GET /v1/meSee Check usage.
executiontimeNo equivalent
errorerrors.messageReturned with an HTTP error status; see Error mapping.
livemodeNo equivalent

Tomba also returns accept_all, disposable, gibberish, regex, smtp_provider, mx.records, and whois, which have no MillionVerifier counterpart.

Status mapping

MillionVerifier resultresultcodeTomba statusTomba result
ok1validdeliverable
catch_all2accept_allrisky
unknown3unknownrisky
error4No status. The request fails with an HTTP error.
disposable5disposableEmpty string
invalid6invalidundeliverable

Compare status case-insensitively. Each value is defined in Status values.

Error mapping

MillionVerifier returns errors with HTTP 200, as result: "error" and an error string on the single endpoint, or an error field on the bulk endpoints. Tomba returns an HTTP error status with an errors object, so check the status code instead:

MillionVerifierTombaWhat to do
apikey_not_found (single), invalid_api_key (bulk)400 authentication_failed (missing or malformed), 400 api_key_expired, 401 authentication_failed (wrong key or secret)Check both headers; rotate an expired key.
No email specified422 params_invalidFix the parameter named in the message.
insufficient_credits (bulk upload)402 quota_exceeded on single requestsFor bulk jobs, the balance is checked at the first download instead; see Billing.
No equivalent429 rate_limitRetry after the Retry-After delay; see Handle 429 responses.
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

MillionVerifierTomba
Upload a file with file_contentsPOST /v1/bulk/verifier with name and a CSV file, or a newline-separated list of addresses
No start callLaunch the job: PUT /v1/bulk/verifier/{id}
Poll fileinfo for status and percentPoll GET /v1/bulk/verifier/{id}/progress for status and progress until status is completed
The file_ready webhook, set in account settingswebhook_url on the job, which receives a signed bulk.completed event. See Bulk job events.
download with a filterGET /v1/bulk/verifier/{id}/download?file=full
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" \ -F "name=Newsletter list" \ -F "file=@emails.csv;type=text/csv" \ -F "email_field_index=0"

Tomba treats the first row of the file as a header. 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 /api/v3/ and returns MillionVerifier's result and resultcode for the address. 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 -> MillionVerifier [result, resultcode] const RESULTS = { valid: ["ok", 1], accept_all: ["catch_all", 2], unknown: ["unknown", 3], disposable: ["disposable", 5], invalid: ["invalid", 6], }; 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) { // Unlike MillionVerifier, errors use HTTP status codes, such as 402 or 429. throw new Error( `${res.status} ${body.errors.type}: ${body.errors.message}`, ); } const check = body.data.email; const [result, resultcode] = RESULTS[check.status.toLowerCase()] ?? RESULTS.unknown; return { email: check.email || email, result, resultcode, free: check.webmail, }; } 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 the api and key parameters from your URLs and logs.
  2. Point single verifications at GET https://api.tomba.io/v1/email-verifier, drop timeout, and set a client timeout of at least 180 seconds.
  3. Replace checks of result: "error" with HTTP status handling: 402, 422, 429 with Retry-After, 408, and 451.
  4. Translate result and resultcode with the status mapping, comparing status case-insensitively.
  5. Replace file uploads with verifier bulk jobs: create, launch, receive the webhook_url event instead of the file_ready webhook, 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
NeverBounceBounceBan
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