What is people data API?
A people data API is an HTTP interface that returns professional profiles on request: look up one person by LinkedIn URL, email or phone, or search people by title, company, seniority and location. Products call it to embed person data.
Also called: person data API · person enrichment API · people search API
People data API in practice
The API has two verbs. Lookup takes a key and returns one profile: name, title, employer, work history, education, skills, location. Search takes filters and returns a list of matching people, usually with totals so you can size a market before paying for the rows.
Contact channels are separate calls on the same person, because they are priced and verified differently from profile fields. A typical flow is search, then lookup for detail, then a mobile or email lookup for the people you want to reach.
How a people data API call works
- AuthenticateSend your API key in a header. Keys are created in the web app.
- Search or look upSearch by filters (title, company, location), or look up one person by LinkedIn identifier, email or phone.
- Read the profileRoles newest first, education, skills, location, and the identifiers to use in the next call.
- Add contact channelsPass the person identifier to the mobile, work email or personal email lookup.
Core endpoints of Forager's people API
| Field | Definition | Example | Forager field | Where |
|---|---|---|---|---|
| People search | Find people by role filters | title = "VP Sales", country = US | person_role_search | API (1 credit per request) |
| Person lookup | One full profile by identifier | linkedin.com/in/example | person_detail_lookup | API (1 credit per request) |
| Reverse email lookup | Profile from an email | name@employer.example | person_detail_reverse_lookup/by_email | API (5 credits per request) |
| Totals | Count of matches before paying for rows | 4,120 people | person_role_search/totals | API |
Example values are illustrative, not records.
People data API vs people data feed
| API | Feed | |
|---|---|---|
| Shape | One request, one answer | Whole dataset as files |
| Billing | Credits per request or per result | Licence, priced per record set |
| Best for | Lookups inside a product, at the moment of need | Search, models and matching in your own warehouse |
| Freshness | Current record at call time | As of each delivery |
Limits and when not to use it
- Search filters match the provider's taxonomy. Use the autocomplete endpoints to find valid IDs for industries, locations and skills before filtering.
- An API suits one-at-a-time and batch use inside a product. Building a search index over a whole market needs a feed.
- Rate limits apply. Production code should retry on 429 with backoff and cache what it already fetched.
How people data API works with Forager
Forager's people API covers 800M+ people: people search (1 credit per request), person lookup from a LinkedIn URL, email or phone (1 credit per request), reverse email lookup (5 credits per request) and contact lookups on top, charged per result found.
- People search
- Person enrichment
- Recipe: prospect contacts at a target domain by title and country via API
- Docs: people search API reference
- $5 free credits
- No credit card
- Run your sample
Questions about people data API
What is a people data API?
An HTTP interface that returns professional profiles: look up one person by LinkedIn URL, email or phone, or search people by title, company, seniority and location. Products call it to embed person data.
What is the difference between people search and person lookup?
Search takes filters and returns a list of matching people with totals. Lookup takes one identifier and returns that person's full profile. Most flows search first, then look up the people they want.
What fields does a person profile contain?
Name, current title and employer, past roles newest first, education, skills, location and the identifiers used for contact lookups. Contact channels are separate calls.
How is Forager's people API priced?
Credits per request: 1 credit per people search, 1 credit per person lookup, 5 credits per reverse email lookup. Mobiles and emails are charged per result found.
How do I get an API key?
Create a Forager account, create an API key in the web app and start with $5 in credits. The quickstart in the docs makes a first request in a few minutes.
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
Keep reading
How-to guides
Related terms
Sources
- Forager docs: people search API (read Nov 1, 2026)
- Forager docs: person lookup API (read Nov 1, 2026)
- Forager docs: errors and rate limits (read Nov 1, 2026)