Resell person and reverse-email enrichment through a developer data API

Give a developer-focused data API a pay-per-result person, company and email-to-person endpoint without building its own people graph.

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

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_lookup/, POST /organization_search/, POST /person_detail_reverse_lookup/by_email/ · Person enrichment 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.

How the data flows

3 inputs → Person enrichment + Company enrichment + Reverse email lookup + Personal emails → 4 fields sample data

01 · Inputs

Work email

lee@example.com

LinkedIn URL

linkedin.com/in/lee-sampler

Company domain

example.com

02 · Forager

Person enrichment + Company enrichment + Reverse email lookup + Personal emails POST /person_detail_lookup/

Match found

03 · Outputs

Lee SamplerVP Revenue Operations · Example Inc.

person profile: /in/lee-sampler
personal email: lee.s@example.net
match: true
name: Lee Sampler
title: VP Revenue Operations
mobile: +1 (312) 555-0107

4 fields in the responseexample data

Steps

Map the vendor's /enrich/person endpoint to POST /person_detail_lookup/ and its company endpoint to POST /organization_search/
Map email-in requests to POST /person_detail_reverse_lookup/by_email/
Add personal_email via /person_contacts_lookup/personal_emails/ for consumer-signup use cases
Normalise to the vendor's schema and bill developers per matched result

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. Map the vendor's /enrich/person endpoint to POST /person_detail_lookup/
# and its company endpoint to POST /organization_search/
r1 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body)
r2 = requests.post(f"{BASE}/organization_search/", headers=HEADERS, json=body)

# 2. Map email-in requests to POST /person_detail_reverse_lookup/by_email/
r3 = requests.post(f"{BASE}/person_detail_reverse_lookup/by_email/", headers=HEADERS, json=body)

# 3. Add personal_email via /person_contacts_lookup/personal_emails/ for
# consumer-signup use cases

# 4. Normalise to the vendor's schema and bill developers per matched result

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

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

# 3. 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

Generated from the recipe stepsRequest fields: API reference

Run it yourself: Person enrichment 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
email	`person profile`
profile URL	`company profile`
company domain	`personal_email`
	`match (bool)`

Questions about this recipe

Which provider can power a reverse email lookup API I resell?

This recipe uses Forager Person enrichment, Company enrichment, Reverse email lookup and Personal emails. Person enrichment: A full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels. Give a developer-focused data API a pay-per-result person, company and email-to-person endpoint without building its own people graph.

What does it cost to resell person and reverse-email enrichment through a developer data API?

Person enrichment: 1 credit per request, charged whether or not data comes back. Company enrichment: 1 credit per request, charged whether or not data comes back. Reverse email lookup: 5 credits per request, charged whether or not data comes back. Personal emails: 5 credits per personal email found, and a personal email lookup that finds nothing costs 0 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 company domain, email and profile URL. You get back company profile, match (bool), person profile and personal_email, as JSON. You also need a Forager API key, which comes with a free account.

How do data API companies source person enrichment?

Map the vendor's /enrich/person endpoint to POST /person_detail_lookup/ and its company endpoint to POST /organization_search/. Map email-in requests to POST /person_detail_reverse_lookup/by_email/.

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 data API vendor sees demand for identity resolution (email in, person out) and person enrichment from its developer customers. The vendor's developer customers resolve sign-ups and CRM records to full profiles through one API.

Which Forager products does this recipe use?

Person enrichment, company enrichment, reverse email lookup and personal emails. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels. Company enrichment: firmographics for a company from its domain or name: industry, headcount, locations, growth and open roles.

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.

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: map the vendor's /enrich/person endpoint to POST /person_detail_lookup/ and its company endpoint to POST /organization_search/, map email-in requests to POST /person_detail_reverse_lookup/by_email/, add personal_email via /person_contacts_lookup/personal_emails/ for consumer-signup use cases and normalise to the vendor's schema and bill developers per matched result.

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.

Can we show Forager data inside 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.

A selection of teams that run this job on Forager · plus other teams on 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.
Bitscale
- GTM workflow builders
Selected use case: Forager in its contact waterfall for mobile numbers.
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 account¹
BetterContact
- Waterfall enrichment
Selected use case: a Forager step in its waterfall for mobile numbers.

Sources

¹ SeekOut: SeekOut, customer interview, Sep 2026.

Resell person and reverse-email enrichment through a developer data API

How the data flows

Steps

Inputs and outputs

Questions about this recipe

Which provider can power a reverse email lookup API I resell?

What does it cost to resell person and reverse-email enrichment through a developer data API?

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

How do data API companies source person enrichment?

Is there a free way to try Forager on this workflow?

When should I run this workflow?

Which Forager products does this recipe use?

How do I know the data is right?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

Can we show Forager data inside our product?

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

Add an additional email source to an email finder's lookup chain

Fill missing emails and mobiles in user-uploaded CSVs

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