LinkedIn Profile API: How to Get Profile Data by URL in 2026

Recruiter and developer comparing a LinkedIn profile against structured JSON output on a dashboard screen

LinkedIn Profile API: How to Get Profile Data by URL in 2026

Disclosure: This article is published by Datamagnet, which sells a people and company data API. LinkedIn's API details come from its documentation on Microsoft Learn, and vendor prices come from each vendor's own pricing page or docs, checked between July and November 2026. Prices change, so confirm them before you buy.

LinkedIn's official API won't give you someone's profile from a URL. Its self-serve product, Sign In with LinkedIn using OpenID Connect, returns only the signed-in member's own basic profile: name, profile picture, locale and email (Microsoft Learn). Data on other members sits behind approved partner programs. To get profile data by URL, developers use a third-party LinkedIn profile API: you send a public profile URL and get structured JSON back, for roughly $0.008 to $0.28 per profile depending on vendor and volume.

Key Takeaways

  • LinkedIn's open permissions (openid, profile, email) only return data about the member who signed in to your app (Microsoft Learn).
  • The permission that returns matched public profiles of other members, r_sales_nav_profiles, belongs to the Sales Navigator Application Platform, which is "not currently accepting new partners" (Microsoft Learn).
  • Published prices run from $0.008 per profile on Datamagnet's Scale plan to $0.28 on People Data Labs' entry plan. Forcing a live read costs more on some vendors.
  • Judge vendors on freshness, fields, cost per profile and rate limits, in that order, using the same 20 test profiles.

A messy, unstructured profile record transforming into a clean structured JSON data card, connected by a blue arrow

Does LinkedIn Have an Official Profile API?

Yes, but it only covers the member who signs in to your app. Sign In with LinkedIn using OpenID Connect is self-serve and returns that member's name, profile picture, locale and, optionally, email. It has no parameter for another person's profile URL. Access to other members' data requires LinkedIn's approval as a partner.

Microsoft's access guide sets the rule: "Most permissions and partner programs require explicit approval from LinkedIn. Open Permissions are the only permissions that are available to all developers without special approval" (Microsoft Learn, Getting Access to LinkedIn APIs). The open permissions are:

PermissionWhat LinkedIn says it returnsWhose data
openidLets your app authenticate the member with OpenID Connect and get an ID tokenThe signed-in member
profile"The member's lite profile including their id, name, and profile picture"The signed-in member
email"The member's email address"The signed-in member
w_member_socialPost, comment and like on the member's behalf (Share on LinkedIn)The signed-in member

Sources: Sign In with LinkedIn using OpenID Connect and Getting Access to LinkedIn APIs, Microsoft Learn, checked November 2026.

The one permission that returns other people's profiles is r_sales_nav_profiles, described as access to "Sales Navigator endpoints that present matched, publicly available member profile information." It is limited to approved Sales Navigator Application Platform (SNAP) partners, and the SNAP page states: "We are not currently accepting new partners for access to the LinkedIn Sales Navigator API" (Microsoft Learn). Talent and Marketing programs also need approval, and none of them is a general profile lookup. Our LinkedIn API pricing guide covers each official program and who can get in.

Can You Get a LinkedIn Profile by URL Through the Official API?

No. The official "get profile" call is the OpenID Connect userinfo endpoint, and it answers one question: who owns this access token? You can't pass it a profile URL, a username or an ID, so it can't look up a prospect, a candidate or a CRM contact. For that you need a partner program or a third-party API.

Here is the whole official request, from LinkedIn's docs:

GET https://api.linkedin.com/v2/userinfo
Authorization: Bearer <access token>

The response has eight fields: sub, name, given_name, family_name, picture, locale, and the optional email and email_verified (Microsoft Learn). There's no job title, employer, work history, education or skills. LinkedIn also notes that this sign-in product "does not verify user identities and should not be marketed as such."

So for "linkedin api get profile": your own signed-in user, use userinfo; anyone else, by URL, use a profile data API.

How Do Third-Party LinkedIn Profile APIs Work?

A third-party profile API takes a public LinkedIn profile URL and returns the profile as JSON: name, headline, current title and company, location, work history, education and skills. Vendors differ in where the data comes from when you call. Some read the public profile live, some serve a stored copy, and many let you choose per request.

There are three common models:

  1. Database lookup. The vendor matches your URL to a record it collected earlier. It's fast and cheap per row, but the record is only as recent as the last refresh. People Data Labs, for example, says its API data is refreshed monthly (PDL docs).
  2. Cache first, live on request. The vendor returns a stored copy by default and reads the live profile when you ask, often for extra credits. Enrich Layer's default if-present mode returns a cached profile regardless of age, and forcing a live fetch adds 9 credits (Enrich Layer docs).
  3. Live read per request. The vendor reads the public profile when you call. Coresignal's Real-time Employee API scrapes on demand for 12 credits per request, taking under 30 seconds on a cache miss (Coresignal docs).

Why freshness decides which model you need

Stored records go stale. B2B contact data decays about 22.5% per year, or roughly 2.1% a month (Landbase, Data Decay Rate Statistics, 2026). The same source reports that 70.8% of business contacts have at least one meaningful change, such as a new title, phone number or email, within twelve months. A database refreshed once a quarter is already wrong for part of your list by the time you use it.

B2B Contact Data Decay Curve Cumulative data staleness rises from 0% at month 0 to roughly 5.6% at month 3, 11.2% at month 6, 16.9% at month 9, and 22.5% at month 12. Source: Landbase, 2026. 0% 5% 10% 15% 20% Month 0 Month 3 Month 6 Month 9 Month 12 Source: Landbase, Data Decay Rate Statistics (2026)
Cumulative B2B contact data staleness by month. Source: Landbase, 2026.

Database size is the number most vendors lead with, and it's the wrong one for a lookup API. When you enrich a CRM contact or a candidate, you need one record: the current one. Snapshots win only when you need millions of rows for analysis and last quarter's data is good enough.

How Do You Get LinkedIn Profile Data by URL with Datamagnet?

Send a POST request to /api/v1/person with the public profile URL and your API key. Each successful profile costs 1 credit, and failed lookups aren't charged. Set use_cache to "never" to read the profile at the moment you call. Without it, the API may return a stored copy.

curl -X POST "https://api.datamagnet.co/api/v1/person" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://www.linkedin.com/in/pratik-dani",
    "use_cache": "never"
  }'

The profile comes back under a message object:

{
  "message": {
    "full_name": "Pratik Dani",
    "profile_headline": "Building real-time data APIs",
    "job_title": "Founder",
    "current_company_name": "Datamagnet",
    "location": "Bengaluru, Karnataka, India",
    "experience": [...],
    "education": [...],
    "skills": [...]
  }
}

Structured JSON schema card showing labeled fields for name, current role, experience, education, and skills

The fields you'll use most

FieldWhat it holds
job_titleCurrent job title
current_company_nameCurrent employer, with company_id and company_industry alongside
locationProfile location, plus country, country_code and location_city
experienceFull work history as a structured list
educationSchools and degrees as a structured list
skillsListed skills

The People Profile endpoint docs list every field, including job_started_on, job_still_working, certification, language and recommendations.

Cache options and costs

use_cache takes three values (docs):

  • if-present (default): returns a stored profile if one exists, and reads live only if none does.
  • if-recent: best effort to return a profile no older than 29 days.
  • never: skips the cache and reads the profile when you call.

The base profile is 1 credit whichever you pick. Optional enrichment flags, such as similar_profiles or company_interest, add 2 credits each and are only charged when they succeed. Datamagnet returns no email addresses or phone numbers, so pair it with a contact-data vendor if you need those.

Pricing starts with 10 free credits and no card, then $39 a month for 1,000 credits, $99 for 10,000 or $199 for 25,000. Pay-as-you-go starts at $0.02 a credit (Datamagnet pricing). The People API page has more request examples, and the people enrichment API page shows the CRM and inbound-lead workflow. Company pages, posts, people search and job postings are on the full API list.

LinkedIn Profile API Comparison: Price per Profile in 2026

Published prices for a person profile lookup run from about $0.008 on Datamagnet's Scale plan to $0.28 on People Data Labs' entry Pro plan. The bigger differences are what one credit buys and whether the data is read live. The table normalizes each vendor's own pricing to one person profile.

ProviderHow a profile is billedCost per profileFreshnessEntry priceSource
Datamagnet1 credit per successful profile$0.008 (Scale) to $0.039 (Starter); from $0.02 pay-as-you-goRead at call time with use_cache: "never"; otherwise may return a stored copy10 free credits, then $39/moPricing
Enrich Layer1 credit cached; +9 credits to force a live fetch$0.0216 to $0.10 cached; $0.216 to $1.00 forced live (10 credits)Cache first (if-present default)100 to 200 trial credits; PAYG from $10Pricing · Cache docs
People Data LabsRecords per month$0.28 at entry ($98/mo for 350 records)API data refreshed monthlyFree up to 100 records/moPricing · Updates
ScrapIn (Reverse Contact)1 credit per successful person profile callNot publishedReal-time profile APIPay-as-you-go from $100Pricing · Docs
Coresignal10 credits per core record, 20 per full record; 12 for a real-time employee requestAbout $0.196 per core record on Mini ($49/mo, 2,500 credits)Stored records; real-time API on demandFree 2,000 credits; Mini $49/moPricing · Real-time docs
Crustdata1 to 7 credits from the database; 7 credits liveNot published (dollar value per credit set by plan)Database, or live as a plan-gated add-onSelf-serve and enterprise plans; per-credit price not listedCredit docs

Per-profile figures are our arithmetic from each vendor's published price, checked between July and November 2026. They aren't quotes from the vendor.

Two caveats. Enrich Layer's monthly and annual subscriptions are both a 12-month commitment, per its pricing FAQ; pay-as-you-go isn't (Enrich Layer). ScrapIn's two sites list different minimums: $100 on reversecontact.com and $500 on scrapin.io (ScrapIn pricing).

For side-by-side detail, see Datamagnet compared with Enrich Layer, People Data Labs, ScrapIn, Coresignal and Crustdata.

How to Choose a LinkedIn Profile API: Four Criteria

Score each vendor on freshness, fields, cost per profile and rate limits, in that order, before price per credit. Freshness decides whether the data is useful at all. Fields decide how much code you write. Cost and rate limits decide whether it fits your volume. Test all four with the same 20 profiles.

1. Freshness

Ask how old a returned record can be, not when the database was last "updated." Check whether the vendor reads the profile live by default, only when you pass a parameter, or never. Then check what a live read costs. On Enrich Layer, a forced live profile is 10 credits instead of 1 (Enrich Layer docs). On Crustdata, live enrich is 7 credits and plan-gated (Crustdata docs).

Include five people you know changed jobs last month. A vendor that still shows the old employer isn't fresh enough for CRM work.

2. Fields and schema consistency

Get a real sample response, not a spec sheet. Check that current role is separate from work history, that experience, education and skills are structured lists rather than free text, and that missing values come back as null instead of a dropped key. A field that's sometimes a string and sometimes an object will break your parser more often than a smaller dataset will.

3. Cost per profile, including failures

Divide the plan price by the profiles it actually buys, using the credits a real request uses. Coresignal charges 10 credits for a core record and 20 for a full one (Coresignal pricing). Then ask whether failed lookups cost money. Datamagnet charges only for successful profile requests, and Crustdata says it doesn't bill unmatched identifiers (Crustdata). Finally, check the minimum: People Data Labs Pro starts at $98 a month, and Enrich Layer's subscriptions run 12 months.

4. Rate limits and delivery

Published limits vary widely. Enrich Layer allows 300 requests a minute on paid accounts and 2 a minute on trial (Enrich Layer docs). Crustdata lists 15 requests a minute for person enrich and 10 for live endpoints (Crustdata docs). Coresignal caps its real-time employee search at 50 URLs a minute (Coresignal docs). Work out your peak, such as a 5,000-row CRM backfill, and check it fits.

Delivery matters as well. REST suits lookups that a person or workflow triggers. Postman's 2025 survey of over 5,700 developers found 93% use REST APIs, while about half use webhooks (Postman, 2025 State of the API Report).

REST vs. Webhook Adoption Among Developers 93% of developers use REST APIs; 50% use webhooks for event-driven delivery. Source: Postman, 2025 State of the API Report. REST APIs 93% Webhooks 50% Source: Postman, 2025 State of the API Report
Developer adoption of REST vs. webhook delivery. Source: Postman, 2025.

Webhooks matter when you need to know the moment something changes, such as a job switch. Polling a whole CRM daily burns credits on profiles that didn't change.

Diagram comparing polling every 5 minutes against an instant webhook push for enrichment data updates

Datamagnet's webhooks and signal monitors cover job-change and engagement events. The Signal API is sales-led, so book a demo to get access.

Does Your Team Shape Which Profile API You Pick?

Yes. Recruiting and sales teams should weight freshness and workflow fit above schema depth, because the cost they're fighting is time. Developer teams building a product feature should weight schema stability and rate limits higher, because every field change becomes a bug in their product.

Recruiters spend 52% of their working hours on administrative work and only 28% on sourcing and candidate engagement, based on a tracked study of over 200 recruiters across 20 companies (IQTalent, Where Recruiting Time Goes, Jan 2026).

Where Recruiter Time Actually Goes 52% administrative work, 28% sourcing and candidate engagement, 12% hiring manager coordination, 8% reporting and other. Source: IQTalent, January 2026. 52% admin work Admin (52%) Sourcing (28%) Coordination (12%) Other (8%) Source: IQTalent, Where Recruiting Time Goes (Jan 2026)
Recruiter time allocation across core activities. Source: IQTalent, 2026.

A profile API that drops a current profile into the ATS or CRM record cuts into that admin share. Test the API inside the tool you'll actually use it from. Datamagnet's n8n integration and Clay integration are two examples of the same API in different workflows.

What Happens If Your Profile API Vendor Shuts Down?

Every integration built on that vendor's endpoints breaks until you migrate. It has happened: Proxycurl, a well-known LinkedIn profile API, shut down on July 4, 2025, after LinkedIn sued it (Nubela, Goodbye Proxycurl). Vendor stability belongs on your checklist next to price and freshness.

Two habits limit the damage: keep vendor field names behind your own mapping layer, and store the profile URL as your key, since every vendor accepts it. Datamagnet's Proxycurl migration guide shows the endpoint mapping teams used after that shutdown.

On terms: LinkedIn's User Agreement (section 8.2) bars members from using software or bots "to scrape or copy the Services, including profiles and other data" (LinkedIn User Agreement). Ask each vendor how it collects and handles data, and get your own legal review for your use case.

Frequently Asked Questions

Does LinkedIn have a profile API?

Only for the member who signs in to your app. Sign In with LinkedIn using OpenID Connect returns that member's name, profile picture, locale and optionally email. LinkedIn's permission for other members' public profiles belongs to the Sales Navigator Application Platform, which isn't accepting new partners. Developers who need other profiles use a third-party profile API.

Can I get a LinkedIn profile by URL with the official API?

No. The official userinfo endpoint returns the profile of whoever owns the access token, and it has no parameter for a profile URL, username or ID. To look up any public profile by URL, you need an approved partner program or a third-party LinkedIn profile API that accepts the URL and returns JSON.

How much does a LinkedIn profile API cost?

Published prices run from about $0.008 per profile on Datamagnet's Scale plan to $0.28 on People Data Labs' entry plan. Enrich Layer starts at $0.0216 per cached profile but charges 10 credits to force a live read. Coresignal works out to about $0.196 per core record on its $49 Mini plan.

What data does a LinkedIn profile API return?

Most return name, headline, current job title and company, location, work history, education and skills as structured JSON. Datamagnet's person endpoint returns these as job_title, current_company_name, location, experience, education and skills, plus certifications, languages and recommendations. Datamagnet does not return email addresses or phone numbers.

How do I test data freshness before choosing a vendor?

Run the same 20 profile URLs through each vendor, including five people you know changed jobs recently. Compare whether each response shows the new title and employer. If a vendor offers a live-read option, run the set both ways and note the extra cost of reading live.

Do I need LinkedIn's approval to use a third-party profile API?

No partner approval is involved, because you aren't calling LinkedIn's API. You're buying data from a vendor that collects public profile information. LinkedIn's User Agreement bars scraping by members, so ask each vendor how it sources data, and run your own legal review, especially if you store profiles of people in the EU.

Sources

Choosing a LinkedIn Profile API

LinkedIn's own API answers "who signed in?", not "who is this profile URL?". For profile data by URL you need a third-party API, and the right one is the one whose freshness, fields, cost per profile and rate limits fit your workflow. Price per credit comes last, after you know what a credit buys.

To test it, create a free Datamagnet account and run 10 profile URLs with use_cache: "never" on the free credits, no card needed. Run the same URLs through one or two other vendors and compare the raw responses side by side. For wider context on people enrichment, see our real-time B2B people enrichment API guide.

Pratik Dani

About Pratik Dani

CEO, Founder