GET /v1/agency/board-automation-catalogue

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/agency/board-automation-catalogue \
  -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 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.

Response

Errors this endpoint can return

401