These endpoints use dashboard (JWT) authentication, not the
/api/v1/* API key surface. Your Supabase session must have the
webhooks:manage permission.Create a subscription
webhooks:manage | Status: 201 Created
Request body
Available event types
All 17 event types
All 17 event types
Response
The response includes asigning_secret field that is shown only
once. Store it securely — you’ll need it to
verify webhook signatures.
List subscriptions
webhooks:manage | Status: 200 OK
Query parameter: include_disabled (boolean, default false) — set to
true to include auto-disabled subscriptions.
The signing_secret field is not returned on list/get — only on
create and rotate.
Delete a subscription
webhooks:manage | Status: 204 No Content
Rotate signing secret
Issues a new signing secret for an existing subscription. A 24-hour grace window accepts signatures from both the old and new secret, giving you time to deploy the new secret without downtime.webhooks:manage | Status: 200 OK
The response includes the new signing_secret (shown once). During the
grace window, the X-Yotel-Signature header contains both signatures:
sha256=OLD,sha256=NEW — your verification code should accept either.
Test a subscription
Sends a synchronous test event to your endpoint and reports the result immediately. This is a dry-run — it bypasses the delivery log.webhooks:manage | Status: 200 OK
Request body
Response
View delivery log
Inspect recent deliveries for a subscription — status, response codes, timing, and retry schedule.webhooks:manage | Status: 200 OK

