LinkedIn API Pricing 2026: Is the LinkedIn API Free? Access Tiers, Partner Programs, and What Actually Costs Money

TLDR: The LinkedIn API is free. LinkedIn’s API Terms of Use say the APIs “are currently provided for free” and reserve the right to charge later, and as of September 12, 2026 no product on the developer portal carries a fee. What you pay instead is access: Sign In and Share on LinkedIn are instant, everything involving company pages or ads goes through the Community Management API or Advertising API with an application, a Development tier capped at 500 calls per app per day, and a Standard tier that needs a screencast review. Tokens last 60 days, refresh tokens 365, versions rotate monthly and must be bumped at least yearly. The things that do cost money are LinkedIn’s own products (Sales Navigator, Recruiter, Premium), partner programs (Talent, Sales, Learning), and unofficial scrapers, which violate the User Agreement and have been sued out of existence.

Does LinkedIn have an API, and what does it cost?

LinkedIn has a REST API at api.linkedin.com, documented on Microsoft Learn since LinkedIn became a Microsoft company. It covers sign-in, posting as a member or a company page, reading page engagement, advertising, events, lead forms, conversions, and the data portability endpoints the EU’s Digital Markets Act forced into existence. Our two earlier guides cover the posting side in detail: the LinkedIn Posting API guide for the full OAuth and publishing flow, and how to post to LinkedIn via API for the direct-versus-unified comparison.

On cost, the primary source is Section 8.2 of the API Terms of Use:

“The APIs are currently provided for free, but LinkedIn reserves the right to charge for the APIs in the future.”

The same section adds that if a fee is introduced you are not obliged to keep using the APIs. So the honest answer to “LinkedIn API pricing” is that there is no price list. There is no free tier and paid tier, no per-call metering, no key you buy. This is different from X, which charges per post and per read since February 2026 and whose rates we broke down in the X API pricing guide, and different from the paid data APIs that Google will happily show you when you search this phrase.

What LinkedIn does instead of charging is gate. Every capability is a product you add to your app, and the products that matter require an application, a business, a LinkedIn Page, and a review. That gating, plus the rate limits and token rules that come with it, is the real cost structure, and it is what the rest of this guide lays out.

Which LinkedIn API products are free and self-serve, and which need approval?

The developer portal’s Products tab is where access is decided. This is the 2026 list, from LinkedIn’s access and permissions documentation:

Two rows cover most developers. If you only need to post as a person, Sign In plus Share on LinkedIn gives you a working integration in an afternoon with no review at all. The moment you need a company page, comments, or analytics, you are in the Community Management API, and that is where the process starts.

Two historical notes that still cause confusion. r_liteprofile and r_emailaddress were retired for new apps in 2023 and replaced by the OpenID Connect scopes and the /v2/userinfo endpoint, so any tutorial that requests them is out of date. And the “Marketing Developer Platform” that older articles describe was split: organization posting and engagement became the Community Management API in 2023, and ads stayed under the Advertising API. Both names still appear in LinkedIn’s own docs.

What does LinkedIn API access actually cost: the access-and-cost matrix

Since the fee is zero everywhere, the useful comparison is what each route costs in time, limits, and prerequisites.

The two costs that surprise teams are the Development tier ceiling and the rejection rule. Five hundred calls a day is enough to build against and not enough to serve customers; a scheduler with fifty connected pages would burn through it before lunch. And if a Standard tier application is rejected, LinkedIn’s review page says you cannot resubmit from the same app: you create a new developer app and start over, which resets your client ID and invalidates every token your users granted.

How do you get a LinkedIn API key?

There is no “API key” in the sense of a single string you buy. LinkedIn issues a client ID and client secret per app, and every call is authorised with a member access token obtained through OAuth 2.0. The steps:

1. Create an app at the developer portal. You must associate it with a LinkedIn Page you administer, even for personal-profile posting; a placeholder company page is fine.
2. Have a super admin of that Page verify the app. Until then the app is unverified and most products cannot be added.
3. Add products. Sign In with LinkedIn using OpenID Connect and Share on LinkedIn are granted immediately. Apply for the Community Management API if you need pages, comments, or analytics.
4. Set your redirect URLs, copy the client ID and secret, and run the authorization code flow to get a member token.

The app name and logo cannot contain “LinkedIn”, “Linked”, or “In”, and the application form wants a business email address; LinkedIn’s review page says personal addresses will not pass vetting. One more rule we learned building PostZen’s company-page support: the Community Management API must be the only product on its app, so a production integration ends up with two LinkedIn apps, one for OpenID Connect sign-in and one for community management, each with its own client ID.

Community Management API: what the Development and Standard tiers cost you

Every Community Management API app starts in the Development tier. The documented limits:

Getting the Development tier needs a verified business email, a verified organization with a website, and the Page verification above. Getting the Standard tier needs a finished product and a screencast. LinkedIn publishes a demo script per use case, and the recording has to show the real thing: the OAuth consent screen, a post being published and appearing on LinkedIn, comments loading with the commenter’s profile fields, and so on, for each of the categories you declared (page management, brand engagement, page analytics, executive management, employee advocacy). Reviewers get test credentials and a downloadable, high-resolution recording, and the docs recommend narration.

LinkedIn publishes no timeline for the review. The one product with a stated turnaround is the Pages Data Portability API at about seven business days; Community Management reviews are widely reported to take weeks, and the documentation states plainly that meeting the minimum requirements does not guarantee an upgrade. Budget for that. If company-page posting is on your roadmap, submit before you need it, not when a customer asks.

How long do LinkedIn API tokens last, and what does that cost?

Two lifetimes govern every LinkedIn integration:

• Access tokens last 60 days. After that, calls return 401 and the member has to go through OAuth again.
• Programmatic refresh tokens last 365 days, and only for apps LinkedIn has approved for them. The refresh token’s clock starts at the original authorization and is never extended: on day 59 a refresh gives you a new 60-day access token and a refresh token with 306 days left; on day 360 both expire in five days and the member must reauthorize.

So even in the best case, every LinkedIn user of your product reauthorizes once a year, and in the common case (no refresh tokens) every 60 days. That reauthorization is a product cost: a scheduled post that lands after the token expired fails, and the user has to notice. PostZen’s LinkedIn connection stores both expiries, marks the account as needing reauthorization when a token stops working, and fires an account webhook so your app can prompt the user instead of discovering the failure in a stalled queue. LinkedIn’s docs also reserve the right to revoke either token at any time for technical or policy reasons, so the fallback to a fresh login has to exist regardless.

A related gotcha: a refresh never grants new scopes. If your app gains a permission after a user connected, that user must reauthorize to grant it, which is why adding company-page support to an existing integration means asking every user to reconnect.

LinkedIn API rate limits and versioning: the maintenance cost

LinkedIn’s rate limiting page says something few platforms admit: standard rate limits are not published. Each endpoint’s limit is shown per app in the developer portal’s Analytics tab as two numbers, an application limit and a member limit, both per day, resetting at midnight UTC. Exceeding either returns HTTP 429. Developer admins get an email at 75% of the application quota, delayed by one to two hours, and there is no member-level alert. The figure of 150 posts per member per day that circulates in tutorials is not on any current LinkedIn page; treat your Analytics tab as the source of truth and the Development tier numbers above as the only published caps.

Versioning is the other recurring cost. Every call to the versioned /rest/ base path must carry a Linkedin-Version: YYYYMM header. There is no default: omit it and the request errors. LinkedIn releases a version every month and supports each for a minimum of one year, after which it is sunset and calls with that header error too. The current version is 202608 (August 2026), and the August 2025 version was sunset on August 17, 2026. In practice that means a yearly engineering task: read the migration notes, bump the header, and retest. PostZen’s LinkedIn publisher pins a version constant and bumps it on that schedule; it is one of the few platforms where “do nothing” breaks an integration on a known date.

What LinkedIn products get confused with API pricing?

Searching for LinkedIn API cost turns up prices for things that are not the API. None of these unlock any API access, scope, or rate limit:

• Sales Navigator is a per-seat subscription for salespeople. Its API, the Sales Navigator Application Platform, is a separate partner program, free as an API but available only to approved partners whose customers hold Sales Navigator licenses.
• Recruiter and Recruiter Lite are per-seat recruiting products. The Talent Solutions APIs (Recruiter System Connect, Apply Connect, Apply with LinkedIn) are partner programs for applicant tracking systems, again with no API fee but a partner application.
• Premium Career and Premium Business are consumer subscriptions with no developer component at all.
• LinkedIn Learning has an API, but access requires being a Learning partner or an organization with a Learning site license.
• The LinkedIn Marketing Partner Program is a badge for agencies and ad-tech vendors with a track record; it is not an API tier.

If a page quotes a monthly price for “the LinkedIn API”, it is either selling one of these products, an unofficial scraper, or a wrapper.

Unofficial LinkedIn APIs and scrapers: what they cost and why they end

The paid “LinkedIn APIs” on marketplaces like RapidAPI are scrapers: services that log in with pools of accounts or crawl public pages and resell the data, typically for tens to hundreds of dollars a month depending on volume. They violate LinkedIn’s User Agreement regardless of whether the data is public, and LinkedIn litigates:

• hiQ Labs v. LinkedIn ran from 2017 to a settlement in December 2022. hiQ accepted a permanent injunction against scraping and agreed to destroy the data, with a judgment for LinkedIn on breach of contract and related claims. The case is remembered for an early appellate ruling favourable to scraping public data; it ended as a loss for the scraper.
• LinkedIn v. Nubela (Proxycurl) was filed in January 2025, alleging fake-account scraping resold through an API. Proxycurl settled and shut its API down in July 2025 after reaching a reported eight-figure annual run rate.

For a product, that history is the cost: any feature built on a scraper has an end date you do not control. The official API’s gating is slower and narrower, but the access it grants does not evaporate in a settlement.

What the free LinkedIn API cannot do

Free and approved still leaves gaps, and knowing them up front saves an application:

• No reading a member’s own feed or posts beyond what your app published. r_member_social is closed; LinkedIn’s docs say access requests are not being accepted.
• No comments or reactions on personal posts. r_member_social_feed is restricted to partners, so engagement reads work on company-page posts only.
• No messaging. There is no InMail or DM API for third parties.
• No polls, articles, newsletters, or events through the Posts API.
• No editing a published post’s text; delete and recreate.

PostZen’s LinkedIn platform docs list these under “what you can’t do” because they are LinkedIn’s limits, not ours.

Posting to LinkedIn through PostZen instead of applying yourself

If the reason you are pricing the LinkedIn API is to publish, the unified route sidesteps the application. PostZen holds the developer apps, the Community Management API relationship, the version header, and the token expiry handling; you connect a member (and the company pages they administer) through a hosted OAuth link and send one request:

curl -X POST https://api.postzen.dev/v1/posts \
  -H "Authorization: Bearer $POSTZEN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "We are hiring two backend engineers. Details and how to apply in the first comment.",
    "publishNow": true,
    "platforms": [
      {
        "platform": "linkedin",
        "accountId": "jh72r5nqk9wx3v8m1t4cz6bs0fy5dg3e",
        "settings": {
          "organizationUrn": "urn:li:organization:12345",
          "firstComment": "Apply at https://example.com/careers"
        }
      }
    ]
  }'

Text up to 3,000 characters, up to 20 images, one video up to 500 MB, or one document up to 100 MB, with the media upload and register steps handled for you. Drop organizationUrn to post as the member. The same request accepts nine other platforms, which the social media API page and our comparison of social media APIs cover; the LinkedIn integration page lists what the LinkedIn target supports, and PostZen’s plans are on the pricing page.

The LinkedIn API is free. Access to it is not effortless, and the maintenance is not zero. Decide based on whether you want to own that relationship or rent it.