Typed fields, not text blobs
Experience comes back as an array of positions with dates and job descriptions; education, skills, and certifications are structured objects you can map straight into a schema. Nothing left to parse.
One URL in, the person out
Turn a LinkedIn URL into a structured person record
One POST with a profile URL returns the full person as typed JSON: current role, complete experience with job descriptions, education, skills, certifications, location, and the identifiers to join everything downstream.
Trusted by the best GTM teams
A record built like an API response, not a scrape
A profile URL is the smallest honest input in B2B data: no name collisions, no domain guessing, exactly one person.
Current by design
The record reflects where the person works now. Job changes are detected, and stale records are removed from live circulation, so yesterday's title does not ship as today's answer.
Keys that survive your joins
Every record carries LinkedIn identifiers and matching keys: stable handles for resolving the same person across a CRM, a warehouse, and a vendor export, however differently each of them spells the name.
An output that chains
The response slots directly into email and phone enrichment. One URL becomes a person, then a verified inbox, without re-matching anything in between.
What teams route through Profile Enrichment
Profile Enrichment, end to endSee the full playbook: when to enrich, what to store, and how the record feeds the rest of the stack.CRM HygieneSomewhere in your CRM, a contact changed jobs and the row never noticed. A stored LinkedIn URL is enough to rebuild it.Data ResolutionUse the matching keys as the join key across fragmented datasets that spell the same person three different ways.For Outbound SpecialistsPersonalize from real career history, not a headline scrape.
From URL to typed record
One endpoint, POST /v2/enrichment/linkedin-to-person, turns a profile link into structured JSON.
Send the URL
POST the person's LinkedIn URL. That is the whole request body; no name, no company, no guessing on your side.
We resolve the person
The URL is matched against 550M+ profiles. If the person has moved, the change is detected and the record reflects the current position.
Read the record
The full record lands in typed fields, from current role and company down to certifications, each one ready to map into a schema.
Write it back, or chain it
Pass the identifiers straight into email or phone enrichment, or write the record back to your CRM and join on the matching keys.
Related APIs
Company Enrichment API
Enrich company profiles with structured data, fresh firmographics, websites, and AI-ready context. Clean CRM records, qualify accounts, and segment lists.
Email Enrichment API
Find verified B2B emails using real signals and catch-all validation. Enrich contacts, improve deliverability, and power outbound workflows at scale.
Phone Enrichment API
Find B2B direct phone numbers for professional contacts in the US. Enrich prospect lists, improve CRM data, and power multichannel sales workflows.
Frequently asked questions
What does the response contain?
The complete person record as structured JSON: current role and company, full experience history with job descriptions, education, skills, certifications, location, plus LinkedIn identifiers and matching keys. Fields are typed, so an experience entry is an object with dates, not a paragraph to parse.
How current is the record?
The record reflects the person's current position: job changes are detected, and stale records are removed from live circulation. B2B data decays roughly 3-5% per month; re-enriching from the stored URL is how teams keep up.
Can I run it at CRM scale?
Yes. Every plan on the lifetime offer runs at 50 requests per second, under a fair use policy of 15,000,000 results a month. Refreshing a full CRM from stored URLs is a batch job, not a project.
