Is the LinkedIn API free? The honest answer for builders in 2026

Say you are a solo founder building a recruiting tool. You register a LinkedIn developer app on a Monday, wire up OAuth before lunch, and fire your first API call. What comes back? Your own name, your own photo, your own email address, and nothing else. That is the entire free, self-serve LinkedIn API. To read anyone else's profile, search for people, or pull company and job data, you have to clear a partner review most applicants never pass, or sign a commercial contract you cannot even apply for as a small team.

So the honest answer to "is the LinkedIn API free" is yes and no, and the gap between the two is the whole story. LinkedIn charges no per-call fee, and the application itself costs nothing. But the free tier only covers a login button and the profile of the person who just logged in, and even that profile is a fixed set of OpenID Connect claims: sub, name, given_name, family_name, picture, email, email_verified, and locale. No headline, no connections, no one else. Everything a business actually wants sits behind approval, and the tiers that matter most are commercial partnerships you cannot self-serve into at all.

This guide gives the direct answer first, then the access-tier table with what each one really costs, then the part that decides your project: the six things you can genuinely build for free versus the three no tier will unlock at any price.

The direct answer: free to call, gated to access

LinkedIn's own API Terms of Use state that it currently does not charge a fee for use of the APIs, though it reserves the right to in future (LinkedIn API Terms of Use, as of 2026). That single sentence is where the idea of a "free LinkedIn API" comes from, and it is technically true. There is no invoice for making a request.

What costs you is access. LinkedIn gates its APIs behind tiers, and only the lowest tier is self-serve. The rest require an application that is reviewed and frequently rejected, or a signed commercial partnership reserved for enterprise vendors. "Free to call" means nothing if you cannot get approved to call the endpoint you need. Price is not the wall here. Approval is.

LinkedIn API access tiers, and what each one really costs

Here is the picture that matters, organised by tier rather than by endpoint. The load-bearing column is not the price, it is who actually gets in.

Read the cost column and the myth dissolves. Nothing in that table has a sticker price, which is exactly why "is it free" is the wrong question. The Sales Navigator, Talent, and Compliance tiers are not free or paid in any menu sense, they are partnerships, and for a solo developer or an early-stage product the odds of reaching them are effectively zero. The endpoint-by-endpoint version of this map, with approval odds for each, lives in the companion piece on LinkedIn API endpoints without approval.

Six things you can build for free, and three you cannot

This is the table to keep. It answers the real question behind "is the LinkedIn API free," which is not about invoices, it is "can I build the thing I have in mind without paying and without a partner contract." Six of these are genuinely reachable. Three are not, at any tier, at any price.

The split is the actual answer to the search. The free API tier does very little on its own, but the compliant lanes around it, public data and your own session, cover most of what people were hoping the API would do. The three "no" rows are the ones the SERP quietly implies are available and are not.

What "free" actually costs: the approval wall

The one gated tier a normal company can realistically clear is the Marketing Developer Platform. It uses a two-step model: every app starts on a Development tier that can build and test against a handful of ad accounts, and a Standard tier you request once your integration meets the business-line requirements (LinkedIn Marketing API docs, Microsoft Learn, as of 2026). To move up you submit a video demonstrating your product creating, editing, and optimising LinkedIn ad campaigns, and LinkedIn quotes the review at up to 30 business days, longer in practice. Thin applications are commonly rejected, and LinkedIn states it can decline an applicant even when every listed requirement is met.

The bar is a real product with active users and a marketing use case that complements LinkedIn's ad business rather than competing with it. Social media schedulers, ad-reporting platforms, and page-management vendors clear it. A prospecting use case, "read profiles to build a list," does not, because that is not a marketing use case in LinkedIn's sense. So the free tier is free in the way a lottery ticket is cheap. The price is not money, it is the probability of approval, and for the most-wanted use cases that probability is low.

The compliant lanes that need no approval at all

Step back from the API question and the path clears. Most of what you want to do with LinkedIn data does not need the partner API, because it splits cleanly into two lanes that need no approval.

The first is public data. Public LinkedIn pages, profiles, company pages, posts, and job listings are readable the way a browser reads them, without acting as anyone and without a connected account. This is where finding and qualifying belong. Reading a public page from a server does not operate an account, so there is no account to expose. A free LinkedIn people search tool runs entirely on this lane: you get results with nothing signed in and nothing at risk. It is not the partner API and it does not pretend to be one; a public page fetched from a server is public data, the same bytes a logged-out browser sees.

The second is your own session. Sending a connection request or a message happens through an account you control, at the one point where an account is genuinely required. The discipline that keeps that account safe is pacing: LinkedIn caps connection invitations at roughly 100 per week (LinkedIn Help, as of 2026), and staying under that ceiling matters far more than any API tier.

There is a third, paid lane worth naming honestly. A category of vendors sells what they call a LinkedIn API by having you hand over a session, then replaying it from their servers to reach the gated data the partner API will not give them. Unipile is a clean example of that model, and it is a legitimate product for what it is. It is also not free, starting around EUR 49 per month on its own published pricing (Unipile pricing, as of 2026), and it concentrates account risk, because your session is now active from an IP that is not yours on a schedule you did not set. What that model costs and how it compares is broken down in the Unipile LinkedIn API pricing piece and the BeReach vs Unipile comparison.

The free-to-start path: an MCP agent inside Claude

If your real goal is outreach rather than a raw integration, the six-and-three table above is effectively the product spec. BeReach is built along those exact lines. Every reachable row, finding people from public pages, qualifying a prospect from a public profile or company page, drafting the message, runs on the public lane with nothing connected and no API tier in play. A LinkedIn session enters at one row only, the actual send, which is the single place any honest tool needs one. That is what cookieless until outreach means here: not a slogan, but the plain fact that the finding and qualifying you wanted the free API for never required an account to begin with, so BeReach does not ask for one until you send.

For builders that surfaces two ways. There is a REST layer of 135 operations behind a BEREACH_API_KEY, documented at the BeReach API landing, covering the public find and qualify operations plus the paced account actions. And there is a 33-tool MCP connector at mcp.bereach.ai that runs inside Claude.ai and Claude Cowork, so an AI agent can do the finding and drafting conversationally and hand you drafts to approve before anything is sent. The deeper walkthrough is in the guide to the LinkedIn MCP server for Claude.

You can start for free. The free tier includes 100 monthly credits with a hard cap and no card, enough to run the public find-and-qualify loop and see real results before you connect anything. When you do move to sending, one included AI model handles the drafting, so there is no key to bring and no model to pick, and the account actions are paced under conservative daily budgets that sit below LinkedIn's own weekly invitation ceiling. The edge is less account exposure, not more automation. Current plan pricing lives on the pricing page.

The short version

Is the LinkedIn API free? Free to call and free to apply for, yes. Free to access in any way that matters, no. The only genuinely open tier is Sign In with LinkedIn, which returns the profile of the person who just logged in and nothing more. The tiers that expose real data are partner-gated, and three of them are commercial contracts a small builder will not reach. But the six things most people actually want, finding, qualifying, and outreach, are reachable without any of it: public data for the finding and qualifying, your own paced session for the send. Build around that split and the approval wall stops being your problem.