Skip to main content
The orders channel sends the orders of the account behind your API key: a snapshot right after login, then the whole order every time it changes.

Snapshot

Right after login_ok, you receive:
orders holds every working order, plus every order that changed in the last 24 hours. Each order has the shape of GET /v1/orders/{id}.

Changes

Every change to an order sends the whole order again:
A change is anything that moves the order or one of its bets: a fill, a decline, a cancellation, an expiry, a settlement or a correction. For each order id, keep the order with the highest version, and ignore one with a lower or equal version: the same version can arrive twice.

Resume

eventId exists for resuming. Keep the highest eventId you received, the snapshot’s included. When you reconnect, log in with it:
  • Inside the window. At most 1 000 changes were missed and the oldest is less than 10 minutes old: the orders that changed are sent as order messages, then the live changes follow. No snapshot is sent.
  • Outside the window. You receive { "type": "snapshot_required", "reason": "resume_window_exceeded", "channels": ["orders"] }, then a new snapshot. Replace what you held with it.
A login without sinceEventId always starts with a snapshot.

Without the channel

A login that names channels without orders receives none of this. A login without channels covers every channel, orders included.