LinkedIn enrichment API
Turn a LinkedIn handle or URL into a full person record and a full company record, then load both into your CRM.
8 endpointsLinkedIn
What API can enrich leads with LinkedIn data? Social Fetch can. Send a handle or profile URL to the LinkedIn profile route for the person's roles, schools and followers, and a company slug to the organization route for headcount, industry and locations. Batch routes take many records in one call, and an optional lookup finds a work email. You pay per lookup, with no seat licence.
A real run. Measured and priced.
Enrich one person and their company, run on 21 Nov 2026 against live public data. A full person record and a full company record, ready for a CRM.
01 GET /v2/
linkedin/ profiles ?handle=satyanadella Chairman and CEO at Microsoft: 5 positions, 3 schools, 12,333,168 followers.
5 credits, 2.8 s
02 GET /v2/
linkedin/ organizations ?slug=microsoft 29,565,288 followers, 230,560 staff and 45 locations, with showcase pages and affiliates.
9 credits, 3.9 s
- Credits
- 14
- 2 calls
- Starter pack
- $0.20
- $14 per 1,000 credits
- Scale pack
- $0.023
- $1.64 per 1,000 credits
- Runtime
- 6.7 s
- Server time, calls one after another
Credits are each route's published price. Dollar figures are those credits at the list rate of each pack. Results and times are from the calls above, made on 21 Nov 2026; live data changes, so a run today returns newer numbers.
What usually breaks first
Where a home-built scraper or a marketplace API tends to fail once it runs in production.
Lead lists arrive half empty
A name and a company is not enough to score, route or personalise, and reps fill the gaps by hand, one profile tab at a time.
Enrichment data goes stale
Enrichment tools sell seats and monthly minimums, and their data can be months old. When someone changes jobs, your CRM keeps the old title until a rep notices.
You need a live lookup
Call it when a lead arrives and again before a campaign, for the person's current role, their company's size and industry, in one JSON shape your pipeline already reads.
The routes. 8 for this job.
The routes teams call for this job on LinkedIn. Each one links to its reference page, with every parameter and field.
GET /v2/ linkedin/ profiles One person from a handle or profile URL: headline, current and past roles, schools, location and followers.
GET /v2/ linkedin/ profiles/ batch Many people in one call, for enriching a list or an import instead of one lead at a time.
GET /v2/ linkedin/ people/ resolve Turn a handle into LinkedIn's stable person id, so a record survives a vanity URL change.
GET /v2/ linkedin/ organizations One company from its slug: industry, staff count, headquarters, locations, followers and showcase pages.
GET /v2/ linkedin/ organizations/ batch Many companies in one call, for account lists and territory planning.
GET /v2/ linkedin/ organizations/ {organizationId}/ headcount Headcount over time, a hiring or shrinking signal for account scoring.
GET /v2/ linkedin/ profiles/ email A work email for a profile, when one can be found. 20 credits per lookup, so call it only for leads you will contact.
GET /v2/ linkedin/ people/ search Find people by title, company or location when you start from a target account, not a name.
5 steps. How teams wire it up.
The usual order. Change the schedule, schema and thresholds to fit your stack.
Step 1: Capture the LinkedIn handle
Store the handle or profile URL when a lead signs up, books a demo or lands from an import. Resolve it to the stable person id once and key the record on that.
Step 2: Enrich the person
Call the profile route for the current title, company, past roles and location. Write them to CRM fields, and keep the raw JSON for anything you don't map yet.
Step 3: Enrich the company
Take the current employer's slug from the profile and call the organization route for industry, staff count and headquarters. Many leads share a company, so cache it per company.
Step 4: Score and route
Your rules decide fit: seniority from the title, size from the staff count, region from the headquarters. Send the lead to the right queue or sequence.
Step 5: Refresh before you reach out
Re-run the profile lookup before a campaign. If the role or employer changed, update the record, or treat the job change as a fresh trigger.
Why revenue teams enrich here
Pay per lookup
A person record is 5 credits, with no seats and no monthly minimum, so enrichment cost follows lead volume.
Look up when it matters
Call when a lead arrives and again before outreach, instead of trusting a yearly data dump.
Person and company in one shape
Profiles, companies, headcount and posts come back in the same JSON layout as every other network we cover.
Batch routes for lists
Enrich an import in a few calls instead of thousands.
You only pay for completed lookups
Requests that fail on our side cost nothing.
Common questions
What API can enrich leads with LinkedIn data?
Social Fetch. GET /v2/linkedin/profiles returns a person's roles, schools, location and followers from a handle or URL, and GET /v2/linkedin/organizations returns a company's industry, staff count and locations. Both use one API key and one response shape.
How much does LinkedIn enrichment cost?
A person record is 5 credits. A company record is 6 credits by id, or 9 by slug, because a slug is resolved to an id first. A work email lookup is 20 credits. Credits are bought in packs and never expire. See pricing.
Do I need a LinkedIn account or cookies?
No. Every lookup returns public profile and company data. You never share a LinkedIn login or cookies with us.
Can I enrich a whole list at once?
Yes. The batch routes take many profiles or companies per call. For very large lists, send batches in parallel and store the results as they arrive.
Start on free credits. Make your first request.
Sign up and get 100 credits, no card needed. Run the request above, then buy more when you need them. Credits never expire.