agency-board
GET /v1/agency/board-automation-catalogue
What a rule can be built out of.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限,因此请为您的密钥赋予所需的最小权限,并通过检查响应来确认,而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织,且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值,并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/agency/board-automation-catalogue \
-H "Authorization: Bearer zdk_live_…"已登录?您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥,并针对实时 API 运行请求,以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Every trigger, condition operator, action and platform event this engine understands, with the context fields each trigger publishes. ⛔ The rule builder reads THIS rather than carrying its own copy of the list. A hardcoded copy in the console is a second source of truth that goes stale the first time a lane adds a trigger — and it goes stale silently, because the builder still renders and simply does not offer the new one. Not board-scoped: the catalogue is the same for every board.
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
triggers | BoardAutomationTriggerSpec[] | 是 | — |
actions | BoardAutomationActionSpec[] | 是 | — |
operators | BoardAutomationOperatorSpec[] | 是 | — |
platform_events | BoardPlatformEventSpec[] | 是 | — |
此端点可能返回的错误
401