Platforms

PostFuze publishes to eleven networks through a single POST /api/v1/posts call. You write the post content once, list the accounts you want it to land on, and attach an optional per-platform config map for the network-specific options (a Pinterest board_id, a YouTube privacyStatus, an Instagram story flag, and so on). Each account becomes an independent target with its own status, so one post can succeed on X while it is still uploading to YouTube.

Supported networks

The platform value is the canonical identifier used everywhere in the API — in POST /social-networks, in the config map keys, and in each target's platform field. Note that Google Business uses the underscore form google_business.

The per-platform config map

When a post fans out to accounts on different networks, the top-level config object is keyed by platformid. Each account's target picks up config[platform] as its own settings. Keys for platforms not in the post are simply ignored.

{
	"content": "Launch day is here 🚀",
	"accounts": ["acct_x_01", "acct_pin_01", "acct_yt_01"],
	"config": {
		"pinterest": { "board_id": "9876543210", "title": "Launch day", "link": "https://example.com" },
		"youtube":   { "isShort": true, "privacyStatus": "public", "categoryId": "22" }
	}
}

The X account in this example receives no config (it has no configurable fields), the Pinterest target reads config.pinterest, and the YouTube target reads config.youtube. See each platform page for its exact field table.

Media constraints at a glance

Connecting an account

Before you can publish, bring your own OAuth app credentials with POST /social-networks, then start the hosted connect flow. Bluesky is the exception — it authenticates with a handle and an app password rather than OAuth. Each platform page below lists the OAuth scopes PostFuze requests.