Outgoing webhook management
Outgoing webhook management
DELETE Delete a webhook — Deletes one outbound webhook from the current organization and stops future deliveries for that webhook immediately.GET List organization webhooks — Returns every outbound webhook configured for the current organization.GET List supported webhook events — Returns the event names you can subscribe to when creating or updating an outbound webhook, together with a short human-readable description for each event.GET List webhook delivery history — Returns recent delivery attempts for one webhook, ordered from newest to oldest. Pagination uses the shared offset pagination query schema.POST Register a new webhook — Registers a URL to receive event notifications. The URL must use HTTPS and resolve to a public IP. Events are signed with HMAC-SHA256.POST Retry a failed webhook delivery — Queues a new delivery attempt for a previously failed webhook delivery. Only deliveries in the failed state can be retried.POST Rotate a webhook's signing secret — Generates a new signing secret for one webhook and returns the new plaintext value once.POST Send test payload to a webhook — Sends a test event to the webhook URL and reports delivery status. Use this to verify endpoint connectivity and inspect the remote response.Was this page helpful?
Set booking outcome (completed / no-show)
Records the final outcome of a confirmed booking in the current organization. Organization API keys with `scheduling:write` and authenticated operator sessions are supported. Only bookings that still have `status: "confirmed"` can be updated. Allowed outcomes are `completed` and `no_show`. Authenticate with an organization API key sent in `X-API-Key` or as a Bearer token and carrying the exact `scheduling:write` scope. API-key access also requires the Automation & API module (`automation_api`). Authorized dashboard sessions remain supported where the route already permits them. The request is isolated to the authenticated organization. Resource and site/project identifiers must belong to that organization; out-of-scope identifiers are not disclosed. Only organization API keys and operator sessions can record outcomes. Allowed body values are exactly `completed` and `no_show`. Retry behavior: Outcome recording is a terminal transition from `confirmed` to `completed` or `no_show`. Repeating the request returns `422`; after an ambiguous timeout, read the booking before retrying.
Delete a webhook
Deletes one outbound webhook from the current organization and stops future deliveries for that webhook immediately. The active-webhooks cache is invalidated so the removal takes effect right away. Admin access is required, and the route returns `404` when the webhook does not exist for the current organization. Access requires an active organization administrator session or an organization API key with the `webhooks:write` scope. API-key calls also require the automation API module. Data is isolated to the authenticated organization; identifiers from another organization or site are not disclosed.