Webhooks
Subscriptions to be notified on. Each carries an action, a destination URL and a
token — and the token is sent as the Authorization header of the delivery
request, which is how your endpoint recognises a genuine call.
There are five event classes:
action | Fires on |
|---|---|
deposit | A change of status on an incoming transfer |
withdrawal | A change of status on a payout |
order | An order reaching a terminal state — done, fail or cancel |
trade | A fill against one of your customers' orders |
market | A change to a market |
All three fields are required. To change a URL or a token, delete the subscription and create it again.
Before you rely on deliveries
Read Receiving Deliveries first. In short: one
subscription per action covers all statuses of that entity, the payload is
authenticated by a static token and not signed, and there are no retries and
no ordering guarantees — so the receiver has to be idempotent.