People who search for a "LinkedIn API key" usually want one of two things. One is a LinkedIn developer app, so members can sign in with LinkedIn or your app can post for them. The other is public profile, company or job data for a lead list, a CRM or a recruiting tool. LinkedIn's self-serve API covers the first and very little of the second. Both are covered here, with LinkedIn's process as of November 2026.
The short answer: create an app in the LinkedIn Developer Portal, tied to a LinkedIn Page, and copy the Client ID and Client Secret from its Auth tab. Self-serve products only reach the signed-in member's own data; everything else needs a partner application. A Social Fetch key is a separate credential for public LinkedIn data.
Two different things called a LinkedIn API key
| LinkedIn's official API | Social Fetch LinkedIn routes | |
|---|---|---|
| What you get | A Client ID and Client Secret, then member access tokens | One sfk_… key |
| How you get it | Create an app tied to a LinkedIn Page, add products | Create it on the API Keys page |
| Sign in with LinkedIn, post as a member | Yes, self-serve | No |
| Other people's public profiles | Only in approved partner programmes | Yes |
| Company pages, posts, jobs | Partner or product approval | Yes |
| Limits | Daily per-app and per-member limits shown in the portal | Credits and available service capacity |
Background reading: Does LinkedIn have an API?, Social Fetch vs the LinkedIn API and the LinkedIn platform page.
How to get an official LinkedIn API key
LinkedIn's API uses OAuth 2.0. Its getting access page says most permissions and partner programmes need explicit approval; only the open permissions are available to every developer. As of November 2026 the steps are:
- Have a LinkedIn Page. LinkedIn's help centre says an app must be associated with a LinkedIn Page, and that company becomes the app's publisher. Create one for your company first if you don't have one.
- Create the app. Sign in to the Developer Portal, open My apps and click Create app. Fill in the app name, the LinkedIn Page, a privacy policy URL and a logo, then agree to the terms.
- Get the Page verified. A super admin of the Page must approve the association. They have 30 days to do it.
- Copy your credentials. Open the app and click the Auth tab. LinkedIn's OAuth documentation says each app gets a unique Client ID (which it also calls the consumer key or API key) and Client Secret. Add your HTTPS redirect URL on the same tab.
- Add products. On the Products tab, add what your app needs:
- Sign In with LinkedIn using OpenID Connect (self-serve): the signed-in member's name, headline, photo and primary email.
- Share on LinkedIn (self-serve): post, comment and like for the signed-in member.
- Advertising API and other Marketing products: apply from the same tab; LinkedIn reviews each request.
- Sales Navigator Application Platform, Talent and Learning integrations: separate partner applications.
Once a member signs in and LinkedIn returns an access token, requests carry it as a bearer token:
That call returns the signed-in member's own profile. There is no self-serve endpoint that looks up someone else by profile URL. LinkedIn lists the Compliance permissions as closed: they can't be requested at all.
LinkedIn API key vs client ID and access token
LinkedIn tutorials use "API key" for different things:
- The Client ID is what LinkedIn's docs call the API key. It identifies your app and goes in the
client_idparameter of the authorisation URL. - The Client Secret proves the request comes from your server. LinkedIn says never to pass it in a URL or post it anywhere public.
- An access token is what actually authorises an API call. Your app exchanges a member's authorisation code (valid for 30 minutes), plus the ID and secret, for a token. LinkedIn currently issues access tokens with a 60-day lifespan; programmatic refresh tokens are only enabled for a limited set of partners.
The portal also has a token generator for creating a test token by hand.
Common errors: 401 "Redirect_uri doesn't match" means the URL in your request isn't exactly the one on the Auth tab; "Invalid scope" means you requested a permission your app's products don't include.
Is the LinkedIn API free?
LinkedIn doesn't sell API access by the call, and it doesn't publish a price list. The open permissions (sign in and share) cost nothing to add. Marketing, Sales Navigator, Talent and Learning access goes through partner applications: LinkedIn decides who qualifies, and terms are set with approved partners. If your plan depends on profile or company data at scale, that approval is the hurdle, not a price.
For a longer look at the partner route against public-data lookups, read LinkedIn partner API vs public data.
LinkedIn API rate limits
LinkedIn's rate limits page sets limits per 24 hours, resetting at midnight UTC. There are two kinds:
- Application: the total calls your app can make in a day;
- Member: the total calls one member's token can make through your app in a day.
LinkedIn says standard limits are not published in its documentation and vary by endpoint. To see yours, open the app in the Developer Portal and go to its Analytics tab; an endpoint only appears there after you've made at least one call to it that day. Going over returns 429. Developer admins get an email alert when the app passes 75% of an application-level limit, typically one to two hours after it happens.
Social Fetch's LinkedIn routes have no daily request quota; requests spend credits. When capacity is full, a request may return 503 temporarily_unavailable with a Retry-After header, which isn't charged. See Credits and Errors.
Get a Social Fetch key for public LinkedIn data
Social Fetch's LinkedIn routes accept a Social Fetch key, so you don't need a developer app, a LinkedIn Page, partner approval or a member's token. They return public data as JSON. The key does not grant any permission under LinkedIn's terms; check those for your use.
- Create a free account or sign in.
- Open API Keys, type a name for the key and click Create key.
- Copy the key from the Save your API key window. It starts with
sfk_and is shown only once. - Try a profile lookup in the Playground: enter
williamhgatesin handle, then click Send. The Playground uses your signed-in workspace and spends its credits; you do not paste a key. - Store the key in an environment variable named
SOCIALFETCH_API_KEYand call the routes from your own code. Keep it on your server, out of public repositories and browser code.
Each endpoint page shows what a lookup costs, and successful responses say what they cost in meta.creditsCharged. Lookups that fail (502 lookup_failed, 503 temporarily_unavailable) are free. Plans and credit packs are on Pricing.
The LinkedIn routes most people start with:
- Profiles: a public profile with headline, experience and education.
- Companies: a company page with industry and headcount.
- Posts: a single public post or article by URL.
- Job search: public job postings by keyword and location.
The full list is on the LinkedIn platform page. These routes read public data only; they don't use a LinkedIn login or cookies, and can't post, message or reach anything visible only to a member's connections.
Which key do you need?
Get a LinkedIn developer app when members should sign in with LinkedIn, when your app posts for them, or when you're an approved partner in a Marketing, Sales Navigator or Talent programme. Those are what LinkedIn's API is built for.
Use a Social Fetch key when the job is reading public profiles, company pages, posts or jobs, for lead enrichment, recruiting research or competitor tracking, without waiting on a partner application. To see the full workflow, read How to scrape LinkedIn data. The same split applies on other networks; the Reddit API key guide walks through it for Reddit.
FAQ
How do I get a LinkedIn API key?
Sign in to the LinkedIn Developer Portal, open My apps and click Create app. Enter the app name, the LinkedIn Page it belongs to, a privacy policy URL and a logo; a super admin of that Page has to approve the association. The Client ID and Client Secret are on the app's Auth tab. Then add products from the Products tab. Only Sign In with LinkedIn using OpenID Connect and Share on LinkedIn are self-serve; the rest need LinkedIn's approval.
Can I use the LinkedIn API to get other people's profiles?
Not with the self-serve products. As of November 2026 the open permissions return the signed-in member's own name, headline, photo and email, and let your app post for that member. Access to matched member profile data is limited to approved partner programmes such as the Sales Navigator Application Platform.
Is the LinkedIn API free?
LinkedIn doesn't publish a per-call price list. The open permissions are free to add from the Products tab. Marketing, Sales Navigator, Talent and Learning integrations go through partner applications, and LinkedIn decides who gets access and on what terms.
Is a LinkedIn API key the same as a client ID?
LinkedIn's docs call the Client ID the API key or consumer key, so yes in that sense. But the Client ID alone doesn't authorise requests: your app exchanges it, the Client Secret and a member's authorisation code for an access token, which LinkedIn currently issues with a 60-day lifespan.
Do I need a LinkedIn developer app to use Social Fetch?
No. Social Fetch's LinkedIn routes take a Social Fetch key (it starts with sfk_) in the x-api-key header. They return public profiles, company pages, posts and jobs without a LinkedIn login, partner approval or member OAuth, and they cannot post or message on LinkedIn.