Skip to main content
GET
Pulls the full record of one delivery — event name, delivery status, HTTP response code, attempt count, and the payload and the first-attempt signature. This is the best tool for debugging a failing verifier, with two caveats: the record does not store the signed timestamp (only createdAt/lastAttemptAt dates), so the HMAC cannot be recomputed from this record alone; and the stored signature is the first attempt’s — retries re-sign with a fresh timestamp but this field is not refreshed, so for a retried delivery it is not the signature your endpoint last received. The verification recipe (timestamp window, HMAC over the raw body, constant-time compare, dedupe on the delivery id) is in the Webhooks & IPN guide.

​
Who can call this

Dashboard only — not accessible with an API key. Send your dashboard JWT (browser session) as a Bearer token, with team role merchant_admin or merchant_member plus the webhooks:view permission. Deliveries are tenant-scoped end to end: you only ever see your own merchant’s deliveries. See the Authentication guide.

​
Path parameters

​
string
required
The delivery id, as returned in the rows of List deliveries.
Use this record to inspect the exact payload bytes. Note that you cannot fully re-verify the HMAC from it — the signed timestamp is not stored, and the signature shown is the first attempt’s, not necessarily the one delivered on a retry. To test your verifier end-to-end, capture the x-liddie-sig and x-liddie-timestamp headers at your own endpoint.

​
See also