Schedule a post
POST/:workspace/posts/schedule/:post
Schedules an existing post.
postNow: false— schedules the post at the date and time already stored on it.postNow: true— schedules the post at the current time (UTC) and, unless it lands inneeds_approval, publishes it immediately.
The resulting status is scheduled if the authenticated user is allowed to approve posts in this workspace,
and needs_approval otherwise. Requires permission to schedule posts in the workspace.
Returns 422 when the post is already in history (published or failed), is currently being published,
or cannot be scheduled — that is, it has no stored date and time, its date and time is in the past, or it
has no accounts attached. With postNow: true the past-date check never fails, since the post is scheduled
at the current time.
It also returns 422 when the post's content does not meet the publishing requirements of its accounts' platforms.
Request
Responses
- 200
- 401
- 403
- 404
- 422
Schedule result.
The bearer token is missing, malformed, unknown, or expired.
The token is valid, but the user it belongs to may not perform this action:
- they are not a member of the
{workspace}in the path; or - their workspace role is too low for this endpoint (write routes require Admin or Member); or
- for
/panelendpoints, they are not a platform administrator.
The host application that Mixpost is installed into can also deny access to Mixpost as a whole, which produces the same response.
Workspace or post not found.
The request body failed validation.