Schedule post
POST/:workspaceUuid/posts/schedule/:postUuid
Schedule an existing post. Optionally move it with date/time (read in timezone) and give
accounts their own times with accounts_schedule. Set postNow: true to publish immediately;
publishing starts within the request and any per-account times are dropped.
Provider requirements are validated and reported as 422. The guardrails check the saved post at
the time it would publish, as on create: 409 duplicate (override with X-Allow-Duplicate: true),
422 account cannot publish, 429 daily or X cap.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
- 429
Schedule 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).