> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bullionwale.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting webhooks

> Common webhook delivery problems and how to fix them.

> [!WARNING]
>
> **Not available yet.** Webhooks are being built and are not part of the API today: there is no way to subscribe yet, and no events are sent. This page describes the planned design so you can prepare; details may change before release.

> **The signature never verifies**
>
> Verify against the **raw** request body, before any JSON parsing or re-encoding; many frameworks hand you a parsed body by default. Check that you sign `t + "." + body` (with the dot), use the secret of the right endpoint and environment, and compare hex strings. See [Signature verification](/webhooks/signature-verification).

> **Every delivery is rejected as too old**
>
> Your server's clock is off. Synchronise it with NTP; the timestamp check compares `t` with your clock.

> **The same event arrives twice**
>
> That is expected: delivery is at least once. Store each event id you have processed and ignore repeats.

> **Deliveries keep being retried although my handler works**
>
> Your endpoint is probably answering too slowly or with a non-`2xx` status. Acknowledge with `2xx` straight away and process the event afterwards. Point the subscription at the final URL: any status other than `2xx` counts as a failure.

> **I stopped receiving events**
>
> After repeated failures an event is dead-lettered and not sent again. Fix your endpoint, then catch up by reading your orders with `GET /orders` and `since`. See [Retries and dead-lettering](/webhooks/retries).

> **An event refers to an order my state does not know yet**
>
> Events can arrive out of order. Read the order with `GET /orders/{order_id}` and use its current `status`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.