Facebook Scheduling API
The Facebook Scheduling API queues Facebook Page posts for a later delivery moment, so your own system does not need to hold and release them itself.
POST {{API_BASE_URL}}/v1/posts
x-access-key: YOUR_API_KEY
Content-Type: application/json
{
"content": "A short example update.",
"platforms": [
{
"platform": "facebook",
"accountId": "fb_456"
}
],
"scheduledFor": "2026-09-10T09:00:00",
"timezone": "Europe/London"
}POST {{API_BASE_URL}}/v1/posts
x-access-key: YOUR_API_KEY
Content-Type: application/json
Each request carries scheduledFor as an ISO 8601 datetime, with an optional IANA timezone deciding how that datetime is read; the reply then states the equivalent UTC publishing time. Text, a single image, a photo carousel, a video, and a link-preview post all use that same queued structure, and anything still waiting can be listed, edited, moved to a different time, or cancelled before it goes live.
What this API does: schedule Facebook Page posts without maintaining your own publishing queue
At its core, this API answers one question for a Facebook Page post: should it go out now, or later? Leaving the scheduling fields out means immediate publication. Adding scheduledFor, and timezone when the intended reading is local time, turns the same request into a future delivery. That keeps the payload familiar while making timing a first-class part of the call and of the reply. If you are lining up content across days or weeks, give every post its own scheduledFor value and submit them one by one; there is no bulk scheduling operation described here. One call may also address more than one network, such as Facebook together with Instagram or LinkedIn, with network-specific wording or settings supplied where a format needs them.
Input contract and field map for POST /v1/posts
To queue a post, call POST /v1/posts. Point the request at a destination by listing it under platforms, with each entry holding a platform value and the accountId of a connected Facebook Page, and put the post wording in content. Timing comes from scheduledFor, an ISO 8601 datetime, plus timezone, an IANA timezone such as Europe/London. The sample in the code examples sends 2026-09-10T09:00:00 in Europe/London and receives 2026-09-10T08:00:00.000Z back as the UTC publishing time, illustrating the one-hour difference for that date. Treat that sample as an illustration of the contract, not as a record of a live call. Before sending, confirm accountId belongs to a connected Facebook Page, scheduledFor lies in the future, and timezone is a valid IANA name if you provide one.
Timezone handling: IANA timezone, UTC return, omitted timezone treated as UTC
Getting the timezone decision right matters most, because it is where a post most easily lands at the wrong hour. If timezone is included, scheduledFor is understood as local time in that IANA timezone, and the response supplies the same moment expressed in UTC. If timezone is left out, scheduledFor is understood as UTC, so a value of 09:00 is delivered at 09:00 UTC and not at 09:00 where your audience lives. A useful sanity check is to line up the local time you meant against the UTC time returned: when the gap does not match the daylight-saving offset expected for that date, pause and fix the timezone or datetime before queueing more posts. Keep both the local scheduledFor you sent and the UTC publishing time you received in your own records, so later changes and reports share one reference point.
Supported formats: text, single image, photo carousel, video, link preview
Five formats can be queued: text posts, a single image, a photo carousel, a video, and a link-preview post. All of them travel through the same scheduled post structure, with scheduledFor doing the scheduling work in every case. That consistency simplifies validation, because destination, wording and timing can be checked once while only the media or link fields change from format to format. Where a format calls for extra fields, for example media references for an image, carousel or video, the captured material did not spell those fields out, so check them against the implementation contract before depending on them. If a request fails over a format-specific field, leave scheduledFor and timezone alone; they govern when delivery happens, not whether the media is valid.
Worked example with source request and response
The code examples show the complete exchange. The request carries content, a platforms entry with platform facebook and accountId fb_456, scheduledFor 2026-09-10T09:00:00, and timezone Europe/London. The reply carries success true, status scheduled, postId post_xyz789, the UTC publishing time 2026-09-10T08:00:00.000Z, and a per-platform success entry for facebook. Keep the postId safe straight away, since the management endpoints use it to edit, reschedule and cancel the queued item. Also check that the UTC time returned matches what you expect for that timezone and date; a mismatch usually points to a missing timezone or a datetime that was already in UTC.
Managing queued posts: GET, PUT, PATCH, DELETE /v1/posts/scheduled endpoints
Once queued, posts are handled through the scheduled-post endpoints. GET /v1/posts/scheduled returns upcoming items with their content, publishing time, timezone, media and platform status. Results can be paged using limit and offset, and ordered by scheduled time in either direction. Choose PUT /v1/posts/scheduled/{postId} for wording or media changes, PATCH /v1/posts/scheduled/{postId} when only the delivery moment needs to move, and DELETE /v1/posts/scheduled/{postId} to drop a queued item before it publishes. A sound routine is to list first, confirm the postId and the current UTC publishing time, then make the smallest change that fixes the problem. Afterward, list again and confirm the new time, or the absence of the item, before trusting the calendar.
Failure and limits matrix: Pages only, temporary unavailability, cancel before publication
Check a few boundaries before putting this into a production workflow. Destinations are Facebook Pages only; a personal profile cannot receive scheduled delivery through this API. Editing, rescheduling and cancelling apply while a post is still queued, so once delivery has happened the item is no longer a queued post. When Facebook is briefly unavailable at the moment a post is due, the specification describes retry handling for temporary platform failures, but no retry timing or limits were supplied, so verify those rather than treating them as guaranteed. Facebook posting, Facebook analytics and Facebook comments may sit beside scheduling in a wider workflow, yet none of them changes the scheduling contract itself. The failure and limits matrix below gathers these checks together as a pre-flight review.
Frequently asked questions
The answers below cover the checks implementers most often need for the Facebook Scheduling API: creating a scheduled Facebook Page post, the post types that can be queued, how timezone handling works, and how to list, edit, reschedule or cancel items that are still waiting. Each answer is written directly against its source question, so the page works as a quick reference while you integrate.
| Field | Location | Type / format | Requiredness | Notes |
|---|---|---|---|---|
| content | Request body | String | Required in example | Post text, e.g. "Our new opening hours start tomorrow." |
| platforms | Request body | Array of objects | Required in example | One entry per destination platform. |
| platforms[].platform | Request body | String enum | Required in example | Value "facebook" for Facebook Page scheduling. |
| platforms[].accountId | Request body | String | Required in example | Connected Facebook Page account identifier, e.g. "fb_456". |
| scheduledFor | Request body | ISO 8601 datetime string | Required for scheduling | Future publishing time; interpreted in timezone when supplied, otherwise as UTC. |
| timezone | Request body | IANA timezone string | Optional | Examples: Europe/London, America/New_York, Asia/Kolkata. Omitted means UTC interpretation. |
| success | 202 response body | Boolean | Returned | Example value true. |
| status | 202 response body | String enum | Returned | Example value "scheduled". |
| postId | 202 response body | String | Returned | Identifier used by scheduled-post management endpoints, e.g. "post_xyz789". |
| scheduledFor | 202 response body | UTC datetime string | Returned | Resolved UTC publishing time, e.g. "2026-09-10T08:00:00.000Z". |
| platforms[].success | 202 response body | Boolean | Returned | Per-platform scheduling result. |
Source-verified fields from captured example and FAQs; full schema not supplied.
| Method and path | Purpose | Key parameters | Notes |
|---|---|---|---|
| GET /v1/posts/scheduled | List queued posts | limit, offset; ascending/descending sort by scheduled time | Returns content, publishing time, timezone, media, and platform status. |
| PUT /v1/posts/scheduled/{postId} | Edit scheduled content or media | postId path parameter | Use for content or media changes before publication. |
| PATCH /v1/posts/scheduled/{postId} | Change only the publishing time | postId path parameter | Use to reschedule without editing other fields. |
| DELETE /v1/posts/scheduled/{postId} | Cancel a queued post | postId path parameter | Applies before publication. |
Methods, paths and parameter names from captured source FAQs; full request/response schemas not supplied.
| Condition | Expected behavior | Check before relying on it |
|---|---|---|
| Destination is a personal profile | Not supported; Facebook Pages only | Confirm accountId is a connected Facebook Page. |
| timezone omitted | scheduledFor treated as UTC | Compare intended local time with returned UTC publishing time. |
| Invalid or unexpected IANA timezone | Time may resolve to an unintended UTC publishing time | Validate timezone name and verify returned UTC offset for the date. |
| Facebook temporarily unavailable at delivery time | Source specification describes retry logic for temporary failures | Verify retry timing and limits during implementation; do not assume a guarantee. |
| Edit, reschedule, or cancel after publication | Management applies to queued posts before publication | List scheduled posts and confirm status before attempting a change. |
| Format-specific media or link fields missing | Request may be rejected for format reasons unrelated to scheduling | Confirm media/link fields against the implementation contract; full schema not supplied. |
Behaviors from captured source; retry timing and error codes not supplied.
Frequently asked questions
How do I schedule a Facebook Page post through the API?
Send a request to POST /v1/posts naming the connected Facebook Page through accountId, supplying the post text in content, and setting scheduledFor to a future ISO 8601 value. Include timezone with an IANA name when you want that value read as local time.
What types of Facebook posts can I schedule?
A Facebook Page can receive plain text, one image, several photos arranged as a carousel, a video, or a post built around a link preview. Adding scheduledFor to the normal publishing request is what turns any of those formats into a queued delivery.
Can I schedule Facebook posts to a personal profile?
No. This integration covers Facebook Pages only, so a personal profile cannot be used as the destination for scheduled delivery here.
How does timezone handling work?
Supply an IANA name such as America/New_York, Europe/London, or Asia/Kolkata and the API reads scheduledFor in that zone, then reports back the matching UTC publishing time. Leaving timezone out means the value is read as UTC.
Do I need my own Facebook developer app or Meta App Review?
That requirement depends on how the owned implementation handles Meta authorization, Page tokens, and any developer-app obligations. Those details were not verified in the captured material for this draft, so confirm the current OAuth and App Review approach during implementation rather than assuming either answer.
Can I edit, reschedule, or cancel a Facebook post after scheduling it?
Yes, while the item is still queued. Send content or media changes with PUT /v1/posts/scheduled/{postId}, send only a new delivery time with PATCH /v1/posts/scheduled/{postId}, or remove the queued item with DELETE /v1/posts/scheduled/{postId}.
Can I see all upcoming Facebook scheduled posts?
Yes. Call GET /v1/posts/scheduled to see queued items, including their text, delivery time, timezone, media, and per-platform status. Results can be paged using limit and offset, and ordered by scheduled time in either direction.
What happens if Facebook is temporarily unavailable when a post is due?
The specification describes retry handling for brief platform outages, so a due post may be attempted again rather than needing a separate retry queue in your application. Exact retry timing and limits were not supplied, so verify them during implementation.
Who is the Facebook Scheduling API for?
It suits developers, SaaS teams, agencies, automation builders, and AI products that need to schedule Facebook Page content programmatically.
{
"success": true,
"status": "scheduled",
"postId": "post_xyz789",
"scheduledFor": "2026-09-10T08:00:00.000Z",
"platforms": [
{
"platform": "facebook",
"success": true
}
]
}GET {{API_BASE_URL}}/v1/posts/scheduled?limit=20&offset=0
PUT {{API_BASE_URL}}/v1/posts/scheduled/{postId}
PATCH {{API_BASE_URL}}/v1/posts/scheduled/{postId}
DELETE {{API_BASE_URL}}/v1/posts/scheduled/{postId}