OAuth Readiness
Back to all apps

LinkedIn

Library guide, researched by Claude Code agents, checked 2026-10-19. Setup not tested by hand.

For the common agent case (identify the member and post on their behalf), LinkedIn's Sign in with LinkedIn (OpenID Connect) and Share on LinkedIn products are self-serve: you add them on the app's Products tab and any LinkedIn member can authorize, with no review. The catch is what you cannot get without vetting: reading a member's posts is closed, company page and ads access need an application with legal-entity and business-email checks, and access tokens last 60 days with no programmatic refresh token unless you are an approved Marketing partner.

Tier 2: Instant, capped

Hands-on work
0.5–2 hours
Waiting for approval
None
Confidence
high

Assumes: Public app any LinkedIn member can connect, using the self-serve products only: Sign in with LinkedIn using OpenID Connect (openid, profile, email) to identify the member, and Share on LinkedIn (w_member_social) to post, comment and like on the member's behalf. Company Page management (Community Management API) and ads (Advertising API) are covered in variants because they need vetted access.

10 min1 hour1 workday1 week1 month6 months

Solid dark bar: your hands-on work. Amber: the minimum wait. Hatched: the range sources disagree on, or an open-ended wait.[1][3]

Biggest blocker: With self-serve access an agent can identify the member and post, but it can't read their posts or feed (r_member_social is closed), and anything involving company pages or ads needs a vetted application that is open only to registered legal organizations.[14][12]

Recurring: Access tokens expire after 60 days. Without partner refresh tokens, each member has to re-authorize (the consent screen is skipped if they are still logged in and the grant is still valid).[5][20]

Why tier 2? Set by: limits until reviewed.
The tier is computed from these seven facts by a fixed rule, not chosen by the AI. High: the gates that set this tier are backed by the provider's own docs or our own test.
Self-serve credentialsYesCreate an app in the Developer Portal to get a Client ID and Client Secret, then add the open products from the Products tab. Every app must be associated with a LinkedIn Page; individual developers can pick a default page.[1][3][9]
Limits until reviewedYesThere is no development-mode user cap for the open products, but access tokens last 60 days and programmatic refresh tokens are only issued to approved Marketing Developer Platform partners, so a self-serve app has to send members back through the consent flow at least every 60 days. Daily rate limits apply and aren't published.[5][6][7]
Provider reviewNoopenid, profile, email and w_member_social are Open Permissions that are 'available to all developers without special approval'. Most other LinkedIn permissions require explicit approval (see variants).[1][2]
Security assessmentNoNone of the LinkedIn docs reviewed mention a third-party security assessment for any product. (no source)
Business verificationNoThe open products need no business verification. The Community Management API does: it requires a registered legal organization, a verified business email, a verified organization website, and app verification by a Page super admin.[1][12]
Mandatory feesNoNone of the access docs reviewed mention a fee for any API product. (no source)
Partner or paid accessNoThe main scenario uses only open permissions. Sales Navigator (SNAP), Talent and Compliance programs are partner-gated or closed, and r_member_social (reading a member's posts) is closed to new requests.[1][14]

You can start today without any of this. Composio already provides a managed OAuth app for LinkedIn (linkedin), so users can connect while you work through your own app. You need your own app for your brand on the consent screen, your own rate limits, or scopes beyond the defaults. Managed auth list

If your case is different

Sign-in only (OpenID Connect)
openid, profile and email come from the self-serve 'Sign in with LinkedIn using OpenID Connect' product. There is no review and no wait. You get name, photo and email only, and LinkedIn says it doesn't verify identity.
Company Pages (Community Management API)
Vetted. Only registered legal organizations with commercial use cases can apply. You need a verified business email (personal emails fail), your organization's legal name, address, website and privacy policy, and a Page super admin must verify the app. It must be the only product on its app. Approval grants the Development tier (500 calls per app and 100 per member per day, with 12 months to finish building). Production needs a separate Standard tier review with a narrated screencast and test credentials. If you're rejected, you must create a new app to reapply. No official timeline is published. One developer reported waiting more than 40 business days for a Standard tier review.
Ads (Advertising API)
Apply from the Products tab. LinkedIn vets your company and use case, and you must complete the vetting survey within 21 days. The Development tier gives unlimited reads but edits on only 5 ad accounts. To upgrade to Standard you file a support ticket with a demo video, and LinkedIn says that review can take up to 30 business days. Matched Audiences, Audience Insights and Media Planning all require Advertising API access first.
Sales Navigator, Talent, Compliance
Partner programs. SNAP needs Sales Navigator partner approval, Talent integrations go through a partner application, and Compliance access is closed.

Steps

Agent steps an AI agent can do or draft for you. You steps that need your identity, accounts, legal authority or a real demo.

  1. Create or choose a LinkedIn Page

    You

    Every app is permanently tied to a LinkedIn Page, which acts as its publisher. Individual developers can select a default page. Use the page of the organization that will own the integration, because an app can't be moved to another page later.[9][15]

  2. Create the developer app

    You

    Sign in to the Developer Portal with your LinkedIn account, click Create App, enter the app details, select the Page and accept the API terms.[13]

  3. Send the Page verification link if needed

    You

    Settings tab > Verify > Generate URL, then send the link to a Page super admin, who has 30 days to approve. Approval can't be undone. Vetted products such as Community Management require this; the docs don't say whether the open products do.[8][10][12]

  4. Add the self-serve products

    You

    On the Products tab, add 'Sign in with LinkedIn using OpenID Connect' and 'Share on LinkedIn'. This provisions openid, profile, email and w_member_social.[1][2][4]

  5. Configure redirect URLs and the scope string

    Agent

    On the Auth tab, add absolute HTTPS redirect URLs with no fragment (query parameters are ignored). Request scope 'openid profile email w_member_social' and keep it minimal: members must accept all scopes together.[3][16]

  6. Implement the auth code flow and token re-authorization

    Agent

    Exchange the code at /oauth/v2/accessToken. Store the 60-day expiry and prompt the member to re-authorize before the token expires.[5][20]

  7. Test with your own account

    You

    Authorize with your own LinkedIn account, call /v2/userinfo and create a test post. Check the app's Analytics tab to see the rate limits for endpoints you have called.[7]

What you will need

  • A LinkedIn member account to create and own the developer app[13]
  • A LinkedIn Page to associate with the app (a default page for individual developers)[9]
  • HTTPS redirect URL(s) registered on the Auth tab[3]
  • Community Management only: a registered legal organization, a verified business email, a privacy policy, a website, and app verification by a Page super admin[12]
  • Standard tier upgrades (Community Management or Ads): a demo video or screencast, plus test credentials for Community Management[11][12]

Nuances that catch people out

  • There are no refresh tokens for self-serve apps. Programmatic refresh tokens (valid 365 days) are only for approved Marketing Developer Platform partners, and everyone else gets 60-day access tokens.[5][6]
  • Members can't pick individual scopes. They must consent to all requested scopes, and changing your app's scopes forces existing users to re-authenticate.[16][17]
  • Self-serve 'post on behalf' is write-only. Reading a member's own posts (r_member_social) is a closed permission.[14]
  • An app is permanently tied to its LinkedIn Page and can't be transferred. If you rebrand or merge, you need new apps.[9]
  • The Community Management API must be the only product on its app. If the app already has Share or Ads, you need a separate app for it.[11]
  • Rate limits are per app and per member per day, reset at midnight UTC, and aren't published. You only see them in the app's Analytics tab after calling an endpoint.[7]
  • Marketing API data has strict use rules: no use for sales, recruiting or ad targeting, no exporting, social activity stored for no more than 48 hours, and most profile data for no more than 24 hours.[18]
  • In one developer's report, the Community Management Development tier only allowed OAuth for Pages their own team administers, so customers couldn't connect until Standard tier was approved.[19]

If you get stuck or rejected

A 403 on an API call
Check that the product shows as Approved on the Products tab, that the token includes the needed scope, and that the member has the required role on the Page or ad account. Then check whether the token has expired.[11]
The Community Management access request button is grayed out
Create a new app with the same Page and request Community Management on that app alone.[11]
Community Management application rejected
You can't reapply with the same app. Fix the qualifications (business email, verified org and domain, Page verification, supported use case) and submit a new request from a new app.[12]
Vetting request closed as 'Insufficient Details'
Complete the vetting survey, and answer any follow-up, within 21 days. Use the Reapply option in the Developer Portal. If you were denied for identity vetting reasons, file a Vetting Appeal through the support contact form.[11]
The Page verification link expired or was denied
Links expire after 30 days, and a denial invalidates every link for the app. Generate a new URL from the Settings tab and send it to a Page super admin.[8][10]

Evidence

What we could not verify

  • Whether Page verification by a super admin is required before the self-serve products (Sign in with OpenID Connect, Share on LinkedIn) work for external members. The help pages say only that verification is required 'for certain functionality and products'.
  • Whether adding the self-serve products is provisioned instantly. The docs say 'self-service' but give no timing.
  • There is no official turnaround for Community Management Development or Standard tier reviews, or for the initial Advertising API review. Only the Ads Standard tier upgrade has a stated figure (up to 30 business days).
  • Default daily rate limits for the self-serve endpoints aren't published.

Sources

Each quote was checked by code against the live page. “Not found on page” means the quote may be paraphrased, so treat that claim with care.

  1. Getting Access to LinkedIn APIs
    Provider docsQuote found on pagechecked 2026-10-19
    Most permissions and partner programs require explicit approval from LinkedIn. Open Permissions are the only permissions that are available to all developers without special approval.
  2. Getting Access to LinkedIn APIs
    Provider docsQuote found on pagechecked 2026-10-19
    The following permissions are available to all developers, and may be added via self-service through the LinkedIn Developer Portal , under the Products tab on your application page.
  3. Authorization Code Flow (3-legged OAuth)
    Provider docsQuote found on pagechecked 2026-10-19
    Click the Auth tab to view your application credentials. Add the redirect (callback) URL via HTTPS to your server.
  4. Share on LinkedIn
    Provider docsQuote found on pagechecked 2026-10-19
    Select your app from My Apps , navigate to the Products tab, and add the Share on LinkedIn product which will grant you w_member_social .
  5. Authorization Code Flow (3-legged OAuth)
    Provider docsQuote found on pagechecked 2026-10-19
    Currently, all access tokens are issued with a 60-day lifespan.
  6. Refresh Tokens with OAuth 2.0
    Provider docsQuote found on pagechecked 2026-10-19
    LinkedIn supports programmatic refresh tokens for all approved Marketing Developer Platform (MDP) partners.
  7. Rate Limiting
    Provider docsQuote found on pagechecked 2026-10-19
    Your application's daily rate limit varies based on which API endpoint you are using. Standard rate limits are not published in documentation.
  8. Send an app verification request for a LinkedIn Page
    Provider docsQuote found on pagechecked 2026-10-19
    Your Page super admin has 30 days to verify the app with the unique URL. Once the Page super admin approves the request, the app is verified in your app settings.
  9. Associate an app with a LinkedIn Page
    Provider docsQuote found on pagechecked 2026-10-19
    Apps are permanently associated with a specific LinkedIn Page and cannot be transferred to another page.
  10. Approve or deny an app verification request for a LinkedIn Page
    Provider docsQuote found on pagechecked 2026-10-19
    As a Page super admin, when you approve the association to an app, you’re also taking responsibility for it. Once approval is complete, it cannot be undone.
  11. LinkedIn API Partner Support
    Provider docsQuote found on pagechecked 2026-10-19
    The review process can take up to 30 business days due to the high volume of requests.
  12. Community Management App Review
    Provider docsQuote found on pagechecked 2026-10-19
    At this time, our Community Management APIs are only available to registered legal organizations for commercial use cases only.
  13. LinkedIn API Partner Support
    Provider docsQuote found on pagechecked 2026-10-19
    Different business lines have different requirements and eligibility criteria. Some allow immediate access without approval; others require a vetting process and use-case review before access can be granted.
  14. Community Management - Overview
    Provider docsQuote found on pagechecked 2026-10-19
    r_member_social is a closed permission. We're not accepting access requests at this time due to resource constraints.
  15. Associate an app with a LinkedIn Page
    Provider docsQuote found on pagechecked 2026-10-19
    API Products available to individual developers must have a default page associated with them and you must select that default page to proceed with the app creation process.
  16. Authorization Code Flow (3-legged OAuth)
    Provider docsQuote found on pagechecked 2026-10-19
    If multiple scopes are requested, the user must consent to all of them and may not select the individual scopes.
  17. Authorization Code Flow (3-legged OAuth)
    Provider docsQuote found on pagechecked 2026-10-19
    If the scope permissions are changed in your app, your users must re-authenticate to ensure that they have explicitly granted your application all of the permissions that it is requesting on their behalf.
  18. Restricted Uses of LinkedIn Marketing APIs and Data
    Provider docsQuote found on pagechecked 2026-10-19
    Under our Data Storage Requirements , member social activity data can only be stored for 48 hours, and most member profile data can only be stored for 24 hours.
  19. Microsoft Q&A: Community Management API Standard Tier review at stage 1 for 40 business days
    Community reportQuote found on pagechecked 2026-10-19
    Development Tier restricts OAuth to Pages our own team administers, so paying customers cannot connect theirs.
  20. Authorization Code Flow (3-legged OAuth)
    Provider docsQuote found on pagechecked 2026-10-19
    To protect members' data, LinkedIn does not generate long-lived access tokens.
  21. Increasing Access (Marketing)
    Provider docsQuote found on pagechecked 2026-10-19
    Development tier is designed to build and test integrations with API call restrictions. You must complete your integration and testing within twelve months of receiving the API access.
  22. Microsoft Q&A: Community Management API Standard Tier review at stage 1 for 40 business days
    Community reportQuote found on pagechecked 2026-10-19
    Your partner support guide states a tier upgrade review can take up to 30 business days; we are now at roughly 40.
  23. Sign In with LinkedIn using OpenID Connect
    Provider docsQuote found on pagechecked 2026-10-19
    Keep in mind Sign In with LinkedIn using OpenID Connect does not verify user identities and should not be marketed as such.