Webhooks
Subscriptions to be notified of deposit, withdrawal, order, trade and market
events. Each carries an action, a destination URL and a
token — and the token is sent on every delivery request, in both the
Webhook-Token and Authorization headers, 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. Registering the same action twice creates a
second subscription, and each one receives its own copy of every delivery — so
to change a URL or a token, delete the old subscription first, then create the new
one.
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.