The LinkedIn API Pricing Guide You Need And How To Get Access

If you're trying to figure out LinkedIn API pricing and how to get access, here's the short version: the official LinkedIn API is useful for narrow, approved use cases, but most developers who want profile, company, or jobs data run into the same wall, restricted access, partner approvals, and pricing that is either opaque or clearly aimed at bigger teams.

Having worked around enrichment and go-to-market data systems for years, I don't think the problem is that LinkedIn's APIs are bad. The problem is that most people reading a "LinkedIn API pricing" article are not actually trying to buy a marketing partner workflow. They want programmatic access to people, company, or job data now, and LinkedIn's approval model was not designed to make that easy.

The earlier version of this article was directionally right on that point. I'm keeping that spine intact. I am updating the parts that matter: the naming, the product landscape, and what to do now that Proxycurl has been sunset.

Here’s a cleaner comparison, and this time I am being explicit: the first four rows are LinkedIn products or LinkedIn-adjacent access routes. NinjaPear is not a LinkedIn API, does not scrape LinkedIn, and should be read as a separate B2B data alternative that covers many of the same downstream use cases.

Product / Route	Pricing	Uses	Access	Data Quality	Ease of Access	Avg. Score
LinkedIn People/Profile access	Custom / partner-led	Retrieve approved member profile data for approved workflows	Requires application and LinkedIn partnership	⭐⭐⭐⭐☆	⭐☆☆☆☆	2.5/5
LinkedIn Company / Organization access	Custom / partner-led	Retrieve company info, organization data, and related firmographics	Requires LinkedIn partnership approval	⭐⭐⭐⭐☆	⭐☆☆☆☆	2.5/5
LinkedIn Jobs API	Variable, based on usage volume	Extract job listings, search for relevant job postings	Limited to LinkedIn partner integrations	⭐⭐⭐⭐☆	⭐☆☆☆☆	2.5/5
Sales Navigator	$99.99 to $149.99 per month, per user	Advanced search and insights for sales outreach	Via Sales Navigator subscription	⭐⭐⭐⭐☆	⭐⭐⭐☆☆	3.75/5
NinjaPear Company API, not a LinkedIn API	Credit-based, transparent	Company details, headcount, updates, funding, logo from public web sources	Self-serve	⭐⭐⭐⭐☆	⭐⭐⭐⭐⭐	4.5/5
NinjaPear Employee API, not a LinkedIn API	Credit-based, transparent	Person profile and work email enrichment from public sources	Self-serve	⭐⭐⭐⭐☆	⭐⭐⭐⭐⭐	4.5/5

That distinction matters.

If you need official LinkedIn functionality inside LinkedIn's rules, keep reading about the official APIs. If you need B2B data in a similar shape for enrichment, prospecting infrastructure, or account intelligence, you should evaluate a non-LinkedIn data vendor separately instead of pretending it is the same thing.

Types of LinkedIn APIs/Tiers

LinkedIn does not really sell one neat, public, developer-friendly API product. It sells access through programs, products, and partner tracks. That distinction matters because "can I technically call an endpoint?" and "can I get approved to call it for my business model?" are two different questions.

1. API for LinkedIn People Profiles

If you need detailed personal data from LinkedIn users, like work history, education, skills, and other profile insights, the People Profile API is the obvious place to start. In practice, this is where most teams hit the wall first.

Important information provided:

• Name and URL of the profile
• Experience at work and current title
• Skills and recommendations
• Education history

If you're willing to put in the time and money to go through the approval process, this API can be excellent. For everyone else, it tends to be impractical, especially if your product is not already aligned with one of LinkedIn's preferred partner categories.

2. API for LinkedIn Company Profiles

The LinkedIn Company Profile API is the natural tool for gathering business information listed on LinkedIn. That includes company name, industry, employee count, and headquarters-related data.

Important information provided:

• Company name and URL
• Size and industry
• Employee growth indicators
• Headquarters location

This API is strong for enterprise workflows tied closely to LinkedIn's ecosystem. It is much less friendly if you're a startup that just wants structured company data without a months-long business-development process.

3. API for LinkedIn Jobs

Another useful part of the stack is the Jobs API. This is mainly relevant if you're building a job board, labor-market analytics workflow, or a recruiting product that needs job posting data.

Important information provided:

• Job title and description
• Employer details
• Location and job type
• Posted and expiration dates

Again, the pattern repeats. The functionality is real. The access is the bottleneck.

4. API for LinkedIn Marketing

For ad workflows, LinkedIn's Marketing API is the piece that matters. It lets businesses create, manage, and measure LinkedIn ad campaigns.

Important information provided:

• Campaign creation and management
• Performance metrics like clicks and impressions
• Audience targeting by industry, title, and similar dimensions

This one makes the most sense if you're already spending materially on LinkedIn Ads. For smaller teams, it usually does not solve the broader enrichment problem they came for in the first place.

5. API for LinkedIn Learning

LinkedIn Learning also has integration pathways for platforms that want course catalogs, enrollment, and progress tracking.

Important information provided:

• Course titles and descriptions
• Enrollment status
• Completion tracking

This is a niche API. Useful, but not what most people searching for "LinkedIn API pricing" are actually after.

Details of Each LinkedIn API

This is where most articles get vague. I'll keep it simple: pricing, use case, access, setup.

1. LinkedIn People Profile API

Pricing of this LinkedIn API

The cost of the LinkedIn People Profile API is high mainly because it is not a clean self-serve SKU for most developers. Access generally comes through LinkedIn's partner structures and enterprise products, which means the real price is a mix of subscription cost, business-development friction, and time.

Applications:

This API offers comprehensive LinkedIn profile information, such as:

• Full name
• Job titles
• Work experience
• Qualifications and certifications
• Education background

It is best suited for businesses that need detailed professional identity data and already fit LinkedIn's approved use cases.

How to Get Access:

Gaining access is not as straightforward as signing up. You generally need to apply, wait for approval, and fit within a partner or approved product track.

1. Apply through the relevant LinkedIn developer or partner program.
2. Wait for approval from LinkedIn.
3. If approved, receive credentials and product access tied to that program.

How to Set Up:

Here’s a simple example of how you’d typically access data via a LinkedIn People Profile API endpoint:

import requests

API_KEY = "your_linkedin_api_key"
person_id = "person_profile_id"

url = f"https://api.linkedin.com/v2/people/{person_id}"

headers = {
    "Authorization": f"Bearer {API_KEY}",
    "Content-Type": "application/json"
}

response = requests.get(url, headers=headers)

if response.status_code == 200:
    data = response.json()
    print(data)
else:
    print(f"Failed to retrieve profile: {response.status_code}")

However, the complex approval process and the enterprise-style commercial model make the official LinkedIn People Profile API hard to use for most teams.

2. LinkedIn Company Profile API

Pricing of this LinkedIn API

The Company Profile API is one of those products where the practical issue is not just the monthly cost. It is the lack of a straightforward public pricing path for most developers.

Uses:

The Company Profile API allows you to pull detailed information about companies, including:

• Company name
• Industry classification
• Number of employees
• Revenue signals or related firmographic context
• Growth trends

This API is particularly useful for B2B marketing, sales prospecting, and competitive analysis.

How to Get Access:

Similar to the People Profile API, getting access typically requires an application to LinkedIn's partner or approved access programs.

1. Apply to the relevant LinkedIn partner program.
2. Upon approval, LinkedIn provides your API credentials.

How to Set Up:

Below is an example of how to set up the Company Profile API to fetch company data.

import requests

API_KEY = "your_linkedin_api_key"
company_id = "company_profile_id"

url = f"https://api.linkedin.com/v2/companies/{company_id}"

headers = {
    "Authorization": f"Bearer {API_KEY}",
    "Content-Type": "application/json"
}

response = requests.get(url, headers=headers)

if response.status_code == 200:
    company_data = response.json()
    print(company_data)
else:
    print(f"Failed to retrieve company profile: {response.status_code}")

3. LinkedIn Jobs API

Pricing of this LinkedIn API

LinkedIn's Jobs API pricing varies by usage, integration needs, and commercial arrangement. That usually means you will not get a satisfying answer from a pricing page alone.

Uses:

This API is used to fetch job listings, which include:

• Job titles
• Company details
• Location
• Employment type
• Posted and expiration dates

This is useful for companies building job aggregation or hiring workflows.

How to Get Access:

Access to the LinkedIn Jobs API also generally requires partnership or approved integration status.

1. Apply for the relevant LinkedIn jobs or partner access.
2. Secure approval to receive your API key.

How to Set Up:

Here’s how you’d typically set up a connection to LinkedIn’s Jobs API.

import requests

API_KEY = "your_linkedin_api_key"
job_id = "job_listing_id"

url = f"https://api.linkedin.com/v2/jobs/{job_id}"

headers = {
    "Authorization": f"Bearer {API_KEY}",
    "Content-Type": "application/json"
}

response = requests.get(url, headers=headers)

if response.status_code == 200:
    job_data = response.json()
    print(job_data)
else:
    print(f"Failed to retrieve job listing: {response.status_code}")

Cons of using the official LinkedIn APIs

The biggest issue with LinkedIn's APIs is not that they do nothing. It's that they do very specific things within very specific business boundaries.

1. Pricing is high or unclear

One of the biggest downsides is the commercial model.

• Many LinkedIn API products are not sold with transparent, self-serve pricing.
• Enterprise and partner arrangements can push the real cost much higher than a startup expects.
• Sales Navigator itself is more straightforward, at roughly $99.99 to $149.99 per user per month, but that is a user tool, not a broad data API strategy.

For small to mid-sized businesses, that is a real barrier.

2. Restricted access

Gaining access to LinkedIn’s APIs is not as simple as creating an account.

• You often need to apply and get approved.
• Approval can take weeks or months.
• LinkedIn can limit access based on your category, business model, and intended use.

That slows down product timelines in a way most founders underestimate.

3. Limited flexibility

LinkedIn APIs come with scope restrictions.

• Certain data is only available for authenticated users.
• Some use cases require explicit user permission.
• Broader enrichment use cases often sit outside what LinkedIn wants to support directly.

4. Complicated setup and integration

The technical setup is not terrible if you already know OAuth, API scopes, and enterprise vendor workflows. If you don't, it gets annoying fast.

• OAuth flows add friction.
• Product-specific approvals add more friction.
• Documentation can be clear on syntax but unclear on commercial eligibility.

5. Long approval times

This point deserves to stand alone because it changes build strategy.

If your team needs data this quarter, a multi-month approval cycle is not just inconvenient. It can kill the project.

6. Data availability and permissions

LinkedIn's API access model also restricts what you can see depending on permissions, product scope, and user consent.

If your business depends on broad, repeatable coverage, this can materially reduce the value of the official route.

Proxycurl, and what changed

The older version of this article recommended Proxycurl heavily. That was fair at the time.

Update: Proxycurl API has been sunset. The founder behind Proxycurl is now building NinjaPear. I am keeping the Proxycurl references here for historical context because they explain the old market shape, but if you're evaluating options today, the modern path is NinjaPear for self-serve B2B intelligence and enrichment from public sources, with none of the legal liability.

Proxycurl existed because there was a huge gap between what developers wanted from LinkedIn-shaped data and what the official LinkedIn API would actually let them do. That gap still exists. The brand changed. The underlying problem did not.

Why NinjaPear is now the better fit

At this point, it should be obvious that the official LinkedIn APIs are strongest when your use case fits LinkedIn's own commercial boundaries. If your job is to enrich records, score accounts, map companies, track hiring signals, or build outbound infrastructure, the better modern alternative is NinjaPear.

I want to be very explicit here because this was the admin feedback, and it was correct: NinjaPear is not a LinkedIn API. It does not scrape LinkedIn. It does not rely on LinkedIn data. It builds company and people intelligence from public sources and returns that data in a structured shape that is useful for many of the same downstream workflows people previously reached for Proxycurl or LinkedIn APIs to solve.

That means the overlap is in the job to be done, not the source.

If your workflow says, "I need a company profile, headcount, funding, updates, work email, or a professional profile-like record for enrichment," NinjaPear can often fill that need. If your workflow says, "I specifically need official LinkedIn member data under LinkedIn's permissions model," then only LinkedIn can give you that.

Where the old Proxycurl endpoints map now

Here is the practical translation layer.

Historical need	Old Proxycurl approach	NinjaPear replacement, not LinkedIn-sourced	Pricing model	Avg. Score
Person profile enrichment	Person Profile API	Employee API GET /api/v1/employee/profile	3 credits per call	4.5/5
Company profile enrichment	Company Profile API	Company API GET /api/v1/company/details	3 credits per call	4.5/5
Employee count	Company enrichment / employee endpoints	Company API GET /api/v1/company/employee-count	part of Company API suite	4.5/5
Company monitoring	N/A or stitched tools	Company API GET /api/v1/company/updates	2 credits per call	4.5/5
Funding data	separate vendor needed	Company API GET /api/v1/company/funding	2 credits + 1 per unique investor	4.5/5
Work email lookup	Contact-style enrichment	Employee API GET /api/v1/employee/work-email	2 credits on hit, 0.5 on miss	4.25/5
Company logo	separate logo endpoint	Company Logo API GET /api/v1/company/logo	Free	5/5

A few specifics matter here:

• NinjaPear offers a 3-day free trial with 10 credits included.
• GET /api/v1/employee/profile costs 3 credits per call.
• GET /api/v1/company/details costs 3 credits per call, with optional flags taking it up to 6.
• GET /api/v1/company/updates costs 2 credits per call.
• GET /api/v1/company/funding costs 2 credits per call + 1 credit per unique investor.
• GET /api/v1/employee/work-email costs 2 credits when found, 0.5 credits on miss.
• The Company Logo API is free.

That is a much more useful pricing model than "talk to sales and maybe talk to legal after that."

Example setups

The original article had setup snippets, which were useful, so I'm preserving that idea and updating the alternative path.

Official LinkedIn style flow

If you are approved and have the right OAuth flow, your setup will generally look like this:

import requests

access_token = "your_access_token"

response = requests.get(
    "https://api.linkedin.com/v2/me",
    headers={"Authorization": f"Bearer {access_token}"}
)

print(response.json())

This is fine for approved, authenticated, narrow flows.

NinjaPear person profile alternative

If what you really needed was structured professional profile data for enrichment, the NinjaPear path is much more direct. Again, this is not LinkedIn data. It is B2B profile data assembled from public sources.

import requests

response = requests.get(
    "https://nubela.co/api/v1/employee/profile",
    params={"email": "[email protected]"},
    headers={"Authorization": "Bearer YOUR_API_KEY"}
)

print(response.json())

NinjaPear company profile alternative

This is also not a LinkedIn company endpoint. It is company intelligence from public web sources in an API shape that is useful for enrichment.

import requests

response = requests.get(
    "https://nubela.co/api/v1/company/details",
    params={"website": "https://stripe.com"},
    headers={"Authorization": "Bearer YOUR_API_KEY"}
)

print(response.json())

NinjaPear company updates alternative

import requests

response = requests.get(
    "https://nubela.co/api/v1/company/updates",
    params={"website": "https://stripe.com"},
    headers={"Authorization": "Bearer YOUR_API_KEY"}
)

print(response.json())

That last one matters more than most people realize. A lot of teams think they need LinkedIn profile or company data, but what they actually need is a trigger: hiring spike, website change, new funding, new blog post, social activity. That is a different class of intelligence.

LinkedIn API pricing, what you should actually do

If you are a big company building squarely inside LinkedIn's approved ecosystem, apply for the official program. That is the right move.

If you are a startup, recruiter, revops team, enrichment vendor, or GTM builder who needs structured people and company data without waiting around for a partner manager to bless your use case, the official LinkedIn path is usually the wrong first move.

This is the part people often avoid saying out loud. I'll say it plainly.

LinkedIn is optimizing for platform control. You are optimizing for shipping.

Those are not the same objective.

linkedin: easy $10/mo upsell on me if you let me filter connection requests by role + fund size + relevance. right now vc's at huge funds get buried under 600+ connection requests and i miss them. no mcp. no api. nothing. @LinkedIn fix this

— Julius Brussee (@julius_brussee) Sun May 24 08:36:42 +0000 2026

Final take

The official LinkedIn API is real, but for most people searching for LinkedIn API pricing, it is the wrong abstraction. The issue is not whether an endpoint exists. The issue is whether you can get approved, afford the commercial model, and use the data the way your product actually needs.

That was the opening thesis of this article before. It still holds.

What changed is the alternative. Proxycurl is no more. NinjaPear is the continuation of that line of thinking, except with richer company intelligence, transparent credit-based pricing, and no dependence on LinkedIn or scraping LinkedIn.

If your next step is practical, do this: first decide whether you truly need official LinkedIn partner access or whether you just need structured B2B intelligence that looks similar to the output your workflow expects. If it's the second one, start with NinjaPear's free trial, test the Employee API and Company API on a few real accounts, and see if it covers the actual job you need done.

Just don't confuse the categories. LinkedIn APIs are LinkedIn products. NinjaPear is not. It is a separate B2B data platform that can solve many of the same business problems without pretending to be a LinkedIn API.