What the LinkedIn Post Limit per Day Really Is, and Where It Comes From

Is there a LinkedIn post limit per day?

There is no published LinkedIn post limit per day for posts from a member profile or a LinkedIn Page, and LinkedIn's Professional Community Policies ban spam without setting any number. The daily limits LinkedIn does document belong to its API, and they count API requests rather than posts. If you post by hand in the LinkedIn app, the rule that applies is the spam policy; if you post through a tool, the API's daily request limits apply as well.

The documented pieces fit in one table:

What is limited	Documented value	LinkedIn source
Posts from the LinkedIn app	No number published	Professional Community Policies
Share on LinkedIn requests, per member	150 requests per day	Share on LinkedIn, Rate Limits
Share on LinkedIn requests, per application	100,000 requests per day	Share on LinkedIn, Rate Limits
Other API endpoints	"Standard rate limits are not published in documentation"	API Rate Limiting
Reset time	Midnight UTC	API Rate Limiting
Over the limit	HTTP 429	API Rate Limiting, Posts API

Numbers such as "one post a day" or a fixed count before LinkedIn restricts an account come from marketing advice, not from LinkedIn. We found no LinkedIn page that states them.

What does LinkedIn's spam policy say about frequent posting?

LinkedIn's spam policy says "Do not spam members or the platform," and defines spam by the kind of content, not by how many posts you make. The full rule in the Professional Community Policies reads: "We don't allow untargeted, irrelevant, obviously unwanted, unauthorized, inappropriate commercial or promotional, or gratuitously repetitive messages or similar content."

Frequency counts against you only through the words "gratuitously repetitive". Five different, relevant posts in a day break no written rule. The same promotional post pushed out five times does. When you plan a heavy posting day, vary the content, not only the time slots.

How do LinkedIn API rate limits work?

LinkedIn API rate limits cap the number of API calls in a 24-hour period, reset at midnight UTC every day, and apply at two levels: the application and the member. LinkedIn's "API Rate Limiting" page defines them as:

• Application: "The total number of calls that your application can make in a day."
• Member: "The total number of calls that a single member per application can make in a day."

The member limit is per member per app. A LinkedIn member connected to two different tools has a separate member allowance in each of them, and each tool also has its own application-wide pool shared by all its users.

LinkedIn states that "Your application's daily rate limit varies based on which API endpoint you are using. Standard rate limits are not published in documentation." The way to see them is the Developer Portal: select the app, open its Analytics tab, and read usage and limits per endpoint. The tab lists only endpoints the app has called at least once that UTC day, so LinkedIn's instruction for an unlisted endpoint is to "make 1 test call to that endpoint and refresh the Analytics page."

LinkedIn emails developer admins when an application passes 75% of its quota. Those alerts cover only application-level limits, "not on member-level or combined member+app-level breaches," and arrive with a delay of 1 to 2 hours.

What is the Share on LinkedIn daily limit?

The Share on LinkedIn daily limit is 150 requests per member and 100,000 requests per application, measured per UTC day, according to the Rate Limits table on LinkedIn's Share on LinkedIn page. Share on LinkedIn is the self-serve product that grants the w_member_social permission, which LinkedIn describes as "Required to create a LinkedIn post on behalf of the authenticated member."

The 150 counts requests, and a post is not always one request. The same page describes an image or video share as three steps:

1. Register the upload with POST /v2/assets?action=registerUpload.
2. Upload the file to the uploadUrl LinkedIn returns.
3. Create the share with POST /v2/ugcPosts, pointing at the uploaded asset.

LinkedIn's table does not say which of these calls count toward the 150. A text-only share is one call. If every step counts, an image share costs three, and 150 requests covers 50 image posts for one member in a day. Either way, the ceiling sits far above any posting schedule a person would run. Image uploads on the newer Images API follow a similar register-then-upload flow, described in the LinkedIn initializeUpload image URN guide.

The Share on LinkedIn budget, split three ways

Text-only postsup to 150 a day

Image posts, if every step countsup to 50 a day

Application-wide pool100,000 requests a day

Do LinkedIn Pages have a separate posting limit?

LinkedIn Pages have no published posting limit, and the Posts API documents no Page-specific daily cap. Posting as a Page uses the w_organization_social permission, which LinkedIn restricts to members with one of three Page roles: ADMINISTRATOR, DIRECT_SPONSORED_CONTENT_POSTER or CONTENT_ADMIN. The limit on those calls is one of the unpublished endpoint limits that appear in the Developer Portal's Analytics tab.

When a Posts API call goes over a limit, LinkedIn returns:

Status	Code	LinkedIn's description
429	TOO_MANY_REQUESTS	"The API rate limit has been exceeded. Reduce request frequency and retry after a delay."

LinkedIn also warns that "In rare cases, LinkedIn may also return a 429 response as part of infrastructure protection. API service will return to normal automatically." A 429 is not always a quota problem; a retry after a pause can succeed the same day.

What happens when you hit a LinkedIn API limit?

When you hit a LinkedIn API limit, LinkedIn answers each further request with HTTP 429 until the counter resets at midnight UTC. The rejected request creates no post, so retrying is your tool's job.

The UTC reset has a practical effect for teams far from UTC. In New York, midnight UTC falls at 8 p.m. in summer. A member who exhausts an allowance in the morning gets it back that evening, not the next morning. Plan retries by UTC, not local midnight.

Rate limits apply to reading as well as writing. Analytics syncs, comment fetches and post lookups each count against the daily limit of the endpoint they call, and LinkedIn sets those limits per endpoint, so a tool that polls heavily can hit read limits on a day it publishes little.

How does AdaptlyPost schedule LinkedIn posts within these limits?

AdaptlyPost connects a LinkedIn profile or company Page through OAuth and schedules text posts, images, videos and document carousels from its LinkedIn post scheduler. You write the post, attach media or a document, and pick the publish time. Its LinkedIn analytics sync the last 180 days of published posts first, then refresh once a day inside LinkedIn's rate limits.

For larger batches, AdaptlyPost's bulk scheduling lets you set posts per day from 1 to 24 and spaces them across the day. A LinkedIn plan that respects both the spam policy and the API:

1. Keep each post distinct in wording and purpose, so nothing reads as "gratuitously repetitive."
2. Space posts across the day rather than publishing them in a burst.
3. Size images before upload; the LinkedIn post sizes guide lists the dimensions.
4. Add alt text within the LinkedIn alt text character limit.
5. If a post fails with a 429, retry after a pause, and plan any remaining retries after midnight UTC.

For the manual and scheduled posting flows side by side, see how to schedule LinkedIn posts.

Frequently asked questions

How many times can you post on LinkedIn per day?

LinkedIn publishes no daily limit on posts for members or Pages. Its Professional Community Policies ban spam and "gratuitously repetitive" content but give no number. Posting through the API is limited by daily request counts, such as 150 requests per member per day on Share on LinkedIn.

Does LinkedIn penalize posting more than once a day?

LinkedIn's written policies set no penalty for posting more than once a day. The spam rule targets untargeted, irrelevant, unwanted or repetitive content. LinkedIn publishes no rule that links posting frequency to reach.

What is the LinkedIn API rate limit?

LinkedIn does not publish standard rate limits for most endpoints; each app sees its own limits in the Developer Portal's Analytics tab. The Share on LinkedIn product is the exception, with 150 requests per member and 100,000 per application per day. All limits reset at midnight UTC.

When does the LinkedIn API limit reset?

LinkedIn API limits reset at midnight UTC every day. The counter covers a 24-hour period that starts and ends at that time. Plan retries by UTC, not your local midnight.

What does a 429 error mean on LinkedIn?

A 429 means the request went over a LinkedIn API rate limit. The Posts API describes it as TOO_MANY_REQUESTS and advises you to "retry after a delay." LinkedIn also returns 429 in rare cases for infrastructure protection, which clears on its own.

Is the LinkedIn Page posting limit different from a profile's?

LinkedIn publishes no posting limit for either. Page posts go through the w_organization_social permission and profile posts through w_member_social, and each endpoint has its own API request limit. For Pages, those limits appear only in the app's Developer Portal Analytics tab.

How many LinkedIn posts can AdaptlyPost's bulk scheduler queue in a day?

AdaptlyPost's bulk scheduling lets you set posts per day from 1 to 24 and spaces them across the day. For scale, 24 image posts at three requests each is 72 requests, under the 150 requests per member per day that LinkedIn documents for Share on LinkedIn. Page posts and other endpoints have limits LinkedIn does not publish.

Does LinkedIn warn you before an app runs out of API requests?

LinkedIn emails developer admins once an application passes 75% of its daily quota. Those alerts cover only application-level limits, not member-level or combined member-and-app breaches, and they arrive with a delay of 1 to 2 hours.

Do LinkedIn analytics syncs count against the API rate limit?

Rate limits apply to reading as well as writing, so analytics syncs, comment fetches and post lookups count against the daily limits of the endpoints they call. LinkedIn sets those limits per endpoint and shows them in the app's Developer Portal Analytics tab. AdaptlyPost syncs the last 180 days of published posts first, then refreshes once a day, inside LinkedIn's rate limits.

Do LinkedIn image or video posts use more of the API limit than text posts?

A text-only share counts as one API request, but an image or video share follows three steps: register the upload, upload the file, then create the share by calling ugcPosts. LinkedIn's rate limit table doesn't say which of these calls count toward the 150-request limit, so an image post could cost up to three requests, which would cap image posting at about 50 a day for one member.