Docs

The webhook delivery log

  • In the sandbox
GET
/webhook/deliveries

Since 0.28.0. One webhook's deliveries, newest attempt first (never attempted last), with each delivery's state, failures and times and not the event itself. A client's key with the read scope reads its own webhook's (naming another client answers 404); the operator's key reads the operator's own webhook, or one client's with client; the read-only operator key reads the same. At most limit rows (default 100, at most 500), with truncated when there are more.

Authorization

apiKey
headerAuthorizationBearer <token>

Send your key as a bearer token: Authorization: Bearer <your-api-key>. Health is the only call that needs no key.

Query parameters

client?string
Match^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$
state?string
Value in"pending""delivered""dead"
limit?integer
Range1 <= value <= 500
Default100

Response body

The deliveries.

application/json
  1. response
data*array<>
truncated*boolean
curl -X GET "https://example.com/webhook/deliveries" \  -H "Authorization: Bearer <your-api-key>"
{  "data": [    {      "invoice_id": "string",      "sequence": 0,      "event_id": "string",      "state": "pending",      "failures": 0,      "first_failure_at": "2019-08-24T14:15:22Z",      "last_attempt_at": "2019-08-24T14:15:22Z"    }  ],  "truncated": true}