agency-board

GET /v1/agency/boards/{boardId}/automations/{ruleId}/runs

Every time this rule was considered — and why it did or did not fire.

所有 agency-board 端点

身份验证

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

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

免费试用

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

curl -X GET https://api.zinndigital.com/v1/agency/boards/{boardId}/automations/{ruleId}/runs \
  -H "Authorization: Bearer zdk_live_…"

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

详细信息

A row is written whenever the rule was **considered**, not only when it fired, and each carries the result of every condition with the value it actually saw. ⛔ That is the whole point of the endpoint. A rule that does not fire otherwise leaves the customer with an absence, which is indistinguishable from "the trigger never happened", from "it is disabled" and from "the platform is down".

参数

名称类型必填内容简介
boardId (path)UuidProject board ID (UUIDv7).
ruleId (path)UuidAutomation rule ID (UUIDv7).
limit (query)integerMaximum items to return (page size).
cursor (query)stringOpaque cursor from a previous page's `page.next_cursor`.

响应

名称类型必填内容简介
dataBoardAutomationRun[]
pagePageMeta

此端点可能返回的错误

401 · 403 · 404