COcontentstudio
🏢 Workspaces

Resume publishing for a workspace

Changed on

Releases the hold on the workspace and returns held posts to the state the product returns them to. time_type decides what happens to each held post: * * - resume (default, and the option the web app pre-selects) — a post whose scheduled slot is still in the future goes back to its original status. A post whose slot passed while publishing was paused stays a draft; it is not back-published. * - recurring — every held post goes back to its original status and is re-spread from now, one every recurring.value recurring.type. * - custom — the hold is released but every post stays a draft, for you to reschedule yourself. * * Automations are not unlocked. RSS and Evergreen automations locked by the pause stay locked, matching the product: a blanket unlock would also re-enable automations the customer had locked by hand, and some plans do not permit automations at all. Re-enable them individually.

post/api/v1/workspaces/{workspace_id}/posting/resume

Request

  • Base URL
    https://api.contentstudio.io
  • URL
    https://api.contentstudio.io/api/v1/workspaces/{workspace_id}/posting/resume
  • Auth
    API key in header X-API-Key

Path parameters

workspace_idstring required
Example:64edbecf78f9fa920f0279fe

Workspace ID

Request body

time_type'resume' | 'recurring' | 'custom'

Example request

{
  "time_type": "resume",
  "recurring": {
    "type": "day",
    "value": 1
  }
}

Response

Posting resumed

statusboolean
messagestring

Example response

{
  "status": true,
  "message": "Posting resumed for this workspace.",
  "data": {
    "time_type": "resume",
    "posts_released": 12,
    "posts_restored": 9,
    "posts_left_as_draft": 3,
    "resumed_at": "2026-09-02T11:02:00+00:00"
  }
}

Changes