Get a webhook delivery
curl https://api.subscriby.net/v1/webhook-deliveries/$DELIVERY_ID \
-H "Authorization: Bearer $SUBSCRIBY_TOKEN"
One delivery. Another team's delivery is a 404 RESOURCE_NOT_FOUND, never a 403.
| Field | Type | Notes |
|---|---|---|
| event | string | The event name, as in the catalog. |
| event_id | string | The 26-character ULID the envelope's id carries without its evt_ prefix; also the SB-Event-Id header your handler received. |
| status | string | pending, delivered, failed or dead. See below. |
| attempts | integer | Posts made so far. Reset to 0 by a retry. |
| response_status | integer or null | The HTTP status your endpoint returned on the last attempt; null before the first post or after a transport failure. |
| response_excerpt | string or null | The start of the response body, or the transport error. |
| payload | object | The full event envelope that was, or would have been, posted, so a consumer can be debugged against it exactly. |
| next_attempt_at | string or null | When the worker will post a failed row again. |
| delivered_at | string or null | Stamped on the first 2xx. |
| dead_lettered_at | string or null | Stamped when the ladder ran out. |
There is no updated_at: a delivery only moves forward through its statuses, and the three timestamps say when each transition happened.
A row is born pending, becomes failed after a non-2xx or transport error while retries remain, delivered on the first 2xx, and dead once the ladder is exhausted or the endpoint vanished. delivered and dead are final until a retry resets the row to pending.
payload discloses nothing new. The envelope is what your own endpoint already received, or would have had it answered. Reading it needs webhook-delivery:view-any, and the tenant scope reaches a delivery only through an endpoint of the token's team.
Request
- Base URL: https://api.subscriby.net
- URL: https://api.subscriby.net/v1/webhook-deliveries/{delivery}
- Auth: HTTP bearer
Path parameters
The delivery, resolved by the route binder.
Response
The delivery with the envelope its endpoint received.
Example response
{
"data": {
"id": "34f1d78e-05a2-4b69-8c3d-7e921ab06f45",
"endpoint_id": "c62a08f4-1b7d-4e35-9860-a37f5d21e0b9",
"event": "subscription.created",
"event_id": "01HXZ3Q8M7Y2K4N6P9R1T3V5W7",
"status": "failed",
"attempts": 2,
"response_status": 500,
"response_excerpt": "upstream unavailable",
"next_attempt_at": "2026-09-06T10:15:00+00:00",
"created_at": "2026-09-06T10:05:00+00:00"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.