POST /v1/board-hooks/{endpointKey}

Xaqiijinta aqoonsiga

Bankigan (endpoint) waa mid dadweyne. Ma qaato wax aqoonsi ah ama urur ah — waa waxa ay site-keenna suuqgeynta iyo matoorada jawaabaha ee AI ay akhriyaan.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

curl -X POST https://api.zinndigital.com/v1/board-hooks/{endpointKey} \
  -H "Content-Type: application/json" \
  -d '{  }'

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Faahfaahin

**Unauthenticated by design: the HMAC signature IS the authentication**, exactly as `/v1/webhooks/stripe` is. Send `X-Zinn-Signature: sha256=<hmac-sha256 over "<timestamp>.<raw body>">` and `X-Zinn-Timestamp` (unix seconds, within five minutes of now), signed with the endpoint's secret. The body must be a JSON object. Five top-level values — `event`, `status`, `title`, `body`, `ref` — are projected into the rule's condition surface as `payload_*`, so a rule can branch on them. Anything else in the body is stored in the request log and is not conditionable. ⛔ An unknown endpoint key and a bad signature both answer **404 with the same body**, deliberately: distinguishing them would turn this into an oracle for whether a key exists. The endpoint's OWNER sees the real reason on their own screen.

Cabiraha

Codsiga jidhkiisa

Jawaab

Cilladaha ay bartaani soo celin karto

404 · 409 · 413 · 429