Reach SMB owners who have no professional profile
Connect local-business records to owners' personal mobiles and emails when there is no professional profile to start from.
- Free API key
- No credit card
- Run your sample
A selection of teams that run this job on Forager · plus other teams on Forager
Uses POST /person_detail_reverse_lookup/by_email/, POST /person_contacts_lookup/phone_numbers/ · Reverse email lookup 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.
- Personal emails
- Mobile numbers
- Reverse email lookup
- API
- Data reseller
- B2B data providers
How the data flows
POST /person_detail_reverse_lookup/by_email/ - owner personal email
- jane.e@example.net
- owner phone number
- +1 (415) 555-0142
- name
- Jane Example
- title
- VP Revenue Operations
- work email
- jane@example.com
- company
- Example Inc.
Steps
- Start from known owner identifiers (business email, phone or name) on the local-business record
- Resolve with
POST /person_detail_reverse_lookup/by_email/or/by_phone_number/to the owner profile - Retrieve
personal_emailand mobile via/personal_emails/andPOST /person_contacts_lookup/phone_numbers/ - Attach to the business record and flag owner-reachable
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. Start from known owner identifiers (business email, phone or name) on # the local-business record # 2. Resolve with POST /person_detail_reverse_lookup/by_email/ or # /by_phone_number/ to the owner profile r1 = requests.post(f"{BASE}/person_detail_reverse_lookup/by_email/", headers=HEADERS, json=body) # 3. Retrieve personal_email and mobile via /personal_emails/ and POST # /person_contacts_lookup/phone_numbers/ r2 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body) # 4. Attach to the business record and flag owner-reachable
# 1. POST /person_detail_reverse_lookup/by_email/ curl -X POST \ https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_reverse_lookup/by_email/ \ -H "X-API-KEY: $FORAGER_KEY" \ -H "Content-Type: application/json" \ -d @request.json # 2. 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
Run it yourself: Reverse email lookup API reference
- Free API key
- No credit card
- Run your sample
Inputs and outputs
| Inputs | Outputs |
|---|---|
| local business record | owner personal_email |
| owner name / business email / phone | owner phone_number |
owner-reachable flag |
Questions about this recipe
How do I contact small business owners who have no professional profile?
Start from known owner identifiers (business email, phone or name) on the local-business record. Resolve with POST /person_detail_reverse_lookup/by_email/ or /by_phone_number/ to the owner profile.
What does it cost to reach SMB owners who have no professional profile?
Personal emails: 5 credits per personal email found, and a personal email lookup that finds nothing costs 0 credits. Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Reverse email lookup: 5 credits per request, charged whether or not data comes back. 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 local business record and owner name / business email / phone. You get back owner personal_email, owner phone_number and owner-reachable flag, as JSON. You also need a Forager API key, which comes with a free account.
What's the best data source for local business owners' mobile numbers?
This recipe uses Forager Personal emails, Mobile numbers and Reverse email lookup. Personal emails: Personal email addresses for reaching people outside their work inbox, such as passive candidates and founders. Connect local-business records to owners' personal mobiles and emails when there is no professional profile to start from.
Is there a free way to try Forager on this workflow?
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 local-business dataset has the business but not a reachable owner. SMB-focused sales teams talk to owners instead of front desks.
Which Forager products does this recipe use?
Personal emails, mobile numbers and reverse email lookup. Personal emails: personal email addresses for reaching people outside their work inbox, such as passive candidates and founders. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you.
How accurate is Forager data?
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 do I reach restaurant owners personal cell?
Start from known owner identifiers (business email, phone or name) on the local-business record. Retrieve personal_email and mobile via /personal_emails/ and POST /person_contacts_lookup/phone_numbers/.
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: start from known owner identifiers (business email, phone or name) on the local-business record, resolve with POST /person_detail_reverse_lookup/by_email/ or /by_phone_number/ to the owner profile, retrieve personal_email and mobile via /personal_emails/ and POST /person_contacts_lookup/phone_numbers/ and attach to the business record and flag owner-reachable.
Is there a contract or minimum commitment?
No contract to start: 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.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
A selection of teams that run this job on Forager · plus other teams on ForagerA selection of teams using Forager
-
Clay - GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
-
Juicebox
- AI candidate sourcing
Selected use case: Forager data behind its PeopleGPT search and sourcing agents.
-
Nooks - Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
-
Amplemarket
- AI SDRs
Selected use case: mobile numbers inside its contact waterfall.
-
HubSpot
- CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
-
SeekOut
- Talent intelligence
Selected use case: Forager’s people data feed, used to keep candidate profiles current.
2–3 years on the Forager people data feed, by SeekOut’s own account1
-
BetterContact - Waterfall enrichment
Selected use case: a Forager step in its waterfall for mobile numbers.
-
Intro
- AI candidate sourcing
Selected use case: phone numbers for outreach to passive candidates.
Sources
1 SeekOut: SeekOut, customer interview, Sep 2026.
More recipes for contact-data vendors
-
Back a sales-intelligence database with an additional mobile source
-
Launch a pay-per-valid-result phone finder on wholesale mobile data
-
Launch a regional B2B contact database on licensed people and jobs feeds
-
Bundle job-posting buying signals into a B2B data product
-
Resell person and reverse-email enrichment through a developer data API
-
Add an additional email source to an email finder's lookup chain