Webhook deliveries API
Environment: Sandbox
List webhook deliveries and their retry state.
# Webhook deliveries API
List the webhooks Moolre has sent, or is still retrying, to your wallet callback URLs, newest first. Use it to see which events were delivered, which are still being retried and which gave up.
## Endpoint
- **Method**: POST
- **URL**: https://sandbox.moolre.com/open/webhook/deliveries
## Headers
| Header | Type | Required | Description |
| :--- | :--- | :--- | :--- |
| X-API-USER | string | Yes | Your Moolre username. |
| X-API-KEY | string | Yes | Your wallet private API key. A public key is refused. |
## Request Body
| Parameter | Type | Required | Description |
| :--- | :--- | :--- | :--- |
| accountnumber | string | Yes | Your Moolre wallet account number. |
| event | string | No | Filter by event name, for example payment.succeeded. |
| state | string | No | pending (still retrying), delivered or dead (gave up). |
| from | string | No | YYYY-MM-DD or a UTC date and time. |
| to | string | No | YYYY-MM-DD or a UTC date and time. |
| limit | integer | No | 1 to 100. Default 25. |
| starting_after | string | No | An event_id: send next_cursor from the previous page. |
| include_payload | integer | No | Send 1 to include the event body that was sent. |
## Response (200 Success)
A page of delivery records.
```json
{
"status": 1,
"code": "WHD01",
"message": "Webhook deliveries",
"data": {
"items": [
{
"event_id": "evt_0123456789abcdef01234567",
"event": "payment.succeeded",
"state": "dead",
"attempt": 9,
"last_http": 500,
"last_error": null,
"created": "2026-11-14T09:00:00Z"
}
],
"has_more": false,
"next_cursor": null
},
"go": null,
"meta": {
"requestid": "req_c68f4c66115c26725c796242",
"notices": []
}
}
```
## Fields every response can carry
These fields are additive: existing fields keep their names, order and types.
| Field | Meaning |
| :--- | :--- |
| error | On a failure: { code, message, fields: [{ field, code, message }] } listing every failing field. |
| meta | Always present, last in the object. meta.replayed is true only when the response is the stored answer to a repeated Idempotency-Key (absent otherwise). meta.requestid is the unique id of the request (also the X-Request-Id response header): quote it when you contact support. meta.notices is always an array, empty when there is nothing to report; each notice is { code, message, docs? }, for example that a deprecated way of sending credentials was used. See [Deprecations](https://docs.moolre.com/guides/deprecations). |
There is no outcome field. Decide the result from status, code and, on payment and transfer endpoints, data.txstatus (0 pending, 1 succeeded, 2 failed). These codes mean the result is unknown and may still succeed, so treat them as pending and check the status: PY01, PY02, TR01, TR02, TP11, TP18, APY10, APY16, ASL06, SYS500. Status 1 with TR08, OBGH01, OTGH01, OBNG01, GHQ03 or OM03 is final success; any other status 1 is an accepted, unfinished request.
Send X-Moolre-Http-Status: strict to receive real HTTP status codes (400, 401, 403, 404, 409, 422, 429, 5xx) instead of HTTP 200. See [Responses and request IDs](https://docs.moolre.com/guides/responses).