EaserixDocs
DevelopersAPI referenceLinksWebhooks

List a webhook's deliveries

This webhook's own delivery attempts, newest first. The payload sent and the signature used are never returned here — the receiving endpoint already saw both at delivery time; this is for finding (and, for a dead one, replaying) a delivery, not re-reading its body.

View as Markdown
GET
/v1/webhooks/{id}/deliveries

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Query Parameters

status?string

Filter to one delivery status (e.g. dead).

Value in

  • "pending"
  • "delivering"
  • "succeeded"
  • "dead"
limit?integer
Range1 <= value <= 200
Default50

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/webhooks/string/deliveries"
{  "deliveries": [    {      "id": "string",      "webhookId": "string",      "event": "string",      "status": "pending",      "attemptCount": 0,      "maxAttempts": 0,      "lastStatusCode": 0,      "lastError": "string",      "nextAttemptAt": "2019-08-24T14:15:22Z",      "created": "2019-08-24T14:15:22Z"    }  ]}

Send a test delivery

Queues a signed "ping" delivery so the endpoint wiring can be verified.

Replay a dead delivery

Requeues a dead delivery for another attempt, reusing the same delivery record and its existing id — never a new one — so the X-Easerix-Delivery header the receiving endpoint already saw stays identical across the replay. Only a delivery currently in the dead state can be replayed; every other status is rejected. Delivery itself happens the normal way afterward (the usual claim/lease/ retry machinery), not synchronously from this call.