in LinkedIn API Live in production. Email, messengers & calendars next
Infrastructure
Messaging
Scraping
Enrichment data
Documentation Browse all docs →
QuickstartOne key, first call in 2 min MCP serverTyped tools for any agent API referenceEvery endpoint & schema WebhooksEvents, retries, signatures
GTM engineersConnect any agent to your GTM process AI SDRRun an autonomous SDR on real infrastructure AgenciesOnboard clients safely, run from your stack PlatformsAdd LinkedIn on proven infrastructure LinkedIn automationSafe connects, messages & follow-ups Account providersWarm, secure & lease account fleets
Pricing Blog
Get API key Sign in
Guides

How to Get LinkedIn API Access in 2026 (What’s Self-Serve, What Isn’t)

Developer Guide · API access

How to Get LinkedIn API Access in 2026 (What’s Self-Serve, What Isn’t)

Creating the app takes ten minutes. Getting permission to call anything useful with it is the part with no timeline.

Updated August 2026 · 9 min read

Two LinkedIn API products are self-serve: Sign In with LinkedIn and Share on LinkedIn. Everything else requires approval into a partner program, and several of those programs stopped taking applications. You create a developer app in minutes, then request products on it one at a time, and each request goes to a review you do not control.

One naming point sends people in circles before they start: LinkedIn issues nothing called an API key. An app gets a Client ID and a Client Secret on its Auth tab, and every call carries an OAuth access token minted from those. Searching for a LinkedIn API key lands you on that tab.

On this page

  1. What you can get without asking anyone
  2. Creating the app and requesting a product
  3. Development tier and Standard tier
  4. The programs that are closed
  5. What approval still will not let you do
  6. Getting a key for outreach instead
  7. Frequently Asked Questions

What you can get without asking anyone

The self-serve surface is two products. Sign In with LinkedIn using OpenID Connect authenticates a member and returns their name, picture, locale and, where granted, their email. Share on LinkedIn posts, comments and reacts as the authenticated member on their own feed, through the w_member_social permission. Both are usable the moment your app exists.

Verified on LinkedIn is a partial third. Its Development tier needs no approval, which makes it a way to test identity checks before applying for the Lite tier.

Creating the app and requesting a product

You cannot create a usable app without a LinkedIn Page you administer, so a solo developer’s first job is creating a Page for a company of one.

  1. Create or claim a LinkedIn Page for the company the app belongs to. A personal profile will not do.
  2. Create the app at linkedin.com/developers/apps/new and associate it with that Page.
  3. Verify the association. A super admin of the Page confirms it. Until that happens the app stays unverified and products cannot be granted.
  4. Request products from the app’s Products tab. Each product has its own access form, and the self-serve two are granted on request.
  5. Generate a token with the portal’s Token Generator, and check what a token actually carries with the Token Inspector, which only reads tokens issued by the app you have selected.

Business Verification sits on top of this for some products, including the EU data-portability program, and asks for legal name, registered address, website, privacy policy and a verified business email before review.

Development tier and Standard tier

Approval into a program does not put you in production. Marketing apps start in a Development tier meant for building and testing, with a 12-month window to finish the integration, and move to Standard tier only after you raise a request through the developer support portal. LinkedIn states plainly that meeting the minimum requirements does not guarantee the upgrade.

Development tiers are quota-limited as well, and Community Management adds two restrictions on top of its quota: batch operations are blocked and webhook push notifications are disabled. Standard tier removes both. The published figures, for the three products that have any, sit on the LinkedIn API rate limits page.

Everything else about your quota stays invisible until you call the endpoint, which is its own design problem.

The programs that are closed

Three programs are shut and one is restricted as of August 2026, and LinkedIn’s own sub-pages have not all caught up with that.

Program Status What that means for a new build
Sales Navigator (SNAP) Closed to new partners The overview page carries the notice. Some of its own sub-pages still invite applications and are stale
Job Posting API Not accepting new partnerships Existing Talent Solutions partners with a signed agreement continue
Compliance API Closed to new applications Messaging and network capture for regulated firms, no route in
Matched Audiences Up to 60-day review Advertising API access first, then a separate review
Marketing, Talent, Learning Partner application Open, with qualification criteria and no published timeline

The SNAP closure is the one that reshapes plans most, because Sales Navigator is where sales tooling expects to integrate. What SNAP did and did not do, and what teams use now, is covered on the Sales Navigator API page.

What approval still will not let you do

Approval widens the fields you can read. It does not lift the rules on what you may keep or do with member data, which ride with the sign-in and profile surfaces rather than with your partner status. LinkedIn’s restricted-use-cases policy, last updated on 29 August 2025, caps storage of most member profile data at 24 hours and social activity data at 48, forbids exporting member data from your application “including to your customers”, and rules out use “for advertising, sales, or recruiting use cases”, naming lead creation, CRM enhancement, audience building and mass messaging.

Nothing in the official catalogue sends a connection request or a member-to-member message. No product in the current catalogue exposes it, at any tier. Teams that need it connect a LinkedIn account to a third-party API instead, and that trade is what the LinkedIn API guide compares in full.

Getting a key for outreach instead

An account-based API asks LinkedIn for nothing at the platform level. It acts as a LinkedIn account you connect and control, so the constraint moves from a review board to the account itself. That is a real trade and not a loophole: LinkedIn’s Terms of Service do not permit third-party automation, so every provider in this category carries that risk, and what separates them is how hard the engine works to keep an account inside its ceiling. gtm-api.com, Unipile and Linked API all work this way. GTM API reports 20,000+ connected accounts at under a 1% monthly ban rate on the stack underneath.

  • Sign up and connect an account. You authenticate in a cloud browser session yourself rather than handing over a password or pasting a cookie, and that session keeps one fingerprint and one IP for the life of the account.
  • Mint a key. Keys are prefixed gtm_live_, shown once, and stored hashed. They are team-scoped and carry an explicit permission list.
  • Rotate without downtime. A rotate swaps the secret in place and leaves the old one valid for a grace window, so deploys do not race the change.
  • Delegate down, never up. A key with key-management permission can mint a narrower child key, and narrowing or revoking the parent immediately downscopes the child.
  • Free plan to start. One connected account, with the API, MCP and CLI all available. Paid plans start from $10 per account at volume.
first callbash
# full reference: docs.gtm-api.com
curl -X POST https://app.gtm-api.com/linkedin/v4/api/linkedin-accounts/search \
  -H "Authorization: Bearer $GTM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "page_size": 5 }'

The same key drives the MCP server at mcp.gtm-api.com, so an agent in Claude, ChatGPT, Cursor or n8n reaches the same tool surface without separate credentials. Setup is on the LinkedIn MCP server page.

Frequently Asked Questions

How do I get a LinkedIn API key?

Create a LinkedIn Page, create an app at linkedin.com/developers/apps/new and associate it with that Page, have a Page super admin verify the association, then request products from the app’s Products tab and generate a token. Sign In with LinkedIn and Share on LinkedIn are granted on request. Every other product goes to a partner review.

How long does LinkedIn API approval take?

LinkedIn publishes a timeline for one program only: Matched Audiences states a review of up to 60 days. The other partner programs give no published turnaround, and LinkedIn states that meeting the minimum requirements does not guarantee approval. Plan the integration so that a rejection or a long silence does not block the rest of the build.

Do I need a LinkedIn Company Page to create a developer app?

Yes. An app is associated with a Page at creation, and a super admin of that Page has to verify the association before products can be granted. A personal profile cannot stand in for the Page, which is why solo developers usually create a Page for the project first.

What can I build with self-serve LinkedIn API access?

Sign-in and publishing. You can authenticate members, read the signed-in member’s name, picture, locale and email, and post, comment or react as that member on their own feed. You cannot read another member’s profile, search people, send a connection request or send a message, at any tier.

Which LinkedIn partner programs still accept applications?

Marketing, Talent and Learning do, with qualification criteria and no published turnaround. The Job Posting API inside Talent Solutions is not taking new partnerships, and the Compliance API is closed to new applications. Sales Navigator is a separate case covered on the Sales Navigator API page.

Sources & Further Reading

Skip the approval queue.

Connect an account you own, mint a key, and send your first message from REST or an AI agent the same day. GTM API reports 20,000+ accounts at under a 1% monthly ban rate. Free plan, then from $10 per account at volume.

Get your API key →

Michael SalamatovMichael SalamatovGTM engineerRuns the GTM API blog. Covers LinkedIn limits, account health and the API side of outbound.in

Last updated: August 2026 · Access states, tiers and program statuses verified against LinkedIn’s developer documentation on 14 August 2026