Email verifiers
Migrate from an email verifier
Each guide maps one provider's single-address and list verification to the Tomba Email Verifier and bulk verifier jobs.
Guides
| Provider | Guide |
|---|---|
| NeverBounce | Migrate from NeverBounce |
| MillionVerifier | Migrate from MillionVerifier |
| BounceBan | Migrate from BounceBan |
| Bouncer | Migrate from Bouncer |
| Kickbox | Migrate from Kickbox |
| Hunter | Migrate from Hunter (email verifier) |
| ZeroBounce | Migrate from ZeroBounce |
| Emailable | Migrate from Emailable |
| Clearout | Migrate from Clearout |
| DeBounce | Migrate from DeBounce |
What changes in every migration
| Area | Change |
|---|---|
| Endpoint | A single check becomes GET https://api.tomba.io/v1/email-verifier?email=. A list becomes a bulk job of type verifier. |
| Authentication | Every request sends X-Tomba-Key and X-Tomba-Secret headers. Tomba doesn't read keys from the query string. See Authentication. |
| Response | The checks are in data.email. status is the detailed outcome and result the deliverability verdict; see Status values and Result values. Compare status case-insensitively. |
| Timing | Each request returns a final result: there's no timeout parameter, pending state, or result to poll for. Set your client timeout to at least 180 seconds. |
| Invalid input | A malformed address fails with 422 params_invalid instead of returning a result. |
| Errors | Out of credits is 402 quota_exceeded, throttling is 429 rate_limit with Retry-After, a withheld address is 451 claimed_email, and a failed mailbox check is 408 proxy_error. See Status codes. |
| Billing | Only some results are charged, and repeating a request within your usage window is free. See Credit costs and Duplicate requests. |
| Lists | Create and launch the job, poll its progress or receive its webhook_url event, and download a CSV. See Lifecycle. |
Last modified on