Schedule post
Pass queue_id (instead of scheduled_time) to drop the post into a posting queue’s next open slot. Supports evergreen recycling via the optional recycle object: each published occurrence automatically schedules the next one until the chain hits its bound.
Facebook allows 30 API-published Reels per Page in a moving 24-hour window. A post whose platform_options.facebook.type is reel is refused when a selected Page would be at that limit at the post’s publish time (Reels published plus Reels already scheduled in the 24 hours before it): 422 PLATFORM_DAILY_LIMIT_REACHED, with details carrying account_id, limit, used and next_available_at. Nothing is created. If a scheduled Reel still hits the limit when it publishes, that account’s result fails with PLATFORM_DAILY_LIMIT_REACHED and is not retried automatically.
Requires scope social:write.
Headers
Client idempotency key (X-Request-Id accepted as an alias). Send a fresh key per logical post and REUSE it when retrying that exact call after a timeout / 5xx / connection reset: the retry returns the original post with HTTP 200 and idempotent_replay: true instead of creating a duplicate. A key permanently identifies its post in the workspace (deleting the post frees the key). See the Idempotency guide.
64^[A-Za-z0-9._:-]{1,64}$Body
Schedule request. Provide scheduled_time (with optional timezone) OR queue_id (next open slot), not both.
Target platforms. Use twitter for X and gmb for Google Business. telegram posts via the workspace's connected bot (created with @BotFather); discord posts via the connected server webhook. Both are connected in the dashboard's Social Accounts page.
facebook, instagram, twitter, linkedin, youtube, tiktok, gmb, threads, bluesky, tumblr, telegram, discord IDs of account groups (GET /social/account-groups). Their connected accounts are added to account_ids, each account once. Send account_ids, account_group_ids or both. An unknown group id answers 404 RESOURCE_NOT_FOUND naming it; a group with no connected accounts left answers 422 VALIDATION_ERROR naming it.
IANA timezone scheduled_time is expressed in when it carries no offset, e.g. Europe/Athens (default UTC). A scheduled_time ending in Z or an offset such as +03:00 is taken as given. Also applies to platform_options.{platform}.scheduled_time. Ignored with queue_id (the queue's own timezone applies).
Evergreen recycling: after this post publishes, the next occurrence is automatically scheduled interval_hours later, repeating until a bound is hit. A bound is REQUIRED - set max_repeats and/or until (no unbounded chains). Stop a chain anytime with DELETE /social/posts/{post_id}/recycle.
Per-platform composer options - the same payload the web composer stores; publish handlers read it as-is (unknown keys are ignored, max 20KB). Keyed by platform, e.g. {"tiktok": {"visibility": "private"}, "instagram": {"content": "IG-specific caption"}, "_thumbnail": {"timestamp_ms": 3000}}. Common keys: per-platform content override; tiktok visibility (REQUIRED for every TikTok post: public | friends | private - a TikTok post without it is refused with VALIDATION_ERROR; branded_content cannot be combined with private), type (video | photo), allow_comments/allow_duet/allow_stitch, disclose_content + your_brand/branded_content; _thumbnail custom video cover. Per-platform STAGGER: give any platform its own scheduled_time here (interpreted in the request timezone) and it publishes at that moment - platforms without one use the request-level scheduled_time. One call, one post per distinct time (response carries staggered[] with the created legs). Not combinable with queue_id or recycle.

