Mobile number API for enrichment waterfalls

Give a waterfall or cascade product a mobile provider that returns dialable direct mobiles for people the earlier steps missed. 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.

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

Fill your waterfall’s top slot without paying for dead numbers. Products like yours are judged on connect rate and cost per valid result, which is why the cost that counts is per result that reaches the right person. Run your own sample to see what mobile numbers returns for your users before you build on it.

The workflow uses Forager Mobile numbers. Mobile numbers: Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Give a waterfall or cascade product a mobile provider that returns dialable direct mobiles for people the earlier steps missed.

You send LinkedIn URL, LinkedIn identifier and LinkedIn identifiers. You get back phone_number, role_title, work_email and organization, from POST /person_contacts_lookup/phone_numbers/, as JSON.

Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager contacts to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.

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.

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.

Call the embedded waterfall from the product's backend with linkedin_public_identifier or name + domain. Use /person_contacts_lookup/work_emails/ and /phone_numbers/ as steps with validation.

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.

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.

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.