LinkedIn API: What Exists, What's Restricted, and What Developers Use Instead (2026)

There is no LinkedIn API for extracting profile data, job listings, or search results at scale in 2026. What exists is a family of purpose-specific APIs — advertising, job posting, company pages, your own profile data — all gated behind LinkedIn's Developer Program with selective approval. Developers who apply to extract job or profile data at scale are rejected.

This guide covers the full LinkedIn API landscape: what each API does, what it actually costs, which ones are accessible vs. invite-only, and what developers building on LinkedIn data actually use when the official API falls short.

What LinkedIn APIs Actually Exist in 2026?

LinkedIn has six API products: the Marketing API (advertising and campaign management), the Jobs API (post and manage job listings), the Profile API (access your own profile via OAuth), the Talent Solutions API (ATS integrations, invite-only), the Learning API (LinkedIn Learning content, invite-only), and the Voyager API (unofficial internal API the mobile app uses). None of these provide open access to job search results, other users' profile data, or LinkedIn search at scale.

The pattern is the same across every official LinkedIn API: each one serves a specific business workflow (advertising, hiring, learning) and is gated to partners in that vertical. There is no "data access" API. The closest thing — the unofficial Voyager API — is what the linkedin-api Python library uses, and LinkedIn bans accounts using it within 3–7 days. See why the unofficial API gets accounts banned for the technical detail. For a full breakdown of what tools developers use instead, see the LinkedIn scraping tools comparison.

LinkedIn's API approval rate for data extraction use cases is effectively zero. The Developer Program application asks for a business justification — 'I want to scrape job listings' is not an approved use case. LinkedIn has not granted new data extraction API access to third parties since 2018.

What Does the LinkedIn API Cost?

Most LinkedIn APIs are free to access but restricted by rate limits and partner approval. The Marketing API is free with LinkedIn Ads spend. The Jobs API pricing is not publicly disclosed — it's part of enterprise ATS partnership agreements. The Profile API (your own data) is free via OAuth. There is no paid tier that unlocks profile search or job listing extraction for third parties.

The common misconception about linkedin api cost is that paying more unlocks data access. It doesn't. LinkedIn's API isn't like a SaaS product where a higher tier gives you more endpoints. The restrictions are structural: LinkedIn's business model (advertising, premium subscriptions, Talent Solutions) depends on keeping profile data and job data on LinkedIn.com. Selling API access to that data would undercut its own revenue.

This is the same logic that drove Indeed to shut down its public API in 2021 and Glassdoor to shut down its Partner API in 2023. LinkedIn never fully opened its API in the first place, so there was nothing to shut down — it was always gated. The result across all three platforms is the same: developers who need job data use browser-based scraping rather than official APIs.

Does LinkedIn Have a Jobs API for Searching or Extracting Job Listings?

LinkedIn has a Jobs API, but it is not a search API — it is a posting API. It lets approved ATS and enterprise HR platforms post job listings to LinkedIn, manage applications, and sync applicant data. It does not let developers query LinkedIn's job listing database or export job search results. Access requires a Talent Solutions partnership agreement, which LinkedIn grants selectively to ATS vendors.

The LinkedIn Jobs API is one of the most commonly misunderstood endpoints. Developers search for a LinkedIn job search API, find documentation for the Jobs API, apply, and then discover it only covers job posting — not job searching or extraction.

For recruiter teams, sales teams monitoring hiring signals, or researchers tracking job market trends — the Jobs API is not the answer. The data you want (what companies are hiring, for what roles, at what salary) lives on LinkedIn's job search pages and is only accessible by reading those pages directly. See how to scrape job listings for the no-code workflow that covers LinkedIn Jobs, Indeed, and Glassdoor. For Sales Navigator specifically, see how to scrape LinkedIn Sales Navigator — lead list exports that the Jobs API never covers.

How Do You Get Access to the LinkedIn Developer API?

Apply at developer.linkedin.com. LinkedIn's Developer Program has three tiers: Default Access (anyone can apply, gets basic OAuth profile data), Partner Access (selective approval for specific use cases), and Enterprise Access (invite-only for Talent Solutions and Marketing partners). Data extraction use cases are not approved under any tier. Approval for Partner Access takes 4–8 weeks and requires a business justification LinkedIn finds acceptable.

1. Create a LinkedIn App at developer.linkedin.com — any developer can do this, gets Default Access immediately
2. Default Access gives you: sign in with LinkedIn (OAuth), basic profile data (your own), Share on LinkedIn. No job search, no profile lookup of other users.
3. Apply for Partner Access by submitting a business justification — use cases LinkedIn approves: advertising management, ATS/HCM integration, learning platforms, marketing automation
4. Use cases LinkedIn rejects: data extraction, scraping, profile aggregation, job search automation, research/analytics on third-party profiles
5. Enterprise/Talent Solutions: invitation only — LinkedIn reaches out to ATS vendors and enterprise HR platforms. Cannot be applied for directly.

If your use case is 'I want to build something that reads LinkedIn job listings' or 'I need profile data for B2B lead generation', the Developer Program will not approve you. This is not a matter of application quality — LinkedIn has structurally decided these use cases don't get API access. The same rejection applies to open source scrapers that try to use the unofficial Voyager API — they work initially then get accounts banned.

What Is the LinkedIn Voyager API and Why Do Developers Use It?

The LinkedIn Voyager API is LinkedIn's internal REST API that the LinkedIn web app and mobile app use to load feeds, profiles, search results, and messages. It's not publicly documented. Developers reverse-engineer it by inspecting network traffic in DevTools. The linkedin-api Python library uses Voyager endpoints. LinkedIn detects non-app usage within 3–7 days and permanently bans the account — making it unsuitable for production use.

Open Chrome DevTools → Network → filter XHR → load a LinkedIn profile or search page. You'll see requests to endpoints like https://www.linkedin.com/voyager/api/identity/profiles/{id} and https://www.linkedin.com/voyager/api/search/dash/clusters. These return clean JSON with all the profile and search data the page displays.

This is what the popular linkedin-api Python library uses. It works — until LinkedIn detects the token usage pattern coming from a non-standard client. Every Voyager request requires a valid CSRF token and session cookie that LinkedIn rotates. Scripts that generate high-velocity requests or use tokens from non-browser contexts get flagged. Accounts are then restricted, then permanently banned.

The fundamental problem with Voyager: it's an undocumented internal API LinkedIn actively monitors for abuse. Every time the linkedin-api library becomes popular enough to appear in LinkedIn's abuse patterns, LinkedIn rotates the token format and the library breaks again. The GitHub repo issue trackers document this cycle clearly — hundreds of "account restricted after 2 days" reports across every major LinkedIn scraper repo. The Python scraper guide covers the exact token patterns LinkedIn detects and the rate limits that trigger restriction.

What Do Developers Actually Use Instead of the LinkedIn API?

Developers who need LinkedIn data in 2026 use four approaches: browser extensions (Clura, ~5% block rate, no API approval needed), managed cloud scrapers (Phantombuster, ~18% block rate, $56/mo), enterprise data providers (Bright Data, ~8% block rate, $500+/mo), or DIY Playwright with residential proxies (~20% block rate, account ban risk). The choice depends on volume and whether automation needs to run unattended.

Full breakdown in the LinkedIn scraping tools comparison, including per-tool deep dives, benchmark methodology, and a decision matrix by use case. For context on how LinkedIn compares to Indeed and Glassdoor on scraping difficulty, see the job board scraper comparison.

Frequently Asked Questions

Does LinkedIn have a public API in 2026?

LinkedIn has several APIs but none are publicly open for data extraction. The Marketing API is open to advertisers. The Jobs API is restricted to ATS enterprise partners. The Profile API lets you access your own profile via OAuth. There is no public API for searching LinkedIn, extracting other users' profiles, or querying job listings at scale.

What is LinkedIn API pricing?

Most LinkedIn APIs are free but access-restricted. The Marketing API is free with an active LinkedIn Ads account. The Jobs API pricing is not publicly disclosed — it's part of enterprise partnership agreements. The Profile API is free via OAuth. There is no paid tier that unlocks profile search or job extraction for third parties — the restrictions are access-based, not price-based.

How do I get a LinkedIn API key?

Apply at developer.linkedin.com. Create a LinkedIn App to get Default Access immediately — this covers OAuth login and your own profile data. For additional access (Marketing API, Jobs API), submit a partner application with a business justification. Data extraction, scraping, and research use cases are not approved. The approval process for partner access takes 4–8 weeks.

Is there a LinkedIn Jobs API for searching job listings?

LinkedIn has a Jobs API but it is a posting API, not a search API. It lets ATS partners post jobs and manage applications — it does not let you search LinkedIn's job listings or export job data. ATS partnership access is invite-only. For accessing LinkedIn job search results, browser-based scraping is the only practical option.

What is the LinkedIn Voyager API?

The LinkedIn Voyager API is LinkedIn's internal REST API used by the LinkedIn web app and mobile app. It's not publicly documented. Developers access it by reverse-engineering network requests in Chrome DevTools. The popular linkedin-api Python library uses Voyager endpoints. LinkedIn detects non-app usage within 3–7 days and permanently bans the account — making it unsuitable for production use.

Can I use the LinkedIn API for free?

The Profile API (your own data via OAuth) and Marketing API are free to use with appropriate account access. However, the APIs most developers want — job search, profile lookup, company data at scale — are not accessible at any price through official channels. The unofficial Voyager API is technically free but results in permanent account bans within 3–7 days.

How is the LinkedIn API different from the Indeed API?

Indeed shut down its public API entirely in May 2021 with no replacement. LinkedIn never fully opened its API — it's always been gated to approved partners. The practical outcome is the same: neither platform provides open API access for job data extraction in 2026. Developers use browser-based scraping tools for both platforms.

Conclusion

The LinkedIn API landscape in 2026 is a collection of purpose-specific tools for advertising, hiring, and learning workflows — none of which provide open access to the profile and job data most developers actually want. The same pattern holds across the other major job boards: Indeed shut its API in 2021, Glassdoor shut its Partner API in 2023.

The Developer Program approval process filters out data extraction use cases by design. LinkedIn's business model depends on people visiting LinkedIn.com — not on selling API access to data that would let developers bypass that entirely. Unlike B2B lead generation tools that LinkedIn officially supports, scraping use cases will never be approved.

For LinkedIn data extraction, browser-based tools are the practical alternative. The LinkedIn scraping tools comparison benchmarks 6 options by block rate and account ban risk. The Python scraper guide covers the working Playwright setup. And the job board scraper comparison puts LinkedIn in context against Indeed and Glassdoor.

Explore related guides:

• LinkedIn Scraping Tools Compared — 6 tools benchmarked by block rate and account ban risk — find the right one for your use case
• LinkedIn Scraper Python — why the unofficial API gets accounts banned and what the working Playwright setup looks like
• LinkedIn Scraper GitHub — why open source LinkedIn repos break or ban accounts
• Indeed API — Indeed shut its API in 2021 — same story, different platform
• Glassdoor API — Glassdoor's API situation — what exists and what developers use instead
• Job Listings Scraper — scrape LinkedIn Jobs, Indeed, and Glassdoor without an API — no-code workflow