Deliveries
List deliveries
List webhook delivery attempts with filters
GET
List deliveries
Debug what reached your endpoint — attempt count, response code, response body excerpt, error.
Rows older than 30 days are eligible for automatic pruning (terminal statuses only —
Scope
webhooks:readHeaders
API key.
Query parameters
Filter to one subscription (UUID).
Filter by status. One of
pending, succeeded, failed, permanently_failed.RFC3339 timestamp. Inclusive lower bound on
createdAt.RFC3339 timestamp. Exclusive upper bound on
createdAt.Page size. Default
50, max 200.Pagination offset. Default
0.Response
Delivery UUID.
UUID of the subscription this delivery belongs to.
Event type, e.g.
payout.status.updated.The full JSON envelope POSTed to your endpoint.
pending, succeeded, failed, or permanently_failed. See below.Number of times Teel has POSTed this delivery.
ISO 8601 timestamp of the next scheduled retry.
null when in a terminal state.HTTP status of the most recent attempt.
null if no transport-level response (timeout, connect refused).Excerpt of the most recent response body. May be truncated.
Transport error message from the most recent failed attempt.
null on success.ISO 8601 timestamp.
ISO 8601 timestamp of the first successful delivery.
null until success.Delivery statuses
| Status | Meaning |
|---|---|
pending | In the queue. Either not yet attempted, or scheduled for retry (nextAttemptAt in the future). |
succeeded | Your endpoint responded 2xx within the 10s timeout. deliveredAt is populated. |
failed | An attempt was non-2xx, timed out, or hit a transport error. Will retry on the schedule (~30s, 2m, 8m, 32m) until budget exhausted. |
permanently_failed | All 5 attempts failed. The delivery will not retry automatically — use Replay to enqueue a fresh attempt. |
pending and in-retry rows are never deleted).
List deliveries