$5 free Limited time. Sign up to activate. Get your $5 →
Industry · B2B data providers

Mobile number API for B2B data providers

Reach the right person.

What B2B data providers teams need from mobile numbers, what Forager returns, and how teams like yours test it.

6 recipes use mobile numbers for B2B data providers teams.

  • $5 free credits
  • 800M+ people
  • 65M+ companies

A selection of teams in B2B data providers using Forager for mobile numbers · plus other teams using mobile numbers

  • Nooks
  • Amplemarket
  • Clay
  • Airscale
  • Orbital
  • BetterContact
  • HubSpot
  • Intro
For B2B data providers teams
The job
Raise mobile and contact coverage inside a contact-data product by blending a complementary source behind existing data.
When
The vendor's customers report missing mobiles in target regions or segments.
Outcome
Same process for the vendor's customers, with more connected decision-makers.
Lead recipe 1

Back a sales-intelligence database with an additional mobile source

When to use it: The vendor's customers report missing mobiles in target regions or segments.

  1. Send records lacking a mobile to POST /person_contacts_lookup/phone_numbers/ in bulk
  2. Cross-validate returned numbers against the vendor's existing records
  3. Store results under the reseller licence with provenance
  4. Surface the blended number in the product and track connect feedback
InputsOutputs
vendor contact recordsphone_number
LinkedIn identifierstier
provenance
validation result
Lead recipe 2

Add a phone-validation layer to a contact-data product

When to use it: A record's phone number is about to be shown or exported, or is flagged by a user.

Show the steps
  1. Resolve the number with POST /person_detail_reverse_lookup/by_phone_number/
  2. Compare returned person name and organization to the stored record
  3. If mismatched, fetch a current number from POST /person_contacts_lookup/phone_numbers/
  4. Mark records validated, replaced or suppressed
InputsOutputs
stored phone numbermatch result
stored person name + organizationcurrent owner name
replacement phone_number
Open the recipe: Add a phone-validation layer to a contact-data product
Lead recipe 3

Power a self-serve, pay-per-found contact database with a licensed people feed

When to use it: A self-serve data vendor wants broader search coverage without building its own crawl.

Show the steps
  1. Load people_feed and company_feed into the search index
  2. Expose filters for industry, size, title and location
  3. On reveal, call /personal_emails/ and /phone_numbers/ and charge credits only when found
  4. Refresh the index on each feed delivery
InputsOutputs
people + company feedprospect list
user search filtersrevealed personal_email
phone_number
Open the recipe: Power a self-serve, pay-per-found contact database with a licensed people feed
Fields

Fields you get back

  • phone_number
  • tier
  • provenance
  • validation result
  • match result
  • current owner name
  • replacement phone_number
  • prospect list
  • revealed personal_email

From the workflows above. Full field reference: Mobile numbers and the Mobile numbers API reference.

Gold or Silver

Gold or Silver for B2B data providers teams: choose per request

Request Gold where a call has to connect and Silver where you want more reach. Silver includes every Gold number.

How the tiers work
Silver · Most coverage 9 credits Gold 15 credits
Who owns this

Who evaluates mobile numbers at B2B data providers teams, and what they are judged on

  • Product manager who owns the enrichment feature: judged on what users see when they open a record
  • Engineering lead integrating the API: judged on response time and errors they can route on
  • Partnerships or data lead managing vendors: judged on cost per valid result

A selection of teams in B2B data providers using Forager for mobile numbers · plus other teams using mobile numbers

  • Nooks
    • Power & parallel dialers

    Selected use case: mobile numbers inside their dialer.

  • Amplemarket
    • AI SDRs

    Selected use case: mobile numbers inside its contact waterfall.

  • Clay
    • GTM workflow builders

    Selected use case: Forager mobile numbers, emails and people data inside Clay tables.

  • Airscale
    • Waterfall enrichment

    Selected use case: a Forager step in its mobile number waterfall.

  • Orbital
    • Lead databases

    Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.

  • BetterContact
    • Waterfall enrichment

    Selected use case: a Forager step in its waterfall for mobile numbers.

  • HubSpot
    • CRM add-ons

    Selected use case: enriching contact and company records with people, company and job-posting data.

  • Intro
    • AI candidate sourcing

    Selected use case: phone numbers for outreach to passive candidates.

“Forager's great for accuracy, the numbers we get from them are consistently the highest grade for accuracy and confidence. They've earned our trust when connect rates matter most.”
OrbitalAaron JosephHead of BizOps
800M+people
65M+companies
How to test it

Test mobile numbers on your own sample

  1. Pull a sample. Take profiles your users looked up last week.
  2. Run it. Use a self-serve key, or book a demo and send us the list.
  3. Measure what your users feel. Connect rate for mobiles, bounces for emails, and whether the right person answers.
  • $5 free credits
  • No credit card
  • Pay per result
FAQ

Frequently asked questions

How do B2B data providers use Forager mobile numbers?

Raise mobile and contact coverage inside a contact-data product by blending a complementary source behind existing data. Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. This page walks through 3 workflows with the exact steps.

What do mobile numbers cost for B2B data providers?

Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. That is $0.20 per mobile number on Starter month to month and $0.15 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

Which B2B data providers workflows use mobile numbers?

Back a sales-intelligence database with an additional mobile source, add a phone-validation layer to a contact-data product and power a self-serve, pay-per-found contact database with a licensed people feed. Each is on this page with its trigger, steps and outcome.

How do I license mobile phone data for resale?

Send records lacking a mobile to POST /person_contacts_lookup/phone_numbers/ in bulk. Cross-validate returned numbers against the vendor's existing records.

What inputs does it take and what does it return?

You send CSV (name, company, LinkedIn URL, email), LinkedIn identifiers and local business record. You get back phone_number, tier, current owner name and fill status, from POST /person_contacts_lookup/phone_numbers/, as JSON.

Am I charged when no mobile number is found?

No. A mobile number lookup that finds nothing costs 0 credits, so you pay for mobile numbers we find. Search, enrichment and reverse lookups are the exception: they are charged per request.

Can B2B data providers test mobile numbers for free?

Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.

How can I check that a phone number still belongs to the right person?

Resolve the number with POST /person_detail_reverse_lookup/by_phone_number/. If mismatched, fetch a current number from POST /person_contacts_lookup/phone_numbers/.

How do you check data quality?

Forager ranked #1 of 10 in Clay's 2026 test of mobile data providers, by quality score: Clay's measure of how likely a dialled number reaches the right person. The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.

How is a mobile number lookup API different from a contact database?

A contact database sells access to a list, often by seat or by export. A lookup API answers one person at a time inside your product or workflow: you send the LinkedIn URL or email you already hold and get back a mobile number in one JSON response. With Forager a mobile number lookup that finds nothing costs 0 credits, so you pay for numbers, not for searches.

Where can I use Forager mobile numbers?

Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Everything else connects through the REST API with one API key.

Do I need a subscription?

Not to test: a free account comes with $5 in credits. To keep using mobile numbers, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.

Start building

Put people, company and job data your users can act on inside your product

Send us a list. We run it, show you what we find, then talk volume and terms.

  • $5 free credits
  • No credit card
  • Run your sample
Platforms and teams that build on Forager
  • Clay
  • Juicebox
  • Nooks
  • Andela
  • HubSpot
  • SeekOut