Configurations

The optional config object on a post holds per-platform settings keyed by platform identifier. When a post fans out, each target receives only the config slice for its own platform — so config.youtube reaches a YouTube target, config.tiktok reaches a TikTok target, and a platform with no slice simply uses its defaults. This is how you set a YouTube title, choose a Pinterest board, lock a TikTok video to a private audience, or control LinkedIn visibility, all from a single request.

The platform keys are the canonical identifiers: x, linkedin, instagram, tiktok, facebook, threads, bluesky, youtube, pinterest, reddit, and the underscore form google_business. The stored object is echoed back as default_config on the post, and the per-platform slice is copied onto each target. Every field below is optional unless explicitly marked required; unknown fields are ignored.

X (Twitter)

Key config.x. The only publishing switch is the long-form toggle for X Premium accounts; otherwise the adapter reads an optional username used purely to render the permalink. Reply settings and polls are not supported.

A first comment or thread is expressed with extra containers, not config.

LinkedIn

Key config.linkedin. Controls post visibility, whether the post is authored by the member or one of their organization pages, and an optional article/document attachment.

Instagram

Key config.instagram. Instagram is a Business/Creator-only, URL-ingest platform. Carousels are inferred automatically from the number of media items in the main container (2–10 items), and reels share to the main feed by default — neither needs a config field. The one switch is publishing as a Story.

TikTok

Key config.tiktok. Sets the post's privacy and interaction permissions and the commercial-content disclosure flags. Field names are snake_case, matching TikTok's Content Posting API.

Facebook

Key config.facebook. Posts publish to the connected Page; the one field below is optional.

Threads

Key config.threads. Controls who can reply, an optional outbound link on text-only posts, and a topic tag.

Bluesky

Key config.bluesky. Bluesky has no per-post configuration fields — pass nothing. Links and @handlementions in the text are detected and rendered as rich text automatically. For a self-hosted account, the Personal Data Server (PDS) host is resolved automatically from the account’s handle when you connect it, so it never needs to be set on a post.

YouTube

Key config.youtube. The container's content becomes the video description; title sets the video title. For compatibility these fields are also accepted nested under config.youtube.youtubeConfiguration.

Pinterest

Key config.pinterest. A pin always lands on a board, so board_id is required. The container's content becomes the pin description; title falls back to it when omitted, and alt_textfalls back to the media's alt text.

Google Business

Key config.google_business(underscore form). Selects the post topic and, for events and offers, the structured event/offer detail. The container's content becomes the post summary (capped at 1,500 characters).

Reddit

Key config.reddit. A submission always targets a subreddit, so subredditis required. The post kind is auto-detected from the content/media when omitted; the container's content becomes a self-post body or supplies the link.

Example: one post, three platforms

A single post fanned out to YouTube, Pinterest and TikTok, each with its own config slice. Platforms not present in config (here, none) would simply use their defaults.

curl https://api.postfuze.com/api/v1/posts \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Behind the scenes of our launch week 🎬",
    "media": [{ "id": "media_launch_clip" }],
    "accounts": ["acct_yt_01", "acct_pin_01", "acct_tt_01"],
    "config": {
      "youtube": {
        "title": "Launch Week — Behind the Scenes",
        "isShort": true,
        "privacyStatus": "unlisted",
        "tags": ["launch", "behindthescenes"]
      },
      "pinterest": {
        "board_id": "987654321",
        "title": "Launch Week BTS",
        "link": "https://postfuze.com/blog/launch-week"
      },
      "tiktok": {
        "privacy_level": "PUBLIC_TO_EVERYONE",
        "disable_duet": true,
        "disable_stitch": true
      }
    }
  }'

{
  "id": "p7c8d9e0-0000-4a9f-9b1c-2e7d6f0a9876",
  "status": "queued",
  "is_draft": false,
  "default_config": {
    "youtube": { "title": "Launch Week — Behind the Scenes", "isShort": true, "privacyStatus": "unlisted", "tags": ["launch", "behindthescenes"] },
    "pinterest": { "board_id": "987654321", "title": "Launch Week BTS", "link": "https://postfuze.com/blog/launch-week" },
    "tiktok": { "privacy_level": "PUBLIC_TO_EVERYONE", "disable_duet": true, "disable_stitch": true }
  },
  "containers": [
    { "id": "c_0001", "position": 0, "role": "main", "content": "Behind the scenes of our launch week 🎬" }
  ],
  "targets": [
    { "id": "t_0001", "social_account_id": "acct_yt_01",  "platform": "youtube",   "status": "queued", "platform_post_id": null },
    { "id": "t_0002", "social_account_id": "acct_pin_01", "platform": "pinterest", "status": "queued", "platform_post_id": null },
    { "id": "t_0003", "social_account_id": "acct_tt_01",  "platform": "tiktok",    "status": "queued", "platform_post_id": null }
  ]
}

The stored config is returned as default_config, and each target receives only its platform's slice. See Posts for the full post lifecycle and the individual platform guides for per-platform media constraints and OAuth scopes.