links

POST `/v1/content/run-schedules`

Post to these sites every N hours.

身份验证

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

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

免费试用

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

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

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

详细信息

Creates a cadence. The first run happens one interval from now, not immediately — a customer setting up a daily schedule at 4pm expects one tomorrow, not one before they have finished reading the form. Gated on `links.edit`. The cadence is served by a durable workflow on the worker, not by a job that calls this API back, so a scheduled run behaves identically to one started by hand. Minimum interval is one hour: anything finer on a private network is a footprint.

请求正文

名称	类型	必填	内容简介
`brief`	`string`	否	—
`site_ids`	`string[]`	否	—
`anchors`	`ContentRunAnchor[]`	否	—
`category`	`string`	否	—
`publish_policy`	`ContentRunPublishPolicy`	否	How far a run may go on its own. `draft_only` is the default and puts nothing live.
`interval_hours`	`integer`	否	—
`enabled`	`boolean`	否	—
`recipe_id`	`string`	否	—

响应

名称	类型	必填	内容简介
`id`	`string`	是	—
`enabled`	`boolean`	是	—
`interval_hours`	`integer`	是	—
`next_run_at`	`string`	是	—
`last_run_at`	`string`	否	—
`last_run_id`	`string`	否	—
`brief`	`string`	是	—
`category`	`string`	否	—
`publish_policy`	`ContentRunPublishPolicy`	是	How far a run may go on its own. `draft_only` is the default and puts nothing live.
`site_ids`	`string[]`	是	—
`recipe_id`	`string`	否	—

此端点可能返回的错误

401 · 403 · 422

POST /v1/content/run-schedules