links

GET /v1/content/runs

Multi-site AI posting runs.

All links endpoints

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 GET https://api.zinndigital.com/v1/content/runs \
  -H "Authorization: Bearer zdk_live_…"

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

Every run this organisation has started, newest first, each with its per-site outcomes. Gated on `links.view`. A **run** is one *"write this brief and put it on these sites"*. It executes as a durable Temporal workflow rather than on a request thread, so a provider outage, a rate limit or a worker restart pauses or retries it instead of losing it. The `state` says where it got to; `totals` says how many sites worked; `items` says what happened to each one and why.

Parameters

NameTypeRequiredWhat it is
state (query)ContentRunStateNoOnly runs in this state.
limit (query)integerNo
offset (query)integerNo

Response

NameTypeRequiredWhat it is
itemsContentRun[]Yes
totalintegerYes
offsetintegerYes
limitintegerYes
has_morebooleanYes

Errors this endpoint can return

401 · 403