Skip to content
← All articles
LinkedIn post scheduler: run a client calendar

LinkedIn post scheduler: run a client calendar

The calendar that breaks is rarely a copy problem. It is an authority or approval problem that shows up on the morning a client expects the post, when the copy is signed and the queue has nowhere to send it. LinkedIn settles part of that before you open a composer, and the rest is settled by the app that publishes, the member who authorizes it, and whether approval is a step your system enforces or a message in an inbox.

For the person running one client calendar or twenty, not the person writing the integration.

In short

  • LinkedIn’s own scheduler stops at 3 months, and Page scheduling refuses several formats outright.
  • A Page post needs a vetted Community Management app, the right scope, and a member holding an accepted Page role. No calendar tool can grant those.
  • Approval has to be a state the queue enforces. A reminder in a thread cannot stop a post at 9 a.m.

LinkedIn’s own scheduler covers less than people assume

The composer schedules a profile post from 10 minutes to 3 months ahead and a Page post from 1 hour to 3 months ahead, converting the device time zone to UTC. Page scheduling inside the LinkedIn interface refuses events, multiple photos, reshares, polls, job posts and service posts, so the built-in queue is a short shelf for a narrow set of objects. Three months is the outer edge, and every date past it lives in your own system.

The Posts API goes further: it has no scheduling field at all. PUBLISHED is the only lifecycle state the schema accepts at creation, as of October 2026, so any calendar you hand a client is a promise the scheduler keeps rather than one LinkedIn keeps. That is why the LinkedIn scheduler is mostly a conversation about the queue.

Format rules settle the payload before the copy is written. A post tops out at 3,000 characters, and document posts run to 100 MB and 300 pages and accept PPT, PPTX, DOC, DOCX or PDF. The API does not scrape a URL for a preview, so the title, description and thumbnail have to be sent explicitly, and a mention has to be written in the @[Name](urn:li:person:123) form before the character count is final. Character limits on every network covers how the same caption behaves elsewhere.

A client Page needs an app approval before it needs a calendar

Publishing to a company Page through the API takes a Community Management app, the w_organization_social scope, and an authorizing member. LinkedIn vets the app and accepts registered legal organizations for commercial use, so verification is a gate that exists before any content is planned, and it is not something a scheduler can request on your behalf.

The operational consequence belongs in the kickoff call rather than the sprint review: which app publishes for this client, and what is its verification status in writing? Review lead time goes into the plan next to the launch date. Version headers, scope tables and call budgets sit in the developer rules for the LinkedIn API, worth reading once.

The member who authorizes decides what the calendar can do

A Page post publishes under a member whose Page role on that organization is ADMINISTRATOR, CONTENT_ADMIN or DIRECT_SPONSORED_CONTENT_POSTER. The role lives on the client’s Page and the calendar inherits whatever it is given. When that content admin changes jobs, or someone tidies up the Page roster, the connection degrades before any document gets updated, and the first sign is a Page that drops out of the picker or a post that worked last week and fails now.

That member is also the one who reauthorizes. Access tokens last 60 days by default, programmatic refresh tokens last a year and are limited to approved Marketing Developer Platform partners, so when the refresh token expires a person walks through consent again. Put their name in the client record next to the Page, and treat the pairing as a dependency with an owner rather than a setting someone configured once.

Approval is a state, and the calendar has to model it

An approval that lives in a message thread is a reminder. It cannot refuse a publish at the scheduled minute, and it keeps no record of who signed. In PostSider, approval is a state: a post in APPROVAL rejects status and date changes from the generic post endpoints, and only an admin-level approval action resolves it. Flows support multiple stages with preventSelfApproval and distinct-approver rules, so the person who wrote the copy is not the only signature on it.

Build the calendar so the approved date is the only date the worker will publish, and make the state visible to whoever opens the board on Monday. Approval workflows that stop typos covers the sign-off side at length. Keep the review inside the tool as well, because the composer has a per-platform preview and a first-comment field, which is where a wrong Page mention or a link that will not unfurl gets caught before a client sees it in the feed.

The failures that arrive quietly, and where to look

Publishing limits are counted in calls, not posts. The publishing side allows 150 posts per member per day and 100,000 per app per day. The Community Management Development tier allows 500 API calls per app per 24 hours and 100 per member, the Standard tier’s limits are not published, limits reset at midnight UTC, and a breach returns 429.

Three failures deserve a shortcut on your desktop. A 401 mid-month is usually an expired token or a refresh token that needs a member to click through consent. A 403 on a Page that worked before is a role that was downgraded. A 429 in the afternoon is a call budget spent earlier than the plan assumed, and the fix is to move the remaining posts rather than retry in a loop. There is also a limit on what a report may hold: member social activity data may be stored for 48 hours and most member profile data for 24 hours, so a client asking for a quarter of member-level history is asking for something the data is not licensed to power. Start at the client record and work outward from there.

A weekly cadence for one client LinkedIn calendar

One client, one week, five passes. The order matters more than the effort.

  • Monday, open the record. Confirm the Page role, the token expiry date and who reauthorizes. Nothing gets queued until this block reads correctly.
  • Tuesday, close the copy. Copy and assets in by noon. Check the 3,000 character count after mentions are inserted, and confirm the preview title, description and thumbnail are sent rather than scraped.
  • Wednesday, route for approval. Move finished posts into APPROVAL, name the approver, and add a second stage with self-approval blocked where the client asks for two signatures.
  • Thursday, place the dates. Approved posts go into the calendar. Keep same-day items inside the 10 minute floor for a profile and the 1 hour floor for a Page, since those are LinkedIn’s rules for its own scheduler and your queue should not promise anything tighter.
  • Friday, read back. Compare what the queue marks published against what the Page actually shows, and log deferrals and 429s so next week is planned against a real number instead of an optimistic one.

The pre-flight list before the first scheduled post

Seven checks, run once per client, before anything is queued.

  1. The app is Community Management, verified, with w_organization_social confirmed in writing.
  2. The authorizing member holds an accepted Page role, and their name and role are in the client record.
  3. A reauthorization owner is named, with a reminder on day 60 and a second one before the refresh token’s year runs out.
  4. A daily call budget per Page is written down, with room for retries and status reads.
  5. Character counts are settled after mentions, and the preview fields are sent explicitly.
  6. Approval stages are configured, with preventSelfApproval on wherever two signatures are required.
  7. A named person owns the failure that arrives at 9 a.m., and the recovery path does not depend on a developer being awake.

Cost is a channel question rather than a seat question, which matters more to an agency than the per-month number. Standard is $20 a month for 5 channels, Team $35 for 10, Pro $45 for 30 and Ultimate $90 for 100, with unlimited team members from Team upward and a seven-day trial without a card. Plans and channel counts lists them next to what each one includes.

PostSider is what I build, and it publishes to LinkedIn profiles and company Pages from the same queue as a client’s other networks; the hosted MCP server exposes 30+ tools and the REST API sits at /public/v1, so a calendar can be filled by a script as easily as by hand. A month of posts survives on the unglamorous answers: who holds the role, which app is verified, and whose signature moves a post out of approval.

Frequently asked questions

Can I schedule a LinkedIn profile post through the API?

No. The Posts API has no scheduling field, and PUBLISHED is the only lifecycle state the schema accepts at creation. A scheduler stores the post in its own queue and calls LinkedIn at the chosen minute, so the scheduled date lives in the tool.

Why does a Page post fail when the copy is fine?

Because publishing to a company Page through the API needs a Community Management app, the w_organization_social scope, and an authorizing member whose Page role is ADMINISTRATOR, CONTENT_ADMIN or DIRECT_SPONSORED_CONTENT_POSTER. LinkedIn vets the app and accepts registered legal organizations for commercial use, so an unverified app fails before the text is ever read.

How far ahead can I schedule in LinkedIn's own composer?

A profile post goes from 10 minutes to 3 months ahead, and a Page post from 1 hour to 3 months ahead, with the device time zone converted to UTC. Page scheduling there also refuses events, multiple photos, reshares, polls, job posts and service posts.

What happens when the token expires in the middle of the month?

Access tokens last 60 days by default. Programmatic refresh tokens last a year and are limited to approved Marketing Developer Platform partners, so when the refresh token expires the member reauthorizes. Until they do, scheduled posts stop with a 401 that reads like a code bug.

Can a reviewer approve and publish without a developer in the loop?

Yes. Approval is a state in the queue rather than a message thread. A post in the APPROVAL state rejects status and date changes from the generic post endpoints, and only an admin-level approval action resolves it, so a reviewer can clear a staged sign-off and let the calendar publish on its own.

Let your AI post
to social media for you.

Connect your accounts, add PostSider to your AI and publish your first post in a few minutes.

7-day free trial · 30+ networks · No credit card · Cancel anytime