LinkedIn Scheduling API
The LinkedIn Scheduling API lets a developer, agency workflow, automation, or AI system queue a LinkedIn post for an exact future time without maintaining its own publishing queue.
curl -X POST "{{API_BASE_URL}}/v1/posts" \
-H "Content-Type: application/json" \
-d '{
"content": "A short example update.",
"platforms": [
{
"platform": "linkedin",
"accountId": "li_456"
}
],
"scheduledFor": "2026-09-10T09:00:00",
"timezone": "Asia/Singapore"
}'curl -X POST "{{API_BASE_URL}}/v1/posts" \
-H "Content-Type: application/json" \
-d '{
You create the queued post once, choose the connected profile or Company Page, set the local time and timezone, and then manage the queued item before it publishes.
Schedule LinkedIn posts without maintaining your own publishing queue
A LinkedIn Scheduling API is useful when publishing time matters more than the moment a user clicks publish. Instead of running a cron job, a retry queue, and a timezone converter in your own application, you send one creation request with the content, the target account, and a scheduledFor value. The service queues the post and returns a scheduled status with the resolved UTC time, so your application can store the postId and show the queued item in a content calendar.
The workflow has three practical steps. First, obtain an API key for the service. Second, connect the LinkedIn account once and keep its accountId for later requests. Third, create scheduled posts through the same endpoint used for other supported platforms, changing only the platform target and LinkedIn-specific settings. That separation matters: connection and authentication happen once, while each post carries its own content, media, time, timezone, and visibility choices.
When scheduledFor is present, you do not need publishNow. Treat scheduledFor as the switch that moves a request from immediate publishing into the queue. If you omit it, you are describing a different publishing path, so check the returned status before assuming a post was queued. A scheduled response should include a postId you can use to track the item, and the scheduledFor value in UTC so downstream systems do not have to guess which offset was applied.
Input contract for POST /v1/posts
Create a queued LinkedIn post with POST /v1/posts. The request example in the Create a scheduled LinkedIn post with POST /v1/posts code example shows the core shape: top-level content, a platforms array containing the LinkedIn target, scheduledFor as an ISO 8601 datetime, and timezone as an IANA timezone name. The platforms entry uses platform set to linkedin and accountId set to the connected account you want to publish from.
Read the 202 response in the 202 response for a scheduled LinkedIn post code example as the confirmation contract. It returns success as true, status as scheduled, a postId, scheduledFor resolved to UTC, and a per-platform result showing linkedin with success as true. Store the postId and the UTC scheduledFor value, because those are the values your calendar, audit log, and support workflow can rely on after the request finishes.
Choose the target by accountId, not by guessing from a display name. A personal profile and a Company Page are different connected accounts, so the accountId determines where the post will publish. If a user has both a profile and a Page connected, select the accountId that matches the intended audience and brand voice. That choice should be made before creation, because changing the destination after queueing is an edit operation, not a property of the original request.
Worked timezone example: Asia/Singapore to UTC
Timezone handling is where scheduling bugs usually hide. The worked example uses scheduledFor of 2026-09-10T09:00:00 with timezone of Asia/Singapore. The response resolves that local time to 2026-09-10T01:00:00.000Z, which is the UTC publishing time. Your interface should therefore collect a local wall-clock time plus an IANA timezone, then display the returned UTC value as the system-of-record publishing instant.
Use IANA names such as Asia/Singapore, America/New_York, or Europe/London rather than fixed offsets, because named zones carry daylight-saving rules. If no timezone is provided, UTC is used, so a bare scheduledFor value must be interpreted as UTC. That default is convenient for machine-generated schedules, but it is risky for human-entered local times. In a form, require an explicit timezone whenever the user is thinking in local business hours, and show the converted UTC time back to them before they confirm.
Formats and targets: text, image, video, and article
Scheduling itself covers three formats: plain text, image, and video. Article and link-sharing possibilities, along with other LinkedIn-specific options, live in the wider publishing layer. When planning a campaign, first decide which format you need, then attach whatever that format demands, and only then fix scheduledFor and timezone.
A single creation call can also carry matching material to LinkedIn alongside Twitter/X, Facebook, and other supported networks, letting each network keep its own copy and options. Keep LinkedIn-specific choices inside the LinkedIn target or its platform-specific settings rather than flattening them into shared fields. That keeps a LinkedIn visibility choice from leaking into another platform and makes per-platform failures easier to diagnose from the response.
Visibility control with platformSpecificData.visibility
Audience reach is set through platformSpecificData.visibility. Leaving it unset gives PUBLIC, meaning anyone can see the item. CONNECTIONS narrows the audience to connections, but only on accounts where that narrowing is offered. Because availability varies by account, choose the value deliberately for every queued post instead of relying on the fallback.
A practical check is to review visibility alongside accountId before queueing. A Company Page post and a personal profile post may need different visibility expectations, and a connections-only post should not be scheduled with the same audience assumptions as a public announcement. If the account does not support the chosen visibility option, treat that as a validation failure to surface to the user rather than silently publishing with a different audience.
Queue management: list, edit, reschedule, and cancel
Once a post is queued, manage it as a calendar item. Calling GET /v1/posts/scheduled returns the queue, with each entry showing its publish moment, timezone, media, and platform state. Paging is handled by limit and offset, and you can flip the ordering between ascending and descending. The List queued posts with GET /v1/posts/scheduled code example shows the origin-modular form of that request.
Any item still waiting can have its copy, media, platform settings, or publish moment changed, and it can be moved to another day or hour, or removed entirely before it goes live. Plan content across days or weeks by creating each post with its own scheduledFor time, which suits a thought-leadership series or a campaign launch without maintaining your own scheduler. After any edit or reschedule, re-read the queued item and confirm the new publishing time, timezone, media, and platform status before telling the user the change took effect.
Failure and operations checks
Brief LinkedIn outages at the due moment are covered by built-in retry logic inside the scheduler, so you do not have to run a second retry system for LinkedIn yourself. That does not remove the need for operational checks: after the due time, verify the post status instead of assuming delivery, and keep the postId available for support and audit trails.
Lead time matters at creation. Give the scheduler at least a few minutes before the requested publishing time, with at least five minutes recommended so the post can be validated and reliably added to the queue. Scheduling a post seconds before its due time invites validation and queueing races. For urgent content, publish immediately through the normal posting path if that is available, or move the scheduled time far enough out to clear the recommended lead time.
| Field | Location | Type as shown | Requiredness | Contract |
|---|---|---|---|---|
| content | Request body | string | Shown in example | Post text, for example "Our latest product update goes live tomorrow." |
| platforms | Request body | array | Shown in example | Platform targets for the post. |
| platforms[].platform | Request body | string | Shown in example | Use "linkedin" for a LinkedIn target. |
| platforms[].accountId | Request body | string | Shown in example | Connected account identifier, for example "li_456"; selects a personal profile or Company Page. |
| scheduledFor | Request body | string (ISO 8601 datetime) | Required for scheduling in this contract | Local scheduled datetime, for example "2026-09-10T09:00:00". When present, publishNow is not needed. |
| timezone | Request body | string (IANA timezone) | Optional | For example "Asia/Singapore". If omitted, UTC is used. |
| platformSpecificData.visibility | Request body (LinkedIn-specific settings) | string enum | Optional; PUBLIC is the default | PUBLIC for public visibility; CONNECTIONS limits visibility to connections where that option applies to the publishing account. |
| success | 202 response body | boolean | Returned | true in the captured example. |
| status | 202 response body | string | Returned | "scheduled" in the captured example. |
| postId | 202 response body | string | Returned | Queued post identifier, for example "post_xyz789". |
| scheduledFor | 202 response body | string (UTC datetime) | Returned | Resolved UTC publishing time, for example "2026-09-10T01:00:00.000Z". |
| platforms[].platform | 202 response body | string | Returned | "linkedin" in the captured example. |
| platforms[].success | 202 response body | boolean | Returned | true in the captured example. |
Preserved from captured source example; types are as shown in the example JSON.
| Scenario | Input | Resolved result | Operational check |
|---|---|---|---|
| Singapore local morning | scheduledFor "2026-09-10T09:00:00" with timezone "Asia/Singapore" | 202 response scheduledFor "2026-09-10T01:00:00.000Z" | Display the UTC value as the publishing instant and store postId for tracking. |
| No timezone provided | scheduledFor without timezone | UTC is used | Confirm the user intended UTC before queueing a human-entered local time. |
| Other IANA zones | scheduledFor with America/New_York or Europe/London | Resolved to the appropriate UTC publishing time | Use named IANA zones so daylight-saving rules are applied. |
Worked example preserved from captured source.
| Decision | Choose this when | Field or setting to set | Check before queueing |
|---|---|---|---|
| Personal profile | The post should publish from an individual LinkedIn profile. | accountId for the connected profile | Confirm the accountId belongs to the intended profile. |
| Company Pages | The post should publish from a LinkedIn Company Page. | accountId for the connected Company Page | Confirm the accountId belongs to the intended Page and that visibility applies to that account. |
| Text post | The announcement needs no media attachment. | content with scheduledFor and timezone | Confirm copy, scheduledFor, and timezone. |
| Image or video post | The post needs attached media. | content plus media fields for the format | Confirm media is attached and the queued item still shows it after creation. |
| Article post | The post shares an article or link through the underlying LinkedIn publishing integration. | LinkedIn-specific article/link fields | Confirm the article/link fields are set for the LinkedIn target. |
| Cross-platform schedule | Compatible content should go to LinkedIn and other supported platforms. | platforms array with per-platform content and settings | Confirm LinkedIn visibility and accountId are not flattened into shared fields. |
Decision criteria derived from captured source contract.
| Situation | Contract behavior | What to verify |
|---|---|---|
| LinkedIn temporarily unavailable at due time | Automatic retry handling for temporary platform failures is included in the scheduling infrastructure. | Check post status after the due time using the stored postId; do not assume delivery. |
| Scheduling too close to due time | At least five minutes of lead time is recommended for validation and reliable queueing. | Move scheduledFor far enough out or use an immediate publishing path for urgent content. |
| Content, media, or settings need changing | While still scheduled, the post can be edited. | Re-read the queued item and confirm content, media, platform settings, and publishing time. |
| Publishing time needs to move | The post can be rescheduled to a new date or time before it goes live. | Confirm the new scheduledFor and timezone after the reschedule. |
| Post should not publish | The post can be cancelled before publication. | Confirm the item no longer appears as queued. |
| Reviewing the calendar | GET /v1/posts/scheduled returns queued posts with publishing time, timezone, media, and platform status; supports limit, offset, and ascending or descending sorting. | Paginate with limit and offset and sort by publishing time for chronological views. |
Behavior preserved from captured source; runtime reliability not claimed as tested.
| Endpoint | Purpose | Parameters or fields | Status or response contract |
|---|---|---|---|
| POST /v1/posts | Create a scheduled LinkedIn post | content, platforms[].platform, platforms[].accountId, scheduledFor, timezone, platformSpecificData.visibility | 202 with success, status "scheduled", postId, UTC scheduledFor, and per-platform success |
| GET /v1/posts/scheduled | List queued posts | limit, offset, ascending or descending sorting | Returns queued posts with publishing time, timezone, media, and platform status |
Exact methods and paths preserved; origin is modular via {{API_BASE_URL}}.
Frequently asked questions
How do I schedule a LinkedIn post through the API?
Send a request to POST /v1/posts naming the connected LinkedIn account through accountId, supplying the copy, and giving scheduledFor in ISO 8601 form. An IANA timezone may accompany it. Because scheduledFor already places the item in the queue, publishNow is unnecessary in that case.
Can I schedule posts to both LinkedIn personal profiles and Company Pages?
Both kinds of destination are covered: an individual profile and a Company Page. Pick the accountId belonging to whichever destination should receive the queued item.
What types of LinkedIn content can I schedule?
For scheduling itself, the supported formats are text, image, and video. Article or link sharing, plus other LinkedIn-specific options, sit in the broader publishing layer rather than the scheduling surface described here.
Can I control LinkedIn post visibility when scheduling?
Set platformSpecificData.visibility on the LinkedIn target. PUBLIC is the fallback and opens the item to everyone; CONNECTIONS restricts it to connections, but only for accounts where that restriction is available.
Do I need my own LinkedIn developer app?
No separate app is required from you. Sign-in, token upkeep, and the publishing plumbing are handled by the hosted integration, so scheduling does not depend on your own LinkedIn developer app.
How does timezone-aware LinkedIn scheduling work?
Supply scheduledFor together with a named zone — Asia/Singapore, America/New_York, and Europe/London are typical examples — and the local moment is converted to its UTC equivalent. Leave timezone out and the value is read as UTC.
Can I edit and reschedule a LinkedIn post after scheduling it?
Yes, provided the item has not gone live yet. Copy, attached media, platform settings, and the publish moment can all be changed, including moving it to a different day or hour.
Can I list all upcoming LinkedIn scheduled posts?
Yes. Calling GET /v1/posts/scheduled brings back the queue, showing when each item will publish, its timezone, any media, and how each platform stands. Paging uses limit and offset, and ordering can run ascending or descending.
What happens if LinkedIn is temporarily unavailable when the post is due?
Brief outages are covered by built-in retry logic inside the scheduler, so you do not have to run a second retry system for LinkedIn yourself.
How far in advance should I schedule a LinkedIn post?
Allow several minutes between creation and the intended publish moment. Five minutes is the recommended minimum, giving validation and queueing room to complete.
{
"success": true,
"status": "scheduled",
"postId": "post_xyz789",
"scheduledFor": "2026-09-10T01:00:00.000Z",
"platforms": [
{
"platform": "linkedin",
"success": true
}
]
}curl -X GET "{{API_BASE_URL}}/v1/posts/scheduled?limit=20&offset=0" \
-H "Content-Type: application/json"