agency-board
GET /v1/agency/board-automation-catalogue
What a rule can be built out of.
Uthibitishaji
Tuma ufunguo wa API kama tokeni ya kubeba. Sehemu hii ya mwisho haitaji ruhusa maalum katika maelezo, kwa hivyo ipe ufunguo wako kiwango cha chini kabisa kinachohitajika na uangalie jibu badala ya kukisia.
Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.
Jaribu
Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.
curl -X GET https://api.zinndigital.com/v1/agency/board-automation-catalogue \
-H "Authorization: Bearer zdk_live_…"Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API
Maelezo
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.
Majibu
| Jina | Aina | Inayohitajika | Kilicho hiki |
|---|---|---|---|
triggers | BoardAutomationTriggerSpec[] | Ndiyo | — |
actions | BoardAutomationActionSpec[] | Ndiyo | — |
operators | BoardAutomationOperatorSpec[] | Ndiyo | — |
platform_events | BoardPlatformEventSpec[] | Ndiyo | — |
Hitilafu ambazo mwisho huu unaweza kurudisha
401