Get webhook
Read a webhook by ID or name, with its status and delivery summary.
/webhooks/{webhook}PermissionCluster key, or a scoped key with read on a namespace or collection that the webhook covers. Key scopes and actions.
- The answer never holds the secret. signing.secret_fingerprint identifies it.
- A key gets 404 for a webhook that covers nothing in its scope, and 403 for one that it can see but cannot manage.
Path parameters
Webhook ID with the whk_ prefix, or the webhook’s name.
Responses
200Success
The webhook with its status and delivery summary.
application/json
Response headers
The Engine request ID. Retain it when investigating a failed or unexpected request.
The X-Request-Id you sent, echoed when it is a valid ID. Otherwise, the Engine request ID.
Time the resource was created, as an ISO 8601 UTC timestamp.
Delivery summary: pending events and the times of the last success and failure.
Why the webhook is off: requested (a key set enabled false) or failing (Engine turned it off). Null while it is on.
- requested
- A key set enabled to false.
- failing
- Engine turned the webhook off: the receiver answered 410, or sent no 2xx for 72 hours.
Whether Engine queues and sends events.
Immutable webhook ID with the whk_ prefix.
Webhook name. It never changes. Each POST sends it in X-Graphon-Events-Webhook.
The webhook’s scope. A namespace or collection key sees only its own namespace and collections in it.
The signing secret: whsec_ and the base64 of 32 random bytes. Only the answers to Create and Rotate hold it. Store it before you continue.
Fingerprints that identify the signing secrets, and the end of a rotation overlap.
Event types that the webhook gets. Null means every type, also types added later.
Time the resource last changed, as an ISO 8601 UTC timestamp.
Receiver URL that Engine POSTs to.
Errors
Select an error in the response example to see its JSON body. See error handling for the common error format.
- 400invalid_request
A field, path, parameter, or conditional request rule is invalid.
What to do: Correct the request. Unknown fields are rejected.
- 401unauthenticated
The API key is missing, invalid, or revoked.
What to do: Send an active key in Authorization: Bearer or X-API-Key.
- 403forbidden
The key can see the resource but lacks permission for this operation.
What to do: Use a key with the required action or scope kind.
- 404not_found
The resource is absent, deleted, or outside this key’s scope.
What to do: Check the identifier and the key’s namespace and collection scope.
- 500internal_error
An unexpected server failure prevented this request from completing.
What to do: Retain request_id for investigation. Follow retryable before retrying a write.