← library
Partner-gated
Social / marketing·curated + hand-verified·checked 2026-10-28
difficulty
4/5

Sign-in and posting as a member are instant. Anything with company pages, ads or analytics requires LinkedIn to vet your business, and a rejection means starting over with a new app.

First working connection
~30 minutes (Sign In + Share on LinkedIn)
Production / approved
Member features: same day · Org pages: vetting + Development tier + Standard tier review (no SLA)
Composio managed OAuth
Available: ship today
Composio offers a managed LinkedIn app. Check which LinkedIn products/scopes it includes before relying on it for page management.
who does itagent 2you 4provider 0
evidencetested 3sourced 22inferred 3

01Pick your path

Self-serve products
when Sign in with LinkedIn (openid, profile, email) and posting as the member (w_member_social).
→ Add from the Products tab and it's available immediately.
Community Management API
when Post/read as a company Page, comments, analytics.
→ Access request vetted by LinkedIn → Development tier (rate-limited, 12-month build window) → Standard tier review with screencast.
Other partner programs (Ads, Sales Navigator, Talent)
when Marketing, sales, or recruiting integrations.
→ Separate applications. Some are closed to new partners.

02Time & effort

Hands-on work
~5 workdays – ~15 workdays
Waiting on others
3 weeks – 10 weeks
You're actually working
7% of elapsed time
Phases
5
start↑ first working connection, then production pathproduction
  1. DEVCreate app, associate a LinkedIn Page, add self-serve products15–30 minutessourced[li-access]
  2. PRODPage admin verifies the appwait 0–2 dayssourced[li-cmreview]Needs a super admin of the company Page.
  3. PRODDevelopment tier access request vettingwait 1–4 weeksinferred[li-cmreview]No published SLA.
  4. PRODBuild integration under Development tier limits1–3 weeksinferred[li-increase]
  5. PRODStandard tier review (screencast + test creds)wait 2–6 weeksinferred[li-cmreview]No published SLA.
agent can do it you waiting on providerbar widths ∝ √time, so short tasks stay visible

03Steps

0/6 done

Get a working connection

  1. Map features to LinkedIn products before writing codeagentsourced[li-access][li-increase]

    Member sign-in and posting as yourself are self-serve. Company Page posting/analytics is Community Management API. Ads/Sales/Talent are partner programs. This mapping decides whether you wait.

  2. Create the app in the Developer Portalyousourced[li-cmreview]

    Associate it with your company's LinkedIn Page. A Page super admin must verify the association.

    ↗ www.linkedin.com/developers/apps/new
  3. Add 'Sign In with LinkedIn using OpenID Connect' and 'Share on LinkedIn'yousourced[li-access]

    Products tab. Grants openid/profile/email and w_member_social without approval.

Make it production-ready

  1. Check your use case isn't restrictedagentsourced[li-cmreview]

    LinkedIn lists restricted use cases (e.g. scraping-like or data-resale patterns). An agent can compare your product description against them before you apply.

    ↗ learn.microsoft.com/en-us/linkedin/marketing/restricted-use-cases
  2. Apply for Community Management API (Development tier)yousourced[li-cmreview]

    Registered legal organization, commercial use case only. Have ready: verified business email, legal name, registered address, website, privacy policy.

  3. Build within Development tier limits, then apply for Standardyousourced[li-increase][li-cmreview]

    Development tier is rate-limited and expects you to finish within 12 months. Standard needs a narrated screencast of each use case (incl. full OAuth flow) and test credentials.

    ◆ prepared by agent · Screencast checklist (Standard tier)
    1. Close all other windows. Record only your app.
2. Narrate throughout.
3. Show a user approving access to their LinkedIn Page via the full OAuth flow (consent screen visible).
4. Show posting to the Page via your app.
5. Show each additional use case you selected in the form (e.g. reading comments, analytics).

04Requirements, scopes & nuances

You'll need

  • ▸Community Management API: registered legal organization, commercial use only. sourced[li-cmreview]
  • ▸Verified business email, legal name, registered address, website and privacy policy. sourced[li-cmreview]
  • ▸App verified by a super admin of the organization's LinkedIn Page. sourced[li-cmreview]
  • ▸Development tier: limited API calls per 24h (500/app). Integration must be completed within 12 months. sourced[li-increase]

Gotchas

  • !Rejected? You can't re-apply with the same app. LinkedIn says to create a new app and submit a new request. sourced[li-cmreview]
  • !Changes to your app's functionality after review may require re-review. sourced[li-cmreview]
  • !LinkedIn may decline to upgrade you 'at its discretion' even if you meet the minimum criteria. sourced[li-increase]
  • !Marketing API versions sunset on a schedule (e.g. 202511 sunsets Nov 16, 2026). Pin and track versions. sourced[li-increase]
Scope / permissionTierNoteEvidence
openid profile emailbasicSign In with LinkedIn (OIDC). Self-serve.sourced[li-access]
w_member_socialbasicPost/comment/like as the member. Self-serve.sourced[li-access]
w_organization_social, r_organization_social, …gatedCommunity Management API. Vetted access.sourced[li-increase]
r_compliance / w_compliancegatedClosed. Cannot be requested.sourced[li-access]

05If you get blocked

✕Need company-page features but you're a solo developer or pre-incorporation.sourced[li-cmreview][composio]

→ Community Management API requires a registered legal org. Ship member-level features (w_member_social) first, or use a managed provider whose app already has access, if its terms allow.

✕Development tier rate limits during testing.sourced[li-increase][li-cmreview]

→ Cache aggressively, test with few members, and move to Standard tier only after the integration is complete (the form requires it).

06Evidence: what was tested, sourced, and still uncertain

$ probes: live GETs with a dummy client_id, no credentials
✓ OIDC discovery document → 200
https://www.linkedin.com/oauth/.well-known/openid-configuration
authorization_endpoint = https://www.linkedin.com/oauth/v2/authorization
∴ Standard OIDC for sign-in. Endpoints confirmed.
✓ Authorize endpoint with a fake client_id → 200
https://www.linkedin.com/oauth/v2/authorization?response_type=code&client_id=probe_invalid&scope=openid
HTML page returned
∴ Endpoint is live and validates the client in its UI.
✓ Old docs URL → 404
https://learn.microsoft.com/en-us/linkedin/marketing/community-management/community-management-api-access
Page not found
∴ Access docs moved to /linkedin/marketing/community-management-app-review. Older guides link dead pages.

Sources read

  1. [li-access] LinkedIn (Microsoft Learn) — Getting access to LinkedIn APIs official
  2. [li-increase] LinkedIn — Increasing access (Marketing API tiers) official
  3. [li-cmreview] LinkedIn — Community Management App Review official
  4. [composio] Composio — Managed OAuth apps directory official
  5. [probe] Live HTTP probes run by the agent (dummy client_id, no credentials) probe

Still uncertain

  • ? LinkedIn publishes no review SLA for Development or Standard tier. Our week ranges are estimates.
  • ? We could not confirm which LinkedIn products Composio's managed app has been granted.
  • ? We did not submit an access request.