People Data Labs Person API

Person enrichment, search, and identification operations.

Operations 12

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /v5/person/subjectrequest Download the list of opted-out person IDs · /v5/person/subjectrequest #
Ask an LLM
“Where can I get the PDL person IDs of people who opted out of the data?”
“Is there a CSV of opted-out profiles I should suppress from my records?”
Tell an agent
Download the CSV of person IDs that have opted out of People Data Labs data.
Fetch the opt-out subject request file so I can purge those person IDs from my copy.
GET /v5/person/enrich Enrich a person record with the v5 enrichment API · /person/enrich #
Ask an LLM
“Can I enrich a person by their PDL ID and get back only certain fields like names and emails?”
“What happens if I require that an enriched person record has a work email before it counts as a match?”
Tell an agent
Enrich PDL person {pdl_id} and include only the fields {data_include}.
Run v5 enrichment for {name} at {company}, and return a match only if it has {required}.
GET /v5/person/enrich/preview Preview a person enrichment match · /person/enrich/preview #
Ask an LLM
“Can I see a preview of a person record before paying for the full enrichment?”
“Is there a way to check whether someone would match without pulling their complete profile?”
Tell an agent
Get a preview record for the person with email {email} instead of the full enrichment.
Preview the enrichment match for {first_name} {last_name} in {locality}.
GET /v5/person/identify Recover all related profiles for an identity · /person/identify #
Ask an LLM
“How can I pull back every related profile for one identity using the v5 identify endpoint?”
“Can I identify all profiles tied to someone from their birth date and postal code?”
Tell an agent
Recover every related profile for the identity with email {email} using v5 identify.
Identify all profiles for {name} born {birth_date} living in postal code {postal_code}.
GET /v5/person/search Search the person dataset with a GET query · /person/search #
Ask an LLM
“Can I limit a v5 person search to a specific dataset category like mobile phones or emails?”
“How do I page through more than 10,000 person search results with a scroll token on a GET request?”
Tell an agent
Search people with SQL {sql} in the {dataset} dataset as a GET request.
Continue my GET person search using scroll token {scroll_token}.
POST /v5/person/search Search the person dataset with a POST query · /person/search #
Ask an LLM
“Can a POST person search return up to 1,000 people per page?”
“Which form of the v5 person search should I use for long Elasticsearch queries sent by POST?”
Tell an agent
POST the Elasticsearch query {query} to v5 person search and return {size} people, up to 1000.
Fetch the next batch of my POST person search with scroll token {scroll_token}.
GET /v5/person/retrieve/{person_id} Retrieve a person by PDL ID · /person/retrieve/ #
Ask an LLM
“How do I pull a single person record when I already have their PDL ID?”
“Can I skip a retrieved person if their record hasn't changed since I last asked?”
Tell an agent
Retrieve the person with PDL ID {person_id}.
Retrieve person {person_id} only if {filter_updated} changed since my last request.
POST /v5/person/retrieve/bulk Retrieve up to 100 people by PDL ID · /person/retrieve/bulk #
Ask an LLM
“Can I retrieve a batch of people at once when I already have their PDL IDs?”
“What's the most person IDs I can fetch in one bulk retrieve call?”
Tell an agent
Bulk retrieve these PDL person IDs in one call: {requests}.
Retrieve the person ID list {requests}, filtering out records where {filter_updated} has not changed.
GET /person/enrich Enrich one person's profile · Enrich a person profile #
Ask an LLM
“Can I get a full professional profile for someone from just their work email?”
“What does People Data Labs return when I enrich a person by phone number?”
Tell an agent
Enrich the person with email {email} and return their single best-matching profile.
Look up the full profile for {first_name} {last_name} who works at {company}.
GET /person/search Search people with an SQL or Elasticsearch query · Search for person profiles #
Ask an LLM
“How do I find every person who matches criteria like job title and location?”
“Can I write an SQL query to search the people dataset?”
Tell an agent
Search person profiles with the SQL query {sql}.
Run the Elasticsearch query {query} against person profiles and return {size} results.
GET /person/identify List likely person matches with likelihood scores · Identify a person #
Ask an LLM
“Which candidate people could this email belong to, ranked by how likely each one is?”
“Can I see several possible matches with scores instead of a single enriched profile?”
Tell an agent
Identify the likely people behind phone number {phone} and show each match score.
List every possible match for {first_name} {last_name} with their likelihood scores.
POST /person/bulk Enrich many person profiles in one request · Bulk person enrichment #
Ask an LLM
“Can I enrich a whole list of contacts at once instead of one call per person?”
“What's the way to batch person enrichment for a CRM export?”
Tell an agent
Bulk-enrich these people in a single request: {requests}.
Send my contact list {requests} as one batch person enrichment call.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/peopledatalabs:peopledatalabs-person-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

peopledatalabs-person-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Peopledatalabs Person API
  version: '1.0'
  description: 'Operations tagged Person across 2 of this provider''s published API definitions: peopledatalabs-docs-openapi.json, peopledatalabs-person-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.peopledatalabs.com
- url: http://api.peopledatalabs.com
- url: https://api.peopledatalabs.com/v5
  description: People Data Labs production API
tags:


# --- truncated at 32 KB (175 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/peopledatalabs/refs/heads/main/openapi/peopledatalabs-person-api-openapi.yml