PATCH /api/v1/contents/{contentId}/schedule
Content (Beta)
Schedule (Contents)
PATCH
PATCH /api/v1/contents/{contentId}/schedule
This endpoint sets or removes an editorial planned date. The historical field
name is
scheduled_publish_at, but the operation does not publish content.
- Send an ISO-8601 value to add or change the planned day.
- Send
nullto remove the planned day. - Wait for the successful response before announcing the change. The returned content object is the server-confirmed state.
- Draft and finalized content may both receive a planned date. Planning never locks a draft or changes its content status.
- A planned date may later become overdue. It never becomes Published without a separate authoritative publication event.
YYYY-MM-DD portion as authoritative. This keeps the planned day stable when a
browser timezone changes. The UI displays the active browser timezone so users
can interpret “today” and “overdue.”Response
Successful response.