People Data Labs API review
Best for building on top of
GET /v5/person/enrich?profile=linkedin.com/in/example X-Api-Key: $PDL_KEY # rate limits are per key, fixed window, per endpoint # x-ratelimit-remaining.minute tells you where you are # free plan returns contact data obfuscated
The People Data Labs API is the most expensive thing in this directory per record, at roughly $0.28 against Apollo's $0.0196, and the gap is not a mistake. You are not buying a lookup, you are buying a data license. PDL is the provider here whose terms are written for you to redistribute enriched records inside a product you sell to other people.
That one fact decides almost every evaluation. If the rows are read by your own reps, you are paying fourteen times the rate for a right you will never exercise, and you will eventually notice. If the rows appear inside something you charge for, the shortlist is one name long and the rate card stops being the question.
Mechanically it is a clean API. Key in a header, a free tier to test on, per-endpoint rate limits you can read out of the response headers, and a dataset that covers person and company records rather than just contact details.
The rest of the category is in the Enrichment APIs listing.
What a call costs, endpoint by endpoint
Person enrichment is the endpoint this page prices: one credit, one record returned, addressed by profile URL or an identity pair. The console above is the call. Everything below is from People Data Labs' own documentation, read on 8 October 2026.
| Call | What it costs | What it is for |
|---|---|---|
| Person enrichment | One credit, $0.28 on the Self-Serve floor | The identity call behind every row this page prices |
| Free-plan calls | Credits still count, but contact fields return obfuscated | Wiring tests and response-shape checks, not match-rate evaluation |
| License feeds | Contract priced | The Enterprise line, which is where redistributing data inside a product actually runs |
Rate limits are per API key with a fixed window per endpoint, and the x-ratelimit-remaining response headers tell you where you stand mid-burst. PDL publishes no central number: your limits arrive with your key.
People Data Labs API pricing, plan by plan
People Data Labs API pricing has three tiers and only one of them has a number attached. Credits are the unit, and a credit is a record returned.
Free
- Full access to the Person APIs for testing
- Contact data is obfuscated, so emails and phones are masked
- No commitment, sign up and go
Self-Serve
- Contact data included and unmasked
- Access to premium fields
- Monthly or annual subscription
- CSV enrichment and email support
Enterprise
- Custom volumes and annual contracts
- Access to all APIs, plus Data License Feeds
- Formal data testing before you commit
- Additional field bundles
At the Self-Serve floor, $98 for 350 credits is $0.28 a record. That rate improves with volume, and Enterprise is where bulk loads and the Data License Feeds live, which is the product if you want the dataset in a warehouse rather than a row at a time. PDL states it is ISO and SOC 2 Type 2 compliant on the same page.
The free plan gives you 100 credits a month and masks emails, phones and addresses. You can test the shape of the response, the match logic and your own code against it, but you cannot measure contact-data quality without paying. That is a reasonable thing for PDL to protect and an awkward one for an evaluation, because contact-data quality is the thing you are evaluating. Budget a paid month for the real test.
Per key, per endpoint, and visible in every response
People Data Labs API rate limits are defined per API key using a fixed window, which means a 100-per-minute limit is 100 calls at any interval inside the 60 seconds rather than a smoothed rate. Limits for every endpoint are separate, so a search loop does not slow an enrichment loop.
The headers that tell you where you are
PDL returns your position on every response, which removes the guesswork.
- x-ratelimit-limit.minute and x-ratelimit-remaining.minute on every endpoint.
- x-ratelimit-remaining.day, on the Autocomplete API only.
- x-ratelimit-remaining.month, on the Company Cleaner API only.
- x-ratelimit-reset, a UTC timestamp for when the window rolls.
Where your own numbers are
The published figures vary by plan, so the response is the authority.
- The API dashboard at dashboard.peopledatalabs.com shows your limits.
- The same headers also carry your credit usage, so one response answers both questions.
- Read the header rather than hard-coding a number, because yours depends on your contract.
Fixed-window limiting means your whole minute's allowance is available at the top of the window and gone until it rolls. A client that fires everything at once will succeed and then stall; one that paces evenly will never notice the limit exists. Neither is wrong, but if you are measuring throughput over a short test, the fixed window will flatter you.
Limits reported in the response headers rather than published as a number is the right design and it means you have to read them. Instrument the headers on the first run rather than inferring a ceiling from how fast things felt, because the figure differs per key and per endpoint and it is the only place either number appears.
How to create a People Data Labs API key
A People Data Labs API key comes from the dashboard and goes in a header. There is no OAuth and no per-endpoint scoping, so the key is the whole of your authentication model and should be treated accordingly.
How it travels
One header, every endpoint.
- Sent as X-Api-Key: <your key>.
- Issued and managed at dashboard.peopledatalabs.com.
- Rate limits are per key, so a second key is a real way to isolate a noisy job.
- Credit usage is reported against the key in the response headers.
Before you commit
Two things worth doing on the free tier first.
- Check the response shape against your schema, since PDL returns far more fields than most.
- Measure your match rate on obfuscated data, which still tells you whether a person was found.
- Read the license terms properly if the data is going anywhere near a customer.
The thing to settle before you commit is not the header name, it is the license. This is the one provider here whose terms are written for putting rows inside a product you sell, and that permission is most of what the price buys, so confirm your own use case against it while you still have the option of buying something cheaper.
Where the People Data Labs API documentation lives
PDL documents itself as a data product rather than a workflow tool, so the docs are organized by dataset and endpoint rather than by use case.
| Surface | Where | What it answers |
|---|---|---|
| Documentation | docs.peopledatalabs.com | Every API, the schema, and what each field means. |
| Rate limiting | docs.peopledatalabs.com/docs/rate-limiting | The fixed-window model and every header above. |
| Dashboard | dashboard.peopledatalabs.com | Your key, your limits and your credit usage. |
| Pricing | peopledatalabs.com/pricing | The three tiers, split by person and company data. |
The schema documentation is the part worth time before you build. PDL returns a much wider record than the email-and-phone providers here, and most of the value is in fields teams never map because they did not read what was in the response.
People Data Labs on video
The section is here either way, because the absence is worth knowing: a vendor with no walkthrough of its own API is a vendor whose docs are the only way in.
We read People Data Labs's own channel on 13 October 2026 and found nothing on it that walks through the API. The channel is the DaaS Cool podcast, plus a 22-second announcement that job posting data is now on the API. When People Data Labs publishes one, or sends us one, it goes here.
A vendor video is the vendor's claim about itself, which is why it sits in its own section.
Strengths and limits
PDL is a license with an API attached, and that is the right way to evaluate it.
What it does well
- Its terms are the most redistribution-friendly in the directory: written for putting enriched records inside a product you sell.
- A consistent schema across person and company records, rather than whatever a waterfall happened to return.
- Rate limits and credit usage reported in the headers of every response.
- Separate limits per endpoint, so one workload cannot starve another.
- ISO and SOC 2 Type 2 compliance stated on the pricing page, plus Data License Feeds for warehouse loads.
Where it falls short
- About $0.28 a record, which is roughly fourteen times Apollo's per-credit rate.
- The free tier obfuscates emails, phones and addresses, so you cannot measure contact quality without paying.
- $98 a month for 350 credits is a high floor for an evaluation.
- No OAuth and no key scoping, so the API key is your entire security model.
- Wrong tool for ordinary outbound, and expensive enough that the mistake is worth catching early.
Those two columns are a single decision wearing two hats. If the rows are going somewhere your customers can see, the license is worth every multiple of the per-record price; if they are not, you are paying fourteen times Apollo's rate for a permission you will never use.
Where People Data Labs data comes from, and what you may do with it
The question that arrives late and expensively is not how good the data is, it is who is allowed to hold it. These are the fields each one returns, the coverage it claims and the compliance it publishes.
| Provider | Fields returned | Coverage | Compliance | Redistribution |
|---|---|---|---|---|
| People Data Labs | Work email, Personal email, Mobile phone, Firmographics, LinkedIn profile | Global | GDPR DPA SOC 2 Type II CCPA | Not stated |
None of these states a redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first.
Two practical notes that apply to every provider on this page. A compliance badge describes the vendor, not your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And every one of these vendors runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs.
If People Data Labs is not the answer
Four providers in the Enrichment APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.
Apollo
$49/seat/moRoughly fourteen times cheaper per record, with search and sequencing in the same account. The right answer whenever the rows are read only by your own go-to-market team.
FullEnrich
$55/mo25 sources behind one call, charged only on a result. The move when coverage was the reason you were paying the premium.
LeadMagic
$99/moA published credit cost for every operation and credits deducted only on success, so finance gets a number rather than a range.
Clay
$167/moA router in front of about 150 providers if what you actually wanted was breadth. Billed in actions and data credits, so model both before you commit.
The full set, organized by the reason people leave, is on the People Data Labs alternatives page.
People Data Labs against the obvious rival
Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: Apollo vs People Data Labs, Clay vs People Data Labs and People Data Labs vs Clearbit. Every pairing in the directory is on the compare hub.
Apollo vs People Data Labs
CompareA go-to-market license at two cents a credit against a license written for redistribution.
Clay vs People Data Labs
CompareCoverage borrowed from 150 vendors against one dataset you are licensed to redistribute.
People Data Labs vs Clearbit
CompareOne of these is still a product you can buy.
Before you build against it
Four things to settle first, each one read off People Data Labs's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.
Who should actually buy this
Buy People Data Labs when enriched records are going to be seen by someone who is not your employee. A customer-facing directory, an enrichment feature inside your product, a dataset you resell: those are what the price is for, and no cheaper provider in this directory licenses you to do them.
The failure mode here runs one way and it is expensive. A team that picks PDL for ordinary outbound overpays and works it out within a quarter. A team that builds a product on a cheaper provider does not find out until an account is suspended, usually after the product has customers. If there is any chance the rows become customer-facing, that asymmetry should decide it rather than the rate card.
For internal go-to-market, almost anything else here is a better buy. Apollo is about fourteen times cheaper per record and the specialists are cheaper still, and none of that matters if the license is wrong.
One practical note for the case where PDL is right. Because the license is what you are buying, the sensible architecture keeps PDL rows separable from everything else you enrich: a field recording which provider resolved each record costs nothing to add and is the only way to answer the question that eventually arrives, which is whether a given row is one you are allowed to show a customer.
The license is the product. Read it before the rate card.
Most teams discover the redistribution question late, usually when legal asks where a row came from. Frontal designs the data layer with that answer built in, so the provider you picked still works when the output becomes customer-facing.
Worked with 300+ companies. A senior operator runs your account.
What People Data Labs users say, in their own words
The one part of this page that is not a vendor claim. Quotes are transcribed as written and linked to the thread.
The accuracy spread between vendors is smaller than the one inside your own list
it's nearly all the same at the end of the day... there's a marginal 5-10% difference between the vendors but overall 55-65% data accuracy / validity overall. [...] have a team of 20+ (or however many) outsourced data integrity workers through fiver or whatnot... it's what the rich tech companies like AirBnB and Uber do to have the most up to date data...
r/SalesOperations · November 2024 · 3 points
The range here lands on the assumption the waterfall stack on this site is modeled with, which is a 55% first pass. That figure is labeled as modeled on every page that uses it, because no provider in this category publishes a match rate you can hold it to, so an independent practitioner arriving at 55 to 65% is the closest thing to corroboration available. It also makes the case for the waterfall itself: if the best single source clears about 60%, the second provider is not a luxury.
The 5 to 10% spread between vendors is this commenter's estimate and nothing here verifies it, and the thread it comes from is a request for benchmarks that were never published. Read it as a reason to run your own test on your own rows rather than as a reason to skip one, and note that it argues against paying a premium for coverage claims, which is a different question from paying a premium for a redistribution license.
14 threads read on 13 October 2026, searched by vendor name. Scores and dates are the comment's own. Nothing here is the only source for a price or a limit on this site: every figure in the tables above comes from a vendor's own page.
People Data Labs API, answered
Is the People Data Labs API free?
Free plan, up to 100 credits per month with contact data obfuscated. Paid use starts at $98/mo.
How much does the People Data Labs API cost?
People Data Labs starts at $98/mo, which works out at $0.28 per record. Billing is subscription, credit packs and free tier. Read from People Data Labs's own pricing page on 8 October 2026.
What are the People Data Labs API rate limits?
Per key, fixed window, separate per endpoint. Reported in the response headers.
How do I get a People Data Labs API key?
API key in the X-Api-Key header. The current steps are in People Data Labs's own documentation, which is authoritative on anything that has changed since 8 October 2026.
Does People Data Labs have an MCP server?
Not one its own documentation describes, at the time of writing. People Data Labs ships REST API, Bulk or async, Native in Clay and n8n node instead.