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
Phone finders
    OverviewLushaContactOutKasprRocketReach
Phone finders

Migrate from a phone finder

Each guide maps one provider's phone and mobile lookups to the Tomba Phone Finder and Phone Validator.

Guides

ProviderGuide
LushaMigrate from Lusha
ContactOutMigrate from ContactOut
KasprMigrate from Kaspr
RocketReachMigrate from RocketReach

What changes in every migration

AreaChange
AuthenticationEvery request sends X-Tomba-Key and X-Tomba-Secret headers. Tomba doesn't read keys from the query string. See Authentication.
InputsGET /v1/phone-finder takes an email, a LinkedIn profile URL in linkedin, or a company domain, alone or combined; send at least one. A domain returns the company's number, not a person's. The phone finder doesn't take a name: look up a person by name and company with the email finder and enrich_mobile=true.
Phones on finder endpointsSet enrich_mobile=true on GET /v1/email-finder, GET /v1/linkedin, GET /v1/enrich, GET /v1/domain-search, or GET /v1/email-verifier to get the person's numbers in phone_data with the rest of the result.
ResultsThe phone finder returns one number in data, preferring a valid one. Set full=true to get an array of every number found. When nothing is found, the response is 200 with data as an empty array.
ResponseEach number comes in E.164, international, national, and RFC 3966 formats, with its country, line type, carrier, region, and time zones. See Phone response.
ValidationCheck a number you already have with GET /v1/phone-validator. A number that isn't valid returns 200 with an empty data array.
Withheld dataA claimed email address or LinkedIn profile sent to the phone finder returns 451 claimed_email or 451 claimed_linkedin, and claimed numbers are left out of its results. The phone validator returns 451 claimed_phone for a claimed number. See Status codes.
BillingThe phone finder's cost depends on whether you send domain, and phone numbers returned with enrich_mobile=true cost extra. See Credit costs.
ListsRun a bulk job: phone-finder takes email addresses, LinkedIn URLs, or domains, and phone-validator takes phone numbers. Create the job, launch it, poll its progress, and download a CSV. See Phone finder and Lifecycle.
Last modified on September 30, 2026
SkrappLusha
On this page
  • Guides
  • What changes in every migration