linkedin.com/in/…
fetch
One call, one record
You already know who
A profile URL in, the full record out. This is the documented call, and the one behind a lookup inside your product.
A profile URL or a work email in. A complete person out.
Full work history with start and end dates, the role descriptions, education and public activity — not a name and a current title. Matching runs at 99% on professional profiles, live or from the graph.
99%Match on professional profiles
920M+Professional profiles
2Input modes
18+Data sources
In production
Who already builds on it.
Platforms shipping their own products on these records today.
Two ways in
Start from a profile, or start from an email.
Same record either way. The difference is only what you happen to hold when you ask.
l.moreau@vertexlabs.com
resolve, then fetch
Same record, from an email99%
You only have an email
A work email in, the professional profile out, at 99%. This is identity resolution at the point of capture.
Freshness
How current do you need it?
The same record either way. You choose whether we go and get it at the moment you ask, or serve it from the graph we already keep current.
| Live | From the graph | |
|---|---|---|
| Freshness | Fetched at the moment you ask. | Served from the graph — 350M+ profiles refreshed every month, about 0.5M every hour. |
| Speed | Under 20 seconds per profile — it goes and gets it. | Under 5 seconds per profile. |
| Use it when | You are about to act on the answer — confirming a job change before a campaign or a routing decision. | You are enriching at volume — a backfill, a nightly refresh, or keeping a CRM current. |
What comes back
The fields that usually go missing.
Start and end dates, role descriptions and the link back to a company are the ones that decide whether an enriched record is usable or just decorated.
Identity
Name, location, current title and employer, and the public profile that anchors the record.
Work history
Every role with employer, title, start and end dates and the description — not only the current one.
Education
Institutions, degrees, fields of study and dates.
Public activity
Posts and comments carried on the person record, so you get what someone is saying, not only what they are.
Specialty attributes
Developer activity where the person is an engineer; specialty context where they are a clinician.
Company link
The person resolves to a company in the Company Dataset, so enrichment and firmographics line up.
How it works
Four steps, and the fourth is the one teams forget.
The first three are a single call. The fourth is why an enriched record is still right six months later.
- 01Send an identifierA profile URL, or a work email if that is all you hold.
- 0299% matchWe resolve itThe identifier is matched against the graph and reconciled across 18+ sources.
- 03Get one record backStructured JSON — full history with dates, education and public activity.
- 04Keep it currentRe-enrich the records that move, rather than the whole list.
The call
One endpoint. One record.
The documented People call, in full. The response is the same shape whether you asked for it live or from the graph — trimmed here to the fields that show what a record looks like.
Request01
POST /datasvc/candidate/fetch
{
"linkedin_url": [ "https://…/in/example" ]
}
Response03
{
"name": "L. Moreau",
"title": "VP Engineering",
"company": "Vertex Labs",
"since": "2021-04",
"roles": [ … 4 more, with dates ],
"education": [ … ]
}
How you take it
However your stack wants it.
Same record through every surface — the difference is only how many you ask for at once.
Real-time
Real-time API
Resolve at the moment of decision, one identifier at a time.
At volume
Batch
Submit a file of identifiers, poll for status, collect the results.
Agents
Skills and MCP
The same enrichment inside Claude and ChatGPT, and any tool that speaks them.
Try it
Ember
A visual layer over the same APIs. Enrich real records in a UI before anyone writes code.
Use cases
What teams do with it.
Every one of these is the same record, asked for at a different moment.
Your product · person view
No second tab
One lookup inside your product
A user opens a record and the profile is already complete — no research step, no second tab. For platforms with a person view.
form submit · work email
ResolvedVP Engineering
routed on role, not on domain
Before it reaches a rep
Resolve identity at capture
A work email arrives on a form and becomes a person before it reaches a rep. For lead capture and routing.
Batch job · 48,200 profiles
Submit, poll, collectasync
One pass, not one at a time
Backfill a database in one pass
Submit the profiles you already hold as a batch, poll, and collect complete records. For data teams.
Head of Dataon file, 2023
VP Datacurrent
re-enriched on your cadence
Current, not remembered
Keep a candidate record from ageing
Re-enrich on a cadence so a title from two years ago is not what your product shows. For recruiting platforms.
what has L. Moreau shipped?
NowVP Engineering · Vertex Labs
BeforePayments · Northwind
A career, not a title
Ground an agent in one person
Give a copilot the whole history rather than a headline, so it reasons about a career instead of a job title. For AI and agent teams.
Profile media
Photofetched
Recordfetched
One call, not two
Enrich a photo alongside the record
Fetch the profile photo with the record so a person view is complete in one call. For product surfaces with faces.
Security and compliance
The graph is ours. The identifiers stay yours.
We resolve and validate our own graph rather than reselling someone else’s, and matching stays hashed — so the raw identifiers you send are never exposed.
Security & Trust Centre
EU & UK
California
India
Audited
FAQs
Enrichment questions,
Enrichment questions,
answered
What does the 99% actually mean?
It is match correctness on reverse lookup — the right person for the email you supplied. It is not a deliverability claim, and it is scoped to professional profiles.
Do you return email addresses or phone numbers?
No. Enrichment takes an identifier and returns a person. We do not supply contact details as an output.
What is the difference between the two input modes?
Only what you start from. A profile URL is a direct fetch; a work email resolves to the profile first, then returns the same record.
Can we enrich in bulk rather than one at a time?
Yes. Submit a batch, poll for status, collect the results — or take the records as a file from the People Dataset.
How current is an enriched record?
350M+ profiles are refreshed monthly, and Signals tell you when one you care about changes, so you re-enrich the movers rather than everything.
Is this resold from another provider?
No. We resolve and validate our own graph across 18+ data sources and reconcile them into a single answer.
Bring your own records
See what comes back on your data.
Fifteen minutes, a handful of your own profiles or emails, and the records we return for them.