Get webhook deliveries
Returns recent webhook delivery attempts for the integrator, newest first.
Use this to tell “Spritz never sent it” apart from “my endpoint rejected it” — from the outside both look like silence.
Read error first — it is what separates the two cases.
success: true— your endpoint accepted the delivery, andresponseStatusis what it returned.success: false, noerror, with aresponseStatus— the request reached your endpoint and it responded with that status. Your handler is being called and is failing.success: falsewith neithererrornorresponseStatus— the outcome was not recorded. Only older records look like this; every delivery the current sender writes carries a status. There is nothing to diagnose from them.success: falsewith anerror— no usable response came back: a timeout, a refused connection, a DNS or certificate problem.errorcarries the underlying reason (for examplegetaddrinfo ENOTFOUND ...). Note thatresponseStatusis still present here — 504 for a timeout, 500 otherwise — but it is our classification of the failure, not something your endpoint said. Do not read it as your handler’s response.
An
errordoes not prove the event was not processed. A refused connection means it never arrived, but a timeout or a dropped connection may mean your endpoint received and fully handled the event and we simply never heard the answer. Treat these as unknown, not as not delivered — re-running non-idempotent work on the strength of anerroris how you double-process. This is the case idempotent handlers exist for.
payload is the exact body that was sent, and the body the Signature header was computed over, so it can be replayed against your own verification code.
Cursor-paginated: pass the previous response’s nextCursor as cursor to walk further back. nextCursor is null on the last page.
Deliveries are recorded for every webhook on the integrator. Scope is your own integrator only.
Authorizations
HMAC signature authentication for backend integrators.
Required Headers:
- X-Integrator-Key: Integrator API key (format: int_...)
- X-Signature: HMAC signature (format: sha256={hex})
- X-Timestamp: Unix timestamp in milliseconds
- Authorization: Bearer {user-api-key}
Signature Algorithm: HMAC-SHA256
Signature Format: {timestamp}.{METHOD}.{path}.{bodyHash}
- timestamp: Unix timestamp in milliseconds
- METHOD: HTTP method in UPPERCASE (GET, POST, etc.)
- path: Request path (e.g., /v1/transactions)
- bodyHash: SHA256 hex digest of request body (empty string if no body)
Timestamp Tolerance: ±5 minutes (300 seconds)
Example: For POST /v1/transactions with body {"amount":100} and timestamp 1234567890000: Payload: 1234567890000.POST./v1/transactions.{sha256(body)} Signature: sha256=abc123...
Integrator API key (format: int_...) used with HMAC authentication
Unix timestamp in milliseconds for replay attack prevention. Must be within 5 minutes of server time.
Query Parameters
Maximum number of results to return
1 <= x <= 100Opaque cursor from the previous response's nextCursor value
^[a-fA-F\d]{24}$