Email finders
Migrate from an email finder
Each guide maps one provider's email finder, domain search, and related lookups to the Tomba Email Finder, Domain Search, and bulk jobs.
Guides
| Provider | Guide |
|---|---|
| Hunter | Migrate from Hunter (email finder) |
| Snov.io | Migrate from Snov.io |
| Prospeo | Migrate from Prospeo |
| Findymail | Migrate from Findymail |
| Apollo.io | Migrate from Apollo.io |
| Voila Norbert | Migrate from Voila Norbert |
| Skrapp | Migrate from Skrapp |
What changes in every migration
| Area | Change |
|---|---|
| Endpoints | Tomba has one endpoint per input: a name and company go to GET /v1/email-finder, a domain to GET /v1/domain-search, a LinkedIn URL to GET /v1/linkedin, an email address to GET /v1/enrich, and verification to GET /v1/email-verifier. |
| Authentication | Every request sends X-Tomba-Key and X-Tomba-Secret headers. There's no token exchange, and Tomba doesn't read keys from the query string. See Authentication. |
| Requests | Lookups are GET requests with query parameters, one person or domain per request. |
| Timing | Each request returns a final result: there are no task IDs to store or results to poll for. Set your client timeout to at least 180 seconds. |
| No result | The email finder returns 200 with data.email set to null. |
| Verification | The email finder returns its best match with a status in data.verification.status, including catch-all and unconfirmed addresses. See Status values. |
| 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 disposable or webmail domain sent to the email finder is 400 unknown_record. 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 | Run a bulk job: finder takes rows of names and companies, as JSON data or a CSV file, search a list of domains, and linkedin, enrich, and verifier either one. Create and launch the job, poll its progress or receive its webhook_url event, and download a CSV. See Lifecycle. |
Last modified on