Update a post
PUT/:workspace/posts/:post
Replaces the post's accounts, tags and versions (the versions in the request are created or updated, and the rest are removed) and recomputes the scheduled date and time from date + time, read in timezone when given.
Caveats — differences from creating a post
schedule,schedule_nowandqueuehave no effect. They are accepted by validation for consistency with post creation, but this endpoint does not read them.- The status is never changed by this endpoint. Only the scheduled date and time is updated. Use
POST /posts/schedule/{post},POST /posts/add-to-queue/{post}orPOST /posts/approve/{post}to change a post's status. - If the post is not a draft and either
accountsis empty ordateandtimeare not both present, the post is moved back todraft.
Returns 422 when the post is already in history (published or failed) or is currently being published.
A scheduled post that stays scheduled — accounts is not empty and date and time are both present — is checked against the publishing requirements of its accounts' platforms, using the accounts and versions in the request. When a requirement is not met, the response is 422 and nothing is changed. A draft, and a post this request moves back to draft, are not checked.
Request
Responses
- 200
- 401
- 403
- 404
- 422
Update 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.
Workspace or post not found.
The request body failed validation.