Add post to queue
POST/:workspaceUuid/posts/add-to-queue/:postUuid
Add an existing post to the smart publishing queue. Each account of the post gets its own
next free queue slot. Returns 422 when the post has no accounts, the posting schedule has no
available times, or provider requirements are not met. The guardrails check the saved post as
publishing at the queue slot it will get (the earliest next free slot of its accounts), as on
create: 409 duplicate (override with X-Allow-Duplicate: true), 422 account cannot publish,
429 daily cap on that slot's UTC day or X cap.
Request
Responses
- 201
- 401
- 403
- 404
- 409
- 422
- 429
Queue confirmation
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).
Resource not found.
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).