Add an additional email source to an email finder's lookup chain
Let an email-finder vendor return more found, verified addresses by adding an independent source to its lookup chain and refreshing its own index.
- 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_contacts_lookup/work_emails/ · Work emails API reference
What it costs: 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.
- Work emails
- Personal emails
- Person enrichment
- People data feed
- API
- Waterfall slot
- B2B data providers
How the data flows
POST /person_contacts_lookup/work_emails/ - work email
- sam@example.com
- personal email
- sam.s@example.net
- source
- forager
- found
- true
- name
- Sam Specimen
- title
- VP Revenue Operations
Steps
- Send not-found requests to
POST /person_contacts_lookup/work_emails/after the vendor's own index - Add
/person_contacts_lookup/personal_emails/for users who prospect founders or candidates - Use
people_feeddeliveries to detect job changes and re-verify emails in the vendor's index - Log per-source found rate and bounce rate to tune order
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. Send not-found requests to POST /person_contacts_lookup/work_emails/ # after the vendor's own index r1 = requests.post(f"{BASE}/person_contacts_lookup/work_emails/", headers=HEADERS, json=body) # 2. Add /person_contacts_lookup/personal_emails/ for users who prospect # founders or candidates # 3. Use people_feed deliveries to detect job changes and re-verify emails # in the vendor's index # 4. Log per-source found rate and bounce rate to tune order
# 1. POST /person_contacts_lookup/work_emails/ curl -X POST \ https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/work_emails/ \ -H "X-API-KEY: $FORAGER_KEY" \ -H "Content-Type: application/json" \ -d @request.json
Run it yourself: Work emails API reference
- Free API key
- No credit card
- Run your sample
Inputs and outputs
| Inputs | Outputs |
|---|---|
| name + company domain | work_email |
| profile URL | personal_email |
source | |
found (bool) |
Questions about this recipe
How do email finder tools increase the share of emails they find?
Send not-found requests to POST /person_contacts_lookup/work_emails/ after the vendor's own index. Add /person_contacts_lookup/personal_emails/ for users who prospect founders or candidates.
What does it cost to add an additional email source to an email finder's lookup chain?
Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Personal emails: 5 credits per personal email found, and a personal email lookup that finds nothing costs 0 credits. Person enrichment: 1 credit per request, charged whether or not data comes back. People data feed is a flat annual licence, global or regional, not priced in credits. Growth's 8,250 monthly credits cover 1,650 emails or 8,250 person enrichments, 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 name + company domain and profile URL. You get back found (bool), personal_email, source and work_email, as JSON. You also need a Forager API key, which comes with a free account.
Which work email API can an email finder add to its lookup chain?
This recipe uses Forager Work emails, Personal emails, Person enrichment and People data feed. Work emails: Verified work email addresses for a person at their current employer. Let an email-finder vendor return more found, verified addresses by adding an independent source to its lookup chain and refreshing its own index.
Can I test work emails 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?
An email finder's not-found rate climbs on a segment (new hires, small companies, a region) and users churn to competitors. The vendor's users get more found addresses and fewer bounces.
Which Forager products does this recipe use?
Work emails, personal emails, person enrichment and people data feed. Work emails: verified work email addresses for a person at their current employer. Personal emails: personal email addresses for reaching people outside their work inbox, such as passive candidates and founders.
How do I know the data is right?
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 add a source to email finder?
Send not-found requests to POST /person_contacts_lookup/work_emails/ after the vendor's own index. Add /person_contacts_lookup/personal_emails/ for users who prospect founders or candidates.
Which tools can run this workflow?
Native in Clay and Zapier, partner-built in Deepline and Cargo, delivered as a data share to Snowflake, Databricks and Amazon S3 and called through the API from Make, n8n, your own code and Google BigQuery. Or call the endpoints in the steps above from your own code with one API key.
How many steps is this workflow?
4 steps: send not-found requests to POST /person_contacts_lookup/work_emails/ after the vendor's own index, add /person_contacts_lookup/personal_emails/ for users who prospect founders or candidates, use people_feed deliveries to detect job changes and re-verify emails in the vendor's index and log per-source found rate and bounce rate to tune order.
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.
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.
-
Andela
- Customer
Selected use case: Forager data for the go-to-market team at a global talent marketplace.
-
Coram
- Internal use
Selected use case: mobile numbers for outbound calling.
-
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
-
Orbital - Lead databases
Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.
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
-
Fill missing emails and mobiles in user-uploaded CSVs