LinkedIn Won’t Give You Posting Access Just Because You Built the App
The Community Management API powers scheduling, posting, and engagement tools for LinkedIn Pages. But you can’t simply request a token and ship. Access is gated behind a two-tier app review, a registered company, and a verified Page — and that is where most integrations stall.
If you are building a SaaS scheduler, a social-engagement tool, or an agency dashboard that posts to LinkedIn on behalf of clients, the Community Management API is the official path. It is also one of the more demanding API approvals in the social space. Adding sign-in is a different product from the Community Management API, and our Sign In with LinkedIn (OpenID Connect) guide covers the setup, scopes, and where apps get stuck. Unlike a quick OAuth app, LinkedIn vets the company behind the integration, not just the code. This guide explains the Development and Standard tier structure, what LinkedIn actually checks, and the common reasons access requests get delayed — so you know what you are walking into before the clock starts.
The two tiers you have to pass through
Community Management API access is not a single yes/no. There are two distinct tiers, and you must move through them in order.
Development Tier
For building and testing your integration. It comes with API call restrictions and a hard deadline: you are expected to complete your integration and upgrade within twelve months of receiving access.
Standard Tier
For live production use with no call restrictions. Reaching it requires a separate access request form and a screen recording of your app demonstrating each stated use case.
The 12-month trap
If you don’t apply for Standard tier within twelve months of getting access, LinkedIn removes your API access for inactivity. Many projects discover this only after they’ve stalled.
Why “just fill the form” is harder than it sounds
The biggest surprise for developers is that the Community Management API is not available to individuals at all. It is reserved for registered legal organizations with commercial use cases — and LinkedIn confirms that by reviewing your company, not just your app.
Registered company only
Access is limited to legally registered entities such as LLCs, corporations, or non-profits. Solo developers and unregistered side projects are not eligible.
Verified LinkedIn Page
A super admin of the LinkedIn Page tied to your organization has to verify your application. No verified Page, no access.
Business identity checks
You must supply — and verify — a business email, plus your organization’s legal name, registered address, website, and privacy policy. Mismatches stall the review.
What LinkedIn actually reviews
This is the part teams underestimate. Every developer completes an access request form, and LinkedIn manually vets both the developer and the app to confirm the API will be used within its terms and supported use cases. Reviewers want a clear company and product overview, a precise description of your use case, and working test credentials so they can see the integration in action. The review is done by hand and commonly takes one to four weeks — longer if anything is unclear or inconsistent. Gaps between what you describe and what your app actually does are the fastest route to a delay. Preparing a clean, accurate, policy-aligned submission is the real work, and it is where dedicated LinkedIn API setup support saves weeks.
How the access process works (high level)
- Confirm eligibility firstMake sure you have a registered legal entity and a verified LinkedIn Page before you start — these are non-negotiable gates, not paperwork you can add later.
- Create the app and add the productIn the LinkedIn Developer portal, create your app, associate it with your verified Page, and add the Community Management API product to begin the access request.
- Complete the Development tier access formProvide your business identity, company and product overview, use-case description, and test credentials. LinkedIn reviews and vets the submission.
- Build and test within the windowUse Development tier to complete your integration — while staying inside the call restrictions and the twelve-month clock.
- Apply for Standard tier with a screencastSubmit the Standard tier access request form plus a screen recording demonstrating each use case exactly as described. Approval lifts the restrictions for production.
We deliberately keep the exact form wording, the per-use-case framing, and the screencast script out of this article — that preparation is the service. Getting any of it wrong usually means weeks of back-and-forth or a rejected access request.
The outcome teams are aiming for
The goal is not just a token. It is an approved, production-ready integration that clears app review the first time and reaches Standard tier well inside the twelve-month window — so your product can post and manage LinkedIn Pages at scale without interruption.
Common reasons access requests stall or fail
- Not a registered entity. Applying as an individual or an unregistered project — instantly ineligible.
- Unverified or mismatched Page. No verified LinkedIn Page, or a Page whose details don’t match the legal organization on the form.
- Vague use case. The access form doesn’t clearly explain what the app does or which endpoints it needs and why.
- Weak screencast. The Standard tier video doesn’t demonstrate every stated use case, or shows behaviour that differs from the form.
- Missing the 12-month upgrade. Staying on Development tier too long and losing access to inactivity.
LinkedIn API access often runs alongside other platform approvals — Meta App Review, Google OAuth verification, and similar. If you are juggling several at once, see our broader API approval services for how they fit together, or get in touch to talk through your specific integration.
Note: The final decision on any LinkedIn API access or tier upgrade rests solely with LinkedIn. This service provides preparation and submission support aligned with official LinkedIn API terms and policies; it does not guarantee an approval outcome.