Spot. WebSocket snapshot (type "snapshot"), then deltas (type "delta"); a REST snapshot is also fetched at startup.
Live in productionWebSocket200 levels
Live now
-
books live
-
messages / s
-
level changes / s
-
KB / s
Messages / s and KB / s are what our handler receives from the exchange (KB after decompression, REST snapshots included); level changes / s are counted after normalization, for the markets we publish.
data.seq from each delta. Deltas that arrive before the snapshot are buffered and only those newer than the snapshot are replayed; live deltas with seq <= the last applied are dropped. No gap check.
On a gap
A new snapshot message replaces the whole book; otherwise books are rebuilt on reconnect (socket error, close, or 30 s without data; 5 s backoff, doubling), with REST snapshots re-fetched.
Depth
200 levels
Authentication
none
Heartbeat
Application-level {"op":"ping"} every 20 s, as Bybit recommends; we also answer WebSocket pings. A 30 s no-data watchdog forces a reconnect.
At most 10 topics per subscribe message; longer lists are split.
The symbol comes from the topic suffix (orderbook.200.BTCUSDT → BTCUSDT).
WebSocket snapshots wrap the book in "data", REST in "result"; both use b/a arrays of [price, qty], qty "0" deletes.
Book only: the trade channel is not subscribed.
Instruments
loading...
Upcoming and recent changes
2026-11-20InfoNew endpoint: Query Card List
Bybit added a new endpoint to query the Bybit card list.
Details
A new endpoint for querying the Bybit card list was added. It relates to card features, not public order book or trade data. No action is needed for market data handlers.
Our handler: Card list endpoint is an account-related feature outside the public spot orderbook channel and REST orderbook snapshot.
Bybit added a new endpoint to query the Bybit card limit.
Details
A new endpoint for querying the Bybit card limit was added. It relates to card features, not public order book or trade data. No action is needed for market data handlers.
Our handler: Card limit endpoint is an account-related feature outside the public spot orderbook.200 channel and /v5/market/orderbook snapshot.
2026-11-12InfoTrading and matching engine migrated to AWS TokyoMay affect market data
Bybit says it moved its trading and matching engine service to AWS Tokyo (apne1-az4) on 12 Nov 2026.
Details
The banner gives no endpoint or format changes. Feed latency and routing from the matching engine may differ, so check latency and sequence behaviour on the spot orderbook.200 stream and the REST snapshot. No client action is stated.
Our handler: The matching engine move could change latency for wss://stream.bybit.com/v5/public/spot orderbook data, though no change to it is announced.
2026-11-03InfoTokyo Dedicated Host has extra connection limit for JSON Market DataMay affect market data
The JSON market data documentation notes that the Tokyo Dedicated Host gets an extra connection limit.
Details
No details are given about the host name or limit size. If we use or plan to use a dedicated host in Tokyo, review the documented connection limits. Our current public stream host is unchanged.
Our handler: It concerns JSON market data connection limits, which could matter for our WebSocket connections, but we use the standard stream.bybit.com host.