Skip to main content
Publish to one or more connected platforms with a single JSON body. Postsiva merges unified fields (shared defaults) with platform override objects (linkedin, facebook, etc.) when you need per-network copy or targeting.
For every field Postsiva accepts (per platform), see the complete Posting parameters reference. For UI + OAuth + API key setup, see Complete setup.

Base URL & auth

Connect accounts first via OAuth. Upload images and videos via Media and pass returned media_id values in post bodies.

Endpoints

Each path accepts the same cross-cutting fields; type-specific fields are validated per route.

Common body fields

These apply to all four post types unless noted.

Platform override objects

Nest platform-specific fields under the platform key. Overrides win over unified defaults for that network only.

LinkedIn targeting

Facebook pages

Facebook posts always target Pages (not personal profiles). You must supply page IDs:

POST /unified/post/text

Text-only posts. Supported platforms: linkedin, facebook, threads, bluesky.

POST /unified/post/image

Single-image posts. Provide default_image_id OR default_image_url (at least one required).
Threads and Bluesky accept default_image_url / video_url — Postsiva uploads the file first, then posts using the returned media_id. Carousel posts still require image_ids from Media.

POST /unified/post/carousel

Multi-image carousel. image_ids required: 2–20 UUIDs from media upload.

POST /unified/post/video

Video posts. Provide video_id OR video_url (at least one required).

Drafts and scheduling

Schedule-only workflows without immediate publish can also use POST /unified/scheduled-posts (same body shape, scheduled_time required, draft not allowed on that route).
When drafts are saved, you receive draft objects instead of live post IDs. Publish drafts from the Postsiva app or scheduled-posts APIs.

Response shapes

Single platform

Multiple platforms

Each platform runs in parallel. Partial success is possible.

Draft responses

Mixed draft + publish

MCP equivalent

Use the publish tool on Unified MCP with the same fields (post_type, platforms, default_text, media ids, draft, scheduled_time, platform_overrides_json).
Auth: X-API-Key: psk_live_… or ?apikey=psk_live_…