Inspect a webhook endpoint
Events and webhooks
Inspect a webhook endpoint
Inspect one endpoint and its most recent delivery attempts.
GET
Inspect a webhook endpoint
recentDeliveries is newest-first and includes failures, the response
status and a short response snippet, so a broken receiver can be diagnosed
without server-side logs. An endpoint auto-disables after
8 consecutive failed attempts; re-enable it with
PATCH {"disabled": false} once the receiver is healthy.
Authorization
This route requires theread 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
recentDeliveriesis your debugging surface. It is newest first and includes failures, the response status and a short response snippet.- An endpoint auto-disables after 8 consecutive failed attempts. Bring it back with
PATCH {"disabled": false}once the receiver is healthy.
Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Path Parameters
The webhook endpoint id returned at registration.
Query Parameters
How many recent delivery attempts to return (default 20, max 100).
Response
Successful Response
GET /v1/webhooks/{id}: the endpoint plus its recent delivery tail.
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.