Send test webhook API
Environment: Live
Send a signed test webhook to your callback URL.
# Send test webhook API
Send a signed webhook.test event to the callback URL on your wallet right now, with the same headers, signature and body envelope as a real event, and see what your endpoint answered. A test event is sent once, with no retries, and appears in Webhook deliveries.
## Endpoint
- **Method**: POST
- **URL**: https://api.moolre.com/open/webhook/test
## 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. |
## Response (200 Success)
The test event was sent. data.delivered tells you whether your endpoint accepted it (a 2xx answer).
```json
{
"status": 1,
"code": "WHT01",
"message": "Test webhook delivered.",
"data": {
"event_id": "evt_0123456789abcdef01234567",
"delivered": true,
"http": 200,
"error": null,
"response": "ok"
},
"go": null,
"meta": {
"requestid": "req_c68f4c66115c26725c796242",
"notices": []
}
}
```
## Response (200 (HTTP 422 in strict mode) No callback URL)
The wallet has no callback URL. Set one with Update account.
```json
{
"status": 0,
"code": "WHT02",
"message": "No callback URL is set on this wallet.",
"data": "callback",
"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).