orderbook_delta
The first message per market is a full orderbook_snapshot. After that you get
deltas:
qty is the new aggregate at that price level, not a change to apply. Set
the level to qty; do not add. A qty of 0 means the level is now empty.Per-order data is never published — this is an aggregated L2 book.
trades
Public tape entries as they print, including a path of direct, mint or
merge. Only tick_yes is sent; the NO price is 100 - tick_yes.
ticker
Conflated to roughly hundreds of milliseconds.
ticker is a display feed, not a correctness feed. It is deliberately
lossy — intermediate updates are dropped. Never drive trading decisions,
position accounting or risk checks from it. Use orderbook_delta for the book
and user for your own state.
user
The private channel. Subscribe with no market_ids; it is scoped to your key’s
account automatically, and there is no parameter that could point it at another
user.
It carries order lifecycle events, fills with their ledger entries, position
changes, and balance updates — including the reservation and fee accounting that
the order placement response deliberately omits.
A client that folds this stream holds a correct live copy of its orders,
positions and balances without ever polling. That is the intended way to run a
bot.
Continuity is tracked by a per-user channel_seq rather than the envelope
seq, and unlike the public channels it supports replay, so a brief
disconnection does not force you to re-read everything over REST. 
