links

PATCH `/v1/content/campaigns/{campaignId}/runs/{runId}`

Move one queued article to a different moment.

Authentication

Send an API key as a bearer token. The key must carry the links.edit permission; a key without it is refused with 403, not 404.

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/campaigns/{campaignId}/runs/{runId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "starts_at": <string> }'

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

Refused with 422 once the article has started: its copy already exists and its placements already carry their own times, so "reschedule" would quietly mean something else. Gated on links.edit.

Parameters

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

Request body

Name	Type	Required	What it is
`starts_at`	`string`	Yes	When this article should be written and placed.

Response

Name	Type	Required	What it is
`campaign_id`	`string`	Yes	—
`brief`	`string`	Yes	—
`total`	`integer`	Yes	—
`pending`	`integer`	Yes	—
`done`	`integer`	Yes	—
`failed`	`integer`	Yes	—
`paused`	`integer`	Yes	—
`cancelled`	`integer`	Yes	—
`next_at`	`string`	No	—
`last_at`	`string`	No	—
`site_count`	`integer`	Yes	—
`runs`	`ContentCampaignRun[]`	Yes	—

Errors this endpoint can return

401 · 403 · 404 · 422

PATCH /v1/content/campaigns/{campaignId}/runs/{runId}