LinkedIn's Community Management API caps new company-page apps at 500 calls a day
LinkedIn charges nothing per API call, but posting to a company page needs Community Management API approval and starts at 500 calls a day per app. A dev.to write-up of LinkedIn's docs says teams should also budget for yearly version and connection renewals.
The Engineer · Build desk
Key figures: at most 125 one-image posts a day across all of an app's customers; 500 calls a day for the whole app, shared by all of its customers; and four requests per one-image post in the author's SDK, with statistics and comments requests on top.
| Figure | Value | Note | Claim |
|---|---|---|---|
| One-image posts a day, at most, across all customers | 125 posts a day | 22 | |
| Calls a day, whole app | 500 calls a day | shared by all the app's customers | 10 |
| Requests per one-image post, in the author's SDK | 4 requests | statistics and comments come on top | 11 |
What happened
- Posting to your own profile needs no review: Share on LinkedIn gives any app the w_member_social permission, which is enough to publish as whoever authorizes it.
- Before granting the Development tier, LinkedIn approves the use case, verifies the team's business email, organization, website and domain, and requires a Page super admin to verify the app.
- A rejection is final for that app, so a team that fails the Development tier review has to create a new app and start over.
- The Development tier has a clock: developers get twelve months to apply for Standard, after which LinkedIn removes access for inactivity.
- The oldest API version still in the documentation, 202510, is sunset on October 15, 2026.
Why it matters
- cost With no per-call fee, the cost is staff time, and it lands up front: the entity review, then the Standard application, then a version bump every year.
- constraint A multi-customer scheduler on one Development-tier app will reach the shared pool before it gets the Standard-tier features that cut call volume, so the Standard review belongs on the roadmap from day one.
- contradiction LinkedIn's own pages disagree: Share on LinkedIn still documents /v2/ugcPosts while the Posts API at /rest/posts replaces it, so code copied from the older page starts on a replaced endpoint.
- decision The write-up's advice is to keep the version in one constant, calendar its sunset date, and run at least one test against the real API, because mocked tests keep passing after a version is retired.
According to the dev.to write-up, LinkedIn's review page says "our Community Management APIs are only available to registered legal organizations for commercial use cases only" [4]. Personal email addresses fail the vetting, so a side project has no route to a company page [5]. LinkedIn's developer documentation lists tiers and reviews, but no price list and no paid plan that buys more calls [6].
The 500 calls a day belong to the app, so every customer of a multi-tenant product draws on one pool [10]. The author's own SDK needs four requests to publish a post with one image: it opens an upload, transfers the image bytes, fetches the image back, then creates the post [11]. At that rate 500 calls allow 125 posts a day across all customers [22]. Statistics and comments requests come on top [11]. The four-request count is one SDK's. For 125 to transfer, another client would have to make the same four calls and spend nothing else from the pool.
Two more limits sit in the Development tier. Batch reads (BATCH_GET) are blocked, and webhooks for social actions stay off until Standard [12]. Standard asks for test credentials, a high-resolution screencast of a user going through the full OAuth flow and each declared use case, a valid privacy policy, and compliance with LinkedIn's data storage rules [13].
Version renewal happens in a request header. LinkedIn publishes a version every month, in YYYYMM format, and supports each for at least a year [14]. A header pinned to 202501 already returns a 426 with the code NONEXISTENT_VERSION [15]. Leaving the header out does not select the latest version. LinkedIn documents a 400 with the code VERSION_MISSING [16]. Connections also expire once a year, according to the write-up, but the excerpt does not describe the renewal flow [18].
The figures are the author's reading of LinkedIn's Increasing Access and Share on LinkedIn pages on October 6, 2026 [21].
What to watch
- Whether LinkedIn updates the Share on LinkedIn page to show /rest/posts in place of /v2/ugcPosts.
- October 15, 2026, when version 202510 is sunset and any header pinned to it falls out of support.
- What daily call limit the Standard tier grants, since a team sizing a multi-customer product needs that number.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence66
- Adoption
- Insufficient
- Hype gap
- Insufficient
- Incentives
- Insufficient
- Confidence58
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
LinkedIn charges nothing per API call.
- [2]
Share on LinkedIn gives any app the w_member_social permission without a review, which is enough to publish to the profile of whoever authorizes it.
- [3]
Posting to a company page requires the Community Management API, which LinkedIn grants only to registered companies after a review and which starts with a cap of 500 calls a day for the whole app.
- [4]
LinkedIn's review page says "our Community Management APIs are only available to registered legal organizations for commercial use cases only".
- [5]
Personal email addresses will not pass LinkedIn's vetting, so a side project has no way to post to a company page.
- [6]
LinkedIn's developer documentation describes access tiers and reviews, with no price list and no paid plan that buys more.
- [7]
For the Development tier, LinkedIn checks five things: an approved use case, a verified business email, a verified organization, a verified website and domain, and that the LinkedIn Page of the same organization has verified the app, which takes one of the Page's super admins.
- [8]
A rejection is final for that app; the developer cannot re-apply for Development tier access with the existing app and must create a new app and start over.
- [9]
The Development tier has a deadline: developers have twelve months to apply for Standard, and after that LinkedIn removes access for inactivity.
- [10]
The 500 calls a day are for the whole app, shared by all of the app's customers.
- [11]
In the author's SDK, a post with one image takes four requests: start the upload, send the bytes, read the image back and create the post. Statistics and comments requests come on top.
- [12]
On the Development tier, batch reads (BATCH_GET) are blocked and webhooks for social actions stay off until Standard.
- [13]
The Standard tier asks for test credentials, a high-resolution screencast showing a user going through the full OAuth flow and each declared use case, a valid privacy policy, and compliance with LinkedIn's data storage rules.
- [14]
LinkedIn publishes an API version every month, in YYYYMM format, and supports each one for at least a year.
- [15]
A Linkedin-Version header pinned to 202501 already gets a 426 response with the code NONEXISTENT_VERSION, as does any retired version.
- [16]
Leaving the Linkedin-Version header out does not get the latest version; LinkedIn documents a 400 with the code VERSION_MISSING.
- [17]
The oldest version still in LinkedIn's documentation, 202510, is sunset on October 15, 2026.
- [18]
Upkeep is a cost: the API version a developer sends expires, and so does every connection, once a year.
- [19]
Share on LinkedIn's documentation still shows the old /v2/ugcPosts endpoint, while the current Posts API at /rest/posts, in LinkedIn's own words, "replaces the ugcPosts API".
- [20]
The author advises keeping the API version in a single constant, noting its expiry date in a shared calendar, and running at least one test against the real API, because a test with mocked responses keeps passing after the version is retired.
- [21]
The figures come from LinkedIn's Increasing Access and Share on LinkedIn pages, read on October 6, 2026.
- [22]
At four requests per one-image post, a 500-call daily cap allows at most 125 such posts a day across all customers, before any statistics or comments requests.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- dev.toIs the LinkedIn API free? Pricing and posting access in 2026
1 article · October 13, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- API access and rate limitsFollow
- API VersioningFollow
- Social media APIsFollow