Create post
POST/:workspaceUuid/posts
Create a new post. Use schedule: true with date and time to schedule,
schedule_now: true to publish immediately, or queue: true to add to the
smart publishing queue (each account gets its own queue slot).
date, time and accounts_schedule are read in timezone when given,
otherwise in the workspace timezone. Use accounts_schedule to give individual
accounts their own departure time.
Post bodies may reference mentions with {{mention:<reference>}} (see the
Mentions endpoints). When the post is scheduled, provider requirements (for example
a network that requires media) are validated up front and reported as 422.
First comment and threads. A version's content is an ordered array. Item 0 is
the post. Add a second item to publish a first comment on Facebook Page, Instagram and
LinkedIn, or to continue a thread on X, Threads, Bluesky, Mastodon and Pixelfed:
{
"accounts": [12],
"schedule_now": true,
"versions": [{
"account_id": 0,
"is_original": true,
"content": [
{ "body": "Our API 1.8 is live.", "media": [345] },
{ "body": "Full changelog: https://postboost.co/docs/changelog/" }
]
}]
}
The comment is posted right after the post goes live. If the comment fails, the post
stays published and the account's entry on the post reports the error. LinkedIn posts
the comment only when first comments are enabled for LinkedIn on this server; otherwise
only item 0 is published and the response carries a linkedin_first_comment_unavailable
warning.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 422
- 429
Created post. warnings lists non-blocking problems (see PostWarning); the key is absent when there are none.
Response Headers
Present and true when the response is a replay of an earlier request with the same Idempotency-Key.
The Idempotency-Key header is not 1 to 255 printable ASCII characters.
Missing or invalid API token.
Access denied. Returned when the caller is not a member of the workspace, lacks the role
the endpoint needs, or the workspace's plan does not include API access (capability api).
Either the content duplicates a post created for the same account within the duplicate window
(code: duplicate_post, existing_post_uuid names it; resend with allow_duplicate: true to post anyway),
or a request with the same Idempotency-Key is still in progress (no code, Retry-After: 1).
Validation failed (errors lists the fields), the Idempotency-Key was already used with a different
body, or the post is scheduled to an account that cannot publish (code: account_unauthorized or
account_token_missing, reconnect the account).
Scheduling would exceed an account's daily post cap for that UTC day (code: account_daily_cap_reached), or the workspace's monthly X allowance (code: x_monthly_cap_reached).