links

GET `/v1/content/runs/{runId}`

One run, with every site's outcome.

身份验证

请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

curl -X GET https://api.zinndigital.com/v1/content/runs/{runId} \
  -H "Authorization: Bearer zdk_live_…"

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。在 API 控制台中打开此端点

The whole run screen in one call. Gated on `links.view`. 404 rather than 403 for a run in another tenant — a 403 would confirm the row exists.

名称	类型	必填	内容简介
`runId (path)`	`string`	是	—

名称	类型	必填	内容简介
`id`	`string`	是	—
`state`	`ContentRunState`	是	Where a run got to. `partial` is a real, honest, terminal answer and not a euphemism: some sites published and some did not, nothing is left to try, and the failures can be resu…
`publish_policy`	`ContentRunPublishPolicy`	是	How far a run may go on its own. `draft_only` is the default and puts nothing live.
`recipe_id`	`string`	否	—
`brief`	`string`	是	—
`category`	`string`	否	—
`post_id`	`string`	否	The article this run wrote. Written once and reused for every site, so a resumed run places the SAME copy rather than paying for a second generation.
`attempt`	`integer`	是	Which pass over the failures this is. 0 is the original run.
`workflow_id`	`string`	否	—
`totals`	`ContentRunTotals`	是	—
`reason`	`ContentRunFailureReason`	否	—
`provider`	`string`	否	—
`message`	`string`	否	An English sentence for the customer. Clients should render their own localised text from `reason` and fall back to this only for a code they do not know.
`resumable`	`boolean`	是	Whether a resume would actually do anything. False on a paused run with nothing failed — do not offer the button when this is false.
`started_at`	`string`	否	—
`finished_at`	`string`	否	—
`created_at`	`string`	是	—
`items`	`ContentRunItem[]`	是	—

401 · 403 · 404