links

PATCH `/v1/content/run-schedules/{scheduleId}`

Change or pause a cadence.

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X PATCH https://api.zinndigital.com/v1/content/run-schedules/{scheduleId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Any subset of the fields. Setting `enabled` to false stops future runs and leaves every run it has already made alone. Gated on `links.edit`.

Parameters

Name	Type	Required	What it is
`scheduleId (path)`	`string`	Yes	—

Request body

Name	Type	Required	What it is
`brief`	`string`	No	—
`site_ids`	`string[]`	No	—
`anchors`	`ContentRunAnchor[]`	No	—
`category`	`string`	No	—
`publish_policy`	`ContentRunPublishPolicy`	No	How far a run may go on its own. `draft_only` is the default and puts nothing live.
`interval_hours`	`integer`	No	—
`enabled`	`boolean`	No	—
`recipe_id`	`string`	No	—

Response

Name	Type	Required	What it is
`id`	`string`	Yes	—
`enabled`	`boolean`	Yes	—
`interval_hours`	`integer`	Yes	—
`next_run_at`	`string`	Yes	—
`last_run_at`	`string`	No	—
`last_run_id`	`string`	No	—
`brief`	`string`	Yes	—
`category`	`string`	No	—
`publish_policy`	`ContentRunPublishPolicy`	Yes	How far a run may go on its own. `draft_only` is the default and puts nothing live.
`site_ids`	`string[]`	Yes	—
`recipe_id`	`string`	No	—

Errors this endpoint can return

401 · 403 · 404 · 422

PATCH /v1/content/run-schedules/{scheduleId}