Test mobile and email coverage in the app before wiring the API

Let a waterfall or sales-tech platform's team check Forager's coverage on its own users' personas in the browser before an engineer builds the integration.

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Uses POST /person_contacts_lookup/phone_numbers/ · Mobile numbers API reference

What it costs: 15 credits per mobile found · 5 credits per email found. A mobile or email lookup that returns nothing costs 0 credits. Enrichment and search are charged per request: credit pricing.

How the data flows

One input → Prospecting web app + Mobile numbers + Work emails → 3 fields sample data

01 · Inputs

Company

Example Inc.

02 · Forager

Prospecting web app + Mobile numbers + Work emails POST /person_contacts_lookup/phone_numbers/

Match found

03 · Outputs

Sam SpecimenVP Revenue Operations · Example Inc.

name: Sam Specimen
title: VP Revenue Operations
mobile: +1 (512) 555-0133
work email: sam@example.com
company: Example Inc.

3 fields in the responseexample data

Steps

Search a sample of the platform's typical personas (titles, countries, company sizes) in the prospecting web app
Reveal mobiles and work emails for the sample and export them to CSV
Compare found rates and connect or bounce results with the current providers on the same people
If the source adds coverage, call POST /person_contacts_lookup/phone_numbers/ and /person_contacts_lookup/work_emails/ in the waterfall slot

import json, os, requests

BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage"
HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]}
body = json.load(open("request.json"))  # request fields: see the API reference

# 1. Search a sample of the platform's typical personas (titles, countries,
# company sizes) in the prospecting web app

# 2. Reveal mobiles and work emails for the sample and export them to CSV

# 3. Compare found rates and connect or bounce results with the current
# providers on the same people

# 4. If the source adds coverage, call POST
# /person_contacts_lookup/phone_numbers/ and
# /person_contacts_lookup/work_emails/ in the waterfall slot
r1 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 1. POST /person_contacts_lookup/phone_numbers/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/phone_numbers/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Generated from the recipe stepsRequest fields: API reference

Run it yourself: Mobile numbers API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
persona sample (titles, countries, company sizes)	`found rate on the sample`
	`mobiles and work emails`
	`CSV for comparison`

Questions about this recipe

How do I test a contact data provider before integrating it?

Compare found rates and connect or bounce results with the current providers on the same people. If the source adds coverage, call POST /person_contacts_lookup/phone_numbers/ and /person_contacts_lookup/work_emails/ in the waterfall slot.

What does it cost to test mobile and email coverage in the app before wiring the API?

The prospecting web app uses the same plan credits as the API: 15 credits per mobile and 5 per email found. Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 550 mobiles or 1,650 emails, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

What do I need to run this recipe, and what comes back?

You send persona sample (titles, countries, company sizes). You get back CSV for comparison, found rate on the sample and mobiles and work emails, as JSON. You also need a Forager API key, which comes with a free account.

How can I compare mobile coverage between data providers?

Reveal mobiles and work emails for the sample and export them to CSV. Compare found rates and connect or bounce results with the current providers on the same people.

Can I test the prospecting web app 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.

When should I run this workflow?

When a platform evaluates a new mobile or email source for its waterfall. The platform decides on a new source from its own sample, and engineering only builds what adds coverage.

Which Forager products does this recipe use?

Prospecting web app, mobile numbers and work emails. Prospecting web app: search people and reveal mobiles and emails in the browser, with no code. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you.

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.

Which tools can run this workflow?

Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Or call the endpoints in the steps above from your own code with one API key.

How many steps is this workflow?

4 steps: search a sample of the platform's typical personas (titles, countries, company sizes) in the prospecting web app, reveal mobiles and work emails for the sample and export them to CSV, compare found rates and connect or bounce results with the current providers on the same people and if the source adds coverage, call POST /person_contacts_lookup/phone_numbers/ and /person_contacts_lookup/work_emails/ in the waterfall slot.

Do I need a subscription?

Not to test: a free account comes with $5 in credits. To keep using Forager, 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.

Can our users see Forager data in our product?

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.

Test mobile and email coverage in the app before wiring the API

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How do I test a contact data provider before integrating it?

What does it cost to test mobile and email coverage in the app before wiring the API?

What do I need to run this recipe, and what comes back?

How can I compare mobile coverage between data providers?

Can I test the prospecting web app for free?

When should I run this workflow?

Which Forager products does this recipe use?

How do you check data quality?

Which tools can run this workflow?

How many steps is this workflow?

Do I need a subscription?

Can our users see Forager data in our product?

More recipes for waterfall enrichment

Add a mobile-number slot to a multi-provider enrichment waterfall

Convert personal-email sign-ups into work identities

Revive a dead CRM with a one-time contact refresh

Embed a validated email and mobile waterfall inside a SaaS product

Enrich and route inbound demo requests in real time

Add a premium phone reveal to a credit-based prospecting tool

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