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 Prospeo

This guide maps the Prospeo API (Enrich Person, Bulk Enrich Person, Enrich Company, Bulk Enrich Company, Search Person, Search Company, and Account Information) to Tomba. Prospeo API behavior checked on 2026-09-29 against the Prospeo API documentation.

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.
  • Prospeo's Enrich Person takes whichever datapoints you have. Tomba has one endpoint per input: a name and company, a LinkedIn URL, or an email address. Route each call by the datapoint you send.

Endpoint mapping

Replace the host api.prospeo.io with api.tomba.io.

ProspeoTombaNotes
POST /enrich-person with a name and companyGET /v1/email-finder
POST /enrich-person with linkedin_urlGET /v1/linkedin
POST /enrich-person with emailGET /v1/enrich
POST /enrich-person with only_verified_mobileGET /v1/phone-finderAccepts an email address, a LinkedIn URL, or a domain.
POST /bulk-enrich-personBulk jobs of type finder, linkedin, or enrichSee Bulk and async jobs.
POST /enrich-companyGET /v1/companies/findLooks up by domain only.
POST /bulk-enrich-companyBulk jobs of type company
POST /search-person filtered by company websiteGET /v1/domain-searchReturns people with their email addresses, one domain per request.
POST /search-companyPOST /v1/reveal/searchUses Tomba's own filters.
POST /search-suggestionsNo equivalent
GET /account-informationGET /v1/meSee Check usage.
Older /email-finder, /domain-search, and /email-verifier pathsGET /v1/email-finder, GET /v1/domain-search, GET /v1/email-verifier

Authentication changes

Prospeo reads the key from the X-KEY header. Tomba needs two headers, X-Tomba-Key and X-Tomba-Secret, and its lookups are GET requests with query parameters instead of POST requests with JSON bodies:

TerminalCode
# Prospeo curl -X POST "https://api.prospeo.io/enrich-person" \ -H "X-KEY: $PROSPEO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"only_verified_email": true, "data": {"full_name": "Jane Doe", "company_website": "stripe.com"}}' # Tomba curl -G "https://api.tomba.io/v1/email-finder" \ --data-urlencode "full_name=Jane Doe" \ --data-urlencode "domain=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

Prospeo fieldTomba parameterNotes
data.first_name, data.last_name, data.full_namefirst_name, last_name, full_nameOn /v1/email-finder.
data.company_websitedomain
data.company_namecompany
data.company_linkedin_urlNo equivalentSend domain or company.
data.linkedin_urlurlOn /v1/linkedin.
data.emailemailOn /v1/enrich.
data.person_idNo equivalent
only_verified_emailNo equivalentFilter on data.verification.status; see Status mapping.
enrich_mobileenrich_mobileAdds phone numbers in data.phone_data, at an extra cost.
only_verified_mobileNo equivalentUse /v1/phone-finder.
Enrich Company data.company_websitedomainOn /v1/companies/find.
Enrich Company data.company_name, data.company_linkedin_url, data.company_idNo equivalentGet the domain for a company name with GET /v1/domain-suggestions.
Search Person filters.company.websites.includedomainOn /v1/domain-search, one domain per request.
Search pagepage

Response field mapping

Tomba wraps every result in data. For Enrich Person calls answered by /v1/email-finder, /v1/linkedin, or /v1/enrich:

ProspeoTombaNotes
person.email.emaildata.emailnull when no address is found.
person.email.statusdata.verification.statusSee Status mapping.
person.email.revealed, verification_methodNo equivalent
person.email.email_mx_providerNo equivalentThe email verifier returns data.email.smtp_provider.
person.first_name, last_name, full_namedata.first_name, .last_name, .full_name
person.linkedin_urldata.linkedin
person.current_job_titledata.position
person.location.country_codedata.country
person.location.country, state, city, time_zoneNo equivalent
person.mobiledata.phone_dataReturned with enrich_mobile=true. See Phone.
person.person_id, headline, job_history, skillsNo equivalent
company.name, company.domaindata.company, data.website_url
free_enrichmentNo equivalentRepeating a request within your usage window is free; see Duplicate requests.

For Enrich Company calls answered by /v1/companies/find, the company is in data:

Prospeo companyTombaNotes
name, domain, descriptiondata.name, data.domain, data.description
employee_rangedata.metrics.employeesA range, such as 51-200.
employee_countNo equivalent
industryNo equivalentGET /v1/domain-search returns it in data.organization.industries.
foundeddata.foundedYearA string.
location.country, country_code, state, citydata.geo.country, .countryCode, .state, .city
linkedin_url, twitter_url, facebook_urldata.linkedin.handle, data.twitter.handle, data.facebook.handleHandles, not URLs.
technology.technology_namesdata.tech
sic_codes, naics_codesdata.category.sic4Codes, data.category.naics6Codes
phone_hqdata.site.phoneNumbers
logo_urlNo equivalentUse https://logo.tomba.io/{domain}; see Logo API.
revenue_range, funding, job_postings, keywordsNo equivalent

Field definitions are in Enrichment.

Status mapping

Prospeo email.statusTomba
VERIFIEDdata.verification.status is valid
UNAVAILABLEdata.email is null, or data.verification.status isn't valid

Tomba returns its best match with a status, including catch-all (accept_all) and unconfirmed (unknown) addresses. If you sent only_verified_email: true, keep only results whose status is valid. Compare status case-insensitively. Each value is defined in Status values.

Error mapping

Prospeo returns errors with HTTP 400 and an error_code. Tomba uses a distinct HTTP status for each cause, with an errors object:

Prospeo error_codeTombaWhat to do
NO_MATCH200 with data.email nullTreat as no match. /v1/companies/find returns 200 with an errors body, type not_found.
INVALID_DATAPOINTS, INVALID_REQUEST422 params_invalidFix the parameter named in the message.
INSUFFICIENT_CREDITS402 quota_exceededWait for your usage window to renew or add credits.
INVALID_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.
INTERNAL_ERROR500 api_errorRetry with backoff.
429 rate limit429 rate_limitRetry after the Retry-After delay; see Handle 429 responses.
No equivalent400 unknown_recordThe email finder received a disposable or webmail domain.
No equivalent451 claimed_emailThe owner of the address asked Tomba to stop processing it. Remove it from your data.

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

Bulk and async jobs

Prospeo's bulk endpoints answer up to 50 records in one synchronous response. A Tomba bulk job runs in the background: create it, launch it, poll its progress, and download the results as CSV. For a few records, send single requests instead.

ProspeoTomba bulk type
Bulk Enrich Person with names and companiesfinder: a CSV file with name and domain columns. See Email finder.
Bulk Enrich Person with LinkedIn URLslinkedin: a JSON list of profile URLs. See LinkedIn finder.
Bulk Enrich Person with email addressesenrich: a JSON list of addresses. See Email enrichment.
Bulk Enrich Companycompany: a JSON list of domains. See Company enrichment.

The requests for each step are in Lifecycle, and webhook_url sends an event when a job ends; see Bulk job events. A job is charged when you first download its results; see Billing.

Code example

This function replaces an Enrich Person call made with a full name, a company website, and only_verified_email: true, and returns Prospeo's field names. 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, }; async function enrichPerson(fullName, companyWebsite) { const url = new URL("https://api.tomba.io/v1/email-finder"); url.searchParams.set("full_name", fullName); url.searchParams.set("domain", companyWebsite); 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}`, ); } // Like only_verified_email: true, return only addresses verified as valid. const found = body.data; if (!found.email || found.verification?.status?.toLowerCase() !== "valid") { return { error: true, error_code: "NO_MATCH" }; } return { error: false, person: { full_name: found.full_name, first_name: found.first_name, last_name: found.last_name, current_job_title: found.position || null, linkedin_url: found.linkedin || null, email: { status: "VERIFIED", email: found.email }, }, company: { name: found.company, domain: found.website_url }, }; } console.log(await enrichPerson("Jane Doe", "stripe.com"));

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 X-KEY.
  2. Route each Enrich Person call by its datapoint: name and company to /v1/email-finder, LinkedIn URL to /v1/linkedin, email address to /v1/enrich.
  3. Turn JSON bodies into query parameters: company_website becomes domain and company_name becomes company.
  4. Read data.email and data.verification.status, and keep only valid addresses where you used only_verified_email.
  5. Replace error_code handling with HTTP status handling: 402, 422, 429 with Retry-After, and 451.
  6. Move bulk enrichment to Tomba bulk jobs, or loop over single requests for small batches.
  7. Run the same sample of people and companies through both services and compare the results before you switch production traffic.
Last modified on September 30, 2026
Snov.ioFindymail
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