Update a webhook endpoint
Events and webhooks
Update a webhook endpoint
Change an endpoint’s url, subscriptions or enabled state.
PATCH
Update a webhook endpoint
A new url is validated exactly like registration (https, public address).
Setting
disabled to false also clears the failure streak, which is how
an auto-disabled endpoint is brought back after the receiver is fixed. The
signing secret is unchanged and is not re-issued.
Authorization
This route requires thewrite scope.
A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.
Headers
These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.Success responses
Errors
Every error is an RFC 9457
application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.
Notes
- Setting
disabledto false also clears the failure streak. That is how an auto-disabled endpoint is re-enabled. - The signing secret is unchanged. There is no rotation route in v1: register a new endpoint and delete the old one.
Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Path Parameters
The webhook endpoint id returned at registration.
Body
application/json
Response
Successful Response
A registered webhook endpoint. The signing secret is never included.
Subscribed event types that no emitter publishes yet, so nothing will be delivered for them. The subscription is kept and starts delivering as soon as the emitter ships; this field exists so you never wait on an event silently.