Event catalog - Bullionwale API

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.

Order events

Event	Sent when
`order.booked`	An order is booked (a production order becomes `open`).
`order.closed`	Bullionwale closes an order. Its closing price and realized profit or loss are then set.
`order.rejected`	Bullionwale’s hedge refuses a production order. Nothing was booked.

Limit-order events

Limit orders are not yet available in the API either; these events arrive with them.

Event	Sent when
`limit_order.placed`	A limit order is accepted and starts waiting for its trigger price.
`limit_order.triggered`	The live price reaches the trigger and the limit order becomes an order.
`limit_order.cancelled`	A limit order is cancelled before it triggers.

Every event carries

a unique event id, the same on every delivery attempt, for de-duplication;
the event type, one of the names above;
the environment, test or production;
the time the event happened;
the object it is about, for example the order.

The exact payload shapes will be published here, with examples, when webhooks are released. Amounts and weights will follow the same rules as the API: decimal strings, in the units described in Units and pricing.