Skip to main content
platform_options is an object keyed by platform that rides along on POST /social/posts, /social/posts/schedule, and bulk rows - the same payload the SmartlyQ composer uses, so anything below works identically from the API. Unknown keys are ignored; you never break a post by sending extra fields.
Universal keys (every platform): content - overrides the global caption for that platform only. Scheduling stagger (schedule endpoint): any platform may carry its own scheduled_time - see the note on the schedule endpoint. One call, each network at its own moment.

Per-platform keys

Instagram

YouTube

TikTok

Reddit

Posting a link instead of a self post is automatic when the post carries media suited to it. Check a community first with GET /social/accounts/{account_id}/reddit/subreddits/{subreddit} (rules + can_post verdict).

Facebook

Stories

type: "story" publishes to the Page’s story tray via Meta’s Page Stories API.
  • Exactly one photo or one video. Not a carousel, not two images.
  • No caption. Neither story endpoint accepts a message, description or text overlay, so the post’s text is not published. Put any wording into the image or video itself. The create response carries a warnings entry saying so when a story post has text.
  • Video: MP4, 9:16, up to 60 seconds, 1080x1920 recommended (540x960 minimum), H.264/H.265, 24-60fps.
  • Photo: JPEG, PNG, BMP, GIF or TIFF, up to 10MB.
  • The media must not already have been published. Meta refuses a photo or video that has appeared in a previous post, and refuses media served from its own CDN (fbcdn.net) - host your own copy.
  • No permanent link. A story lives for 24 hours and has no /posts/{id} page, so post_url comes back null once it expires. The post_id is always returned.
  • Your Page token needs pages_manage_posts and pages_read_engagement.

LinkedIn

title (video/document posts), first_comments, _thumbnail.url. Document (PDF) posts publish via the document pipeline automatically.

X (Twitter)

content override and media_urls per platform. first_comments publish as a reply thread: the first replies to the post, each subsequent one replies to the previous (a chained thread). Each comment may be a plain string, or an object { "text": "...", "media_urls": ["https://..."] } to attach media to that reply - up to 4 images, or one video (X’s per-reply limits). Example:

Threads

reply_control - who can reply; first_comments.

Google Business

Pinterest

title, board_id, link (destination), alt_text; video cover via a second media item or _thumbnail.url.

Snapchat

surface (story / spotlight), save_to_profile, title (saved stories, ≤45 chars), description + locale (spotlight).

Telegram

Tumblr

tags (array).

Bluesky / Discord

content override only - links, mentions and previews are handled automatically.

First comments summary

first_comments (array, max 5) is supported on Facebook, Instagram, X, LinkedIn, Threads, and Reddit. Other platforms ignore it. On X they post as a chained reply thread and each entry may carry media ({ text, media_urls }); on Facebook an entry may carry a single image. Elsewhere they are text only.