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 Skrapp

This guide maps the Skrapp API (the v2 finder, account, and list endpoints and the v3 verifier endpoints) to Tomba. Skrapp API behavior checked on 2026-09-30 against the Skrapp API reference.

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.
  • Set your HTTP client timeout to at least 180 seconds. Tomba returns the finished result in the response.

Endpoint mapping

Replace the host api.skrapp.io with api.tomba.io, and the /api/v2 and /v3 prefixes with /v1.

SkrappTombaNotes
GET /api/v2/findGET /v1/email-finder
POST /api/v2/find_bulkPOST /v1/bulk/finderSee Bulk and async jobs.
GET /v3/verifyGET /v1/email-verifier
GET /v3/verify with enrichGET /v1/enrichReturns the person and company for an address.
GET /v3/verify_bulkPOST /v1/bulk/verifierSee Email verifier.
GET /api/v2/accountGET /v1/meSee Check usage.
GET /api/v2/listGET /v1/leads_lists
GET /api/v2/list/:listId/leadsGET /v1/leads with listPages with page and limit instead of start and size.

Authentication changes

Skrapp reads the key from the X-Access-Key header. Tomba needs two headers, X-Tomba-Key and X-Tomba-Secret:

TerminalCode
# Skrapp curl "https://api.skrapp.io/api/v2/find?firstName=Jane&lastName=Doe&domain=stripe.com" \ -H "X-Access-Key: $SKRAPP_API_KEY" # Tomba curl "https://api.tomba.io/v1/email-finder?first_name=Jane&last_name=Doe&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

SkrappTombaNotes
Finder firstName, lastNamefirst_name, last_nameTomba also accepts full_name.
Finder domaindomainTomba returns 400 unknown_record for a disposable or webmail domain.
Finder companycompanyWhen you send both, Tomba uses domain.
Verifier emailemailA malformed address returns 422 params_invalid instead of a result.
Verifier enrichNo equivalentCall GET /v1/enrich for the person and company.
List leads listIdlist
List leads start, sizepage, limitTomba pages start at 1: page = start / limit + 1.
List leads kwNo equivalent

Response field mapping

Tomba wraps every result in data.

SkrappTombaNotes
Finder emaildata.emailnull when no address is found; the status is 200, not 404.
Finder accuracydata.scoreComputed differently. Recalibrate any threshold you apply to it.
Finder firstName, lastNamedata.first_name, data.last_name
Finder companyNamedata.company
Finder quality.statusdata.verification.statusnull when the address hasn't been verified. See Status mapping.
Finder quality.resultNo equivalentVerify the address with GET /v1/email-verifier for a result.
Verifier emaildata.email.emailAn empty string when the domain is disposable.
Verifier email_statusdata.email.statusSee Status mapping.
Verifier resultdata.email.resultSee Result values.
Verifier firstName, lastName, companyName, titledata.first_name, .last_name, .company, .position from GET /v1/enrich
Account credits.remaining, credits.totalGET /v1/meSee Check usage.

Tomba's email finder also returns full_name, position, linkedin, country, and the sources where the address was found; see Person. The verifier fields are in Email verifier response.

Status mapping

Skrapp email_statusTomba statusTomba result
validvaliddeliverable
catch-allaccept_allrisky
invalidinvalidundeliverable
unknownunknownrisky

Tomba also returns disposable, with an empty result, for a disposable domain. The email finder uses the same status values in data.verification.status. Compare status case-insensitively. Each value is defined in Status values.

Error mapping

Skrapp returns an error code, a message, and the remaining credits. Tomba returns an errors object with type, message, and code:

SkrappTombaWhat to do
400 missing or malformed parameter422 params_invalidFix the parameter named in the message.
401 invalid, missing, or revoked key400 authentication_failed (missing or malformed), 400 api_key_expired, 401 authentication_failed (wrong key or secret)Check both headers; rotate an expired key.
402 insufficient_credits402 quota_exceededWait for your usage window to renew or add credits.
404 no address found200 with data.email nullCheck data.email instead of the status.
429 rate limited429 rate_limitRetry after the Retry-After delay; see Handle 429 responses.
5xx500 api_errorRetry with backoff.

Also handle 451 claimed_email when the owner of an address asked Tomba to stop processing it. Error responses don't consume credits; every type is listed in Errors.

Bulk and async jobs

Skrapp's bulk finder takes up to 100 people in a JSON body and returns a job id to poll. Its bulk verifier takes up to 50 addresses per request and answers directly. Tomba runs both as bulk jobs:

Skrapp endpointTomba bulk type
POST /api/v2/find_bulkfinder: a CSV file or JSON data rows with name and domain or company columns. See Email finder.
GET /v3/verify_bulkverifier: a JSON list of addresses or a CSV file. See Email verifier.

Each job is created, launched, polled, and downloaded as CSV; see Lifecycle. Row limits are in Bulk types. To be notified when a job ends, set webhook_url; see Bulk job events. A job is charged when you first download its results; see Billing.

The tId you attach to each Skrapp row has no equivalent. Keep your own ID in an extra CSV column.

Code example

This function replaces a call to Skrapp's GET /api/v2/find and returns Skrapp's field names, or null where Skrapp returned 404. 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 -> Skrapp email_status. const SKRAPP_STATUS = { valid: "valid", accept_all: "catch-all", invalid: "invalid", unknown: "unknown", }; // Accepts Skrapp's parameters: firstName, lastName, and domain or company. async function find({ firstName, lastName, domain, company }) { const url = new URL("https://api.tomba.io/v1/email-finder"); url.searchParams.set("first_name", firstName); url.searchParams.set("last_name", lastName); if (domain) url.searchParams.set("domain", domain); if (company) url.searchParams.set("company", company); 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}`, ); } const found = body.data; if (!found.email) return null; const status = found.verification?.status?.toLowerCase(); return { email: found.email, accuracy: found.score, firstName: found.first_name, lastName: found.last_name, companyName: found.company, quality: { status: SKRAPP_STATUS[status] ?? null }, }; } console.log( await find({ firstName: "Jane", lastName: "Doe", domain: "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-Access-Key.
  2. Change the host and path prefixes, and rename firstName and lastName to first_name and last_name.
  3. Treat data.email null as not found instead of a 404.
  4. Translate email_status with the status mapping, comparing status case-insensitively, and call /v1/enrich where you used enrich=true.
  5. Handle 402 for exhausted credits, retry 429 after Retry-After, and drop addresses that return 451.
  6. Move find_bulk and verify_bulk batches to finder and verifier bulk jobs.
  7. Run the same sample of people and addresses through both services and compare the results before you switch production traffic.
Last modified on September 30, 2026
Voila NorbertOverview
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