crustdata > APIs > People API
People API: search and enrich people in real time
Crustdata gives you two people APIs on one platform. The People Search API finds anyone across 1B+ profiles using 60+ filters. The People Enrichment API turns an email, name, or profile URL into a full profile. Both read the same data, indexed live from the public web, so a person you find and a person you enrich come back in the same shape.
Companies
People profiles
Search filters
Datapoints per person
The category
What is a people API?
A people API returns structured data about a person from a single programmatic request: their role, company, work history, education, location, and business email. Instead of assembling that by hand, you call an endpoint and get a clean record back.
Two jobs sit under that term, and Crustdata gives you an API for each:

Search
finds the people who match a description, such as title, seniority, company, location, or a recent job change.

Enrichment
takes a person you already know and fills in the rest of their profile.
You can use one or both. They run on the same underlying data, so lists you search and records you enrich stay consistent across your stack.
Two APIs, one platform
Two people APIs, one platform
See it ina code
Two endpoints, one workflow
Search finds the people who match your filters. Enrich turns a profile you already have into a full record. Same auth, same data, same x-api-version: 2025-11-01 header.

POST
/person/search
0.03 credits per result
curl --request POST \
--url https://api.crustdata.com/person/search \
--header 'authorization: Bearer YOUR_API_KEY' \
--header 'content-type: application/json' \
--header 'x-api-version: 2025-11-01' \
--data '{
"filters": {
"op": "and",
"conditions": [
{ "field": "experience.employment_details.current.title", "type": "(.)", "value": "VP Sales" },
{ "field": "basic_profile.location.country", "type": "=", "value": "United States" }
]
},
"limit": 5
}'

Response
{
"profiles": [
{
"crustdata_person_id": 97567,
"basic_profile": {
"name": "Jordan Lee",
"headline": "VP of Sales",
"location": { "raw": "San Francisco, California, United States" }
},
"experience": {
"employment_details": {
"current": [{ "name": "Example Corp", "title": "VP of Sales" }]
}
}
}
],
"next_cursor": "H4sIA...",
"total_count": 8421
}

POST
/person/enrich
1 credit per profile
curl --request POST \
--url https://api.crustdata.com/person/enrich \
--header 'authorization: Bearer YOUR_API_KEY' \
--header 'content-type: application/json' \
--header 'x-api-version: 2025-11-01' \
--data '{
"professional_network_profile_urls": ["https://
"fields": ["basic_profile", "experience", "education"]
}'

Response
[
{
"matched_on": "https://
"match_type": "professional_network_profile_url",
"matches": [
{
"confidence_score": 1.0,
"person_data": {
"crustdata_person_id": 14540,
"basic_profile": { "name": "Jane Doe", "current_title": "Founder, CEO" },
"experience": {
"employment_details": {
"current": [{ "name": "Example Corp", "title": "Founder, CEO", "start_date": "2023-02-01" }]
}
},
"education": {
"schools": [{ "school": "State University", "degree": "BS, Computer Science" }]
}
}
}
]
}
]
Note: by default enrich returns the basic profile and social handles. Request experience, education, and skills fields in at no extra credit.
What data you get
90+ datapoints per person
We reconcile 15+ sources into one record per person, indexed from the public web. You request only the fields you need, and you pay only for what matches.

●
One clean, consistent record whether you searched for the person or enriched them.

●
Every record carries a timestamp, so you always know how fresh it is.

One profile, six groups
Identity
Education
Employment
Contact
Company context
Signals
Reconciled from 15+ sources, indexed from the public web
Freshness, your choice
Choose real-time or database, per call
Most people APIs hand you a static dataset refreshed on their schedule, so a record can be months old before you read it. Crustdata gives you both modes on the same call:

●
Database returns an instant response from our maintained dataset of 1B+ profiles. Best for volume and cost.

●
Real-time pulls the current version from the public web at query time when a record is missing or stale. Best for accuracy on the people who matter.
You pick per request, so you are never locked into speed over freshness across your whole workload.
Coverage & sources
The data behind the People API
Our people data is indexed directly from the public web, not resold from a pre-licensed static dataset. That is why the profiles stay current.
What you can build
What teams build on the People API

Sales & GTM
Build targeted prospect lists and enrich them the moment they hit your CRM.
Sales solutions →

Recruiting
Source candidates by role, skills, and background, then verify and enrich your ATS.
Recruiting solutions →

Investors
Track founders and operators, and see who is on the move.
Investor solutions →

Product & PLG
Enrich signups in real time to route, score, and personalize.
PLG solutions →
How Crustdata compares
Our people data is indexed directly from the public web, not resold from a pre-licensed static dataset. That is why the profiles stay current.
Dimension
People profiles
Data freshness
Real-time retrieval from the web
Social posts & engagement
Crustdata
1B+
Real-time
Yes
Yes
Coresignal
780M
Monthly
No
No
PDL
1.5B
Monthly, 6-hour updates on select fields
No
Yes
Pricing
Simple, usage-based pricing
You pay per result. Search bills 0.03 credits per profile returned, and cached enrichment starts at 1 credit per profile, with contact data and live-from-the-web retrieval priced higher. Nothing is charged for a miss, and you start on free credits.
0.03 credits
per search result
1 credit
per cached enrichment
$0
charged for a miss

Get started
Build on people data that stays current
Get an API key and make your first call in minutes, or connect Crustdata to Claude over MCP and pull people data with no code.
Keep reading
Keep reading

Roundup
Best People Search APIs
How the major people APIs stack up, and where each one fits.
Read the roundup →


1
GET /v1/people/search
2
params:
3
response:
4
status: 200 OK
5
rate_limit: 1000 / min
Guide
People Search API guide
A practical walkthrough of searching people programmatically.
Read the guide →











