canonical: https://jentic.com/apis/peopledatalabs.com/peopledatalabs # People Data Labs API Enrich, search, and retrieve person and company records from a dataset of over 3 billion profiles. The API supports person enrichment by name, email, phone, or social profile, company enrichment by domain, and SQL-like search queries across the full dataset. Additional endpoints handle IP-to-company resolution, job title standardisation, skill normalization, and autocomplete for fields like companies, schools, and locations across 21 operations. ## For AI agents Enrich person and company records, search a 3+ billion profile dataset with SQL-like queries, and resolve IPs to companies. Supports enrichment by email, phone, name, LinkedIn, and domain. ## Scope Does not handle email sending, CRM workflow automation, or marketing campaign management - use for person and company data enrichment and search only. ## Capabilities - Enrich person profiles from email, phone, LinkedIn URL, or name plus company combination - Search the full person dataset using SQL-like queries with boolean filters on 100+ fields - Look up company firmographics including size, industry, funding, and tech stack by domain - Resolve IP addresses to the company operating from that network - Standardise free-text job titles to canonical titles and seniority levels - Normalize skill descriptions into structured skill taxonomy entries - Autocomplete partial inputs for companies, schools, locations, and job titles ## Use cases ### AI Agent Lead Enrichment via Jentic AI agents building prospect lists can search People Data Labs through Jentic to enrich sparse lead data into full profiles. Given an email or LinkedIn URL, the agent retrieves job title, company, seniority, location, skills, and social links - enabling automated lead scoring and outreach personalisation without manual research across multiple platforms. Example prompt: Search Jentic for 'enrich person by email', load the People Data Labs /v5/person/enrich schema, and submit a GET with email 'jane.smith@acme.com' to retrieve her full professional profile ### Targeted Prospect Search with SQL Queries Sales and recruiting teams find ideal candidates or accounts by querying the full People Data Labs dataset using SQL-like syntax. Filter by job title, company size, location, industry, skills, and seniority across 3+ billion records. Results include full enriched profiles ready for outreach, with pagination supporting bulk list builds. Example prompt: POST to /v5/person/search with SQL query "SELECT * FROM person WHERE job_title='CTO' AND location_country='united states' AND job_company_size='501-1000'" and retrieve the first 10 results ### IP-to-Company Resolution for Website Visitors Marketing and sales platforms identify anonymous website visitors by resolving their IP addresses to company records. The /v5/ip/enrich endpoint maps an IP to the company operating from that network, returning firmographic data that powers account-based marketing triggers and personalised website experiences. Example prompt: GET /v5/ip/enrich with ip='203.0.113.42' and retrieve the company name, domain, industry, and employee count associated with that IP address ### Company Enrichment for Account-Based Sales Account executives research target companies by passing a domain to the company enrichment endpoint. The API returns industry, employee count, revenue estimates, tech stack, funding history, and headquarters location, giving reps the context they need to personalise outreach and qualify accounts. Example prompt: GET /v5/company/enrich with website='stripe.com' and retrieve the company name, industry, employee count, funding total, and headquarters location ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /v5/person/enrich | Enrich a person record from identifiers | | POST | /v5/person/search | Search persons with SQL-like queries | | GET | /v5/person/identify | Identify a person from partial data | | GET | /v5/company/enrich | Enrich company data by domain or name | | POST | /v5/company/search | Search companies with SQL-like queries | | GET | /v5/ip/enrich | Resolve an IP address to a company | | GET | /v5/autocomplete | Autocomplete partial field values | | GET | /v5/job_title/enrich | Standardise a free-text job title | ## Key resources - **Person Records** — Enrich, search, identify, and retrieve person profiles with 100+ data fields - **Company Records** — Enrich and search companies by domain, name, or firmographic criteria - **IP Enrichment** — Resolve IP addresses to the associated company - **Data Cleaning** — Standardise company names, school names, locations, job titles, and skills ## Why Jentic - **Setup:** Wiring People Data Labs by hand means setting the X-API-Key header and constructing its Elasticsearch-style search bodies for person and company queries yourself. Through Jentic you install once, import the People Data Labs API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** People Data Labs takes most query criteria in the request body or query string for search and enrich, so scoping is operations-only: limit the agent to the operations it needs, such as person enrich and company search, and leave the others out of the allowed set unless you add them. - **Credential handling:** Your People Data Labs API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find people by job title and location', and Jentic returns the matching People Data Labs operation with its input schema so the agent builds the query correctly without browsing the reference docs. ## Related APIs - **FullContact Enrich API** — Identity resolution and contact enrichment with a multi-identifier graph approach - **Hunter API** — Discovers and verifies professional email addresses by domain, feeding enrichment workflows - **Clearbit Logo API** — Retrieves company logos by domain to visually complement PDL firmographic data ## FAQ ### What authentication does the People Data Labs API use? The API uses an API key passed in the X-API-Key header on every request. Through Jentic, this key is stored encrypted in the credential vault and injected automatically - agents authenticate without handling raw keys. ### Can I search for people by job title and location with the People Data Labs API? Yes. The /v5/person/search endpoint accepts SQL-like queries. For example: SELECT * FROM person WHERE job_title='Data Engineer' AND location_country='united states'. You can filter on 100+ fields including skills, company size, industry, and seniority. ### What are the rate limits for the People Data Labs API? Rate limits vary by plan. The free tier allows 100 person enrichments per month. Paid plans offer higher throughput with per-minute rate limits documented in your account dashboard. Bulk endpoints like /v5/person/retrieve/bulk support up to 100 records per request. ### How do I enrich a person through Jentic? Install the SDK with pip install jentic and search for 'enrich person from email'. Jentic returns the People Data Labs /v5/person/enrich operation schema. Pass identifiers like email, LinkedIn URL, or name+company as query parameters and Jentic handles auth and execution. ### Can I resolve an IP address to a company using this API? Yes. The /v5/ip/enrich endpoint accepts an IP address and returns the company operating from that network, including company name, domain, industry, and size. This is useful for identifying anonymous website visitors at the account level. ### What is the difference between person/enrich and person/identify? The /v5/person/enrich endpoint requires enough identifiers to match a single record and returns a full profile. The /v5/person/identify endpoint works with less data and returns multiple candidate matches ranked by confidence score, useful when you have sparse input data. ### Can I limit what my agent is allowed to do with the People Data Labs API? Yes. Because you run Jentic One yourself, your own rules decide which People Data Labs operations the agent may call and which stored credential it uses. Since People Data Labs takes its search and enrich criteria in the request body or query string, scoping is done at the operation level: you allow only the operations the agent needs, such as person enrich and company search, and leave others like IP enrich or SQL person search out of the allowed set. Any operation you do not add stays off limits to the agent.