Feeds / Crypto exchanges (live)

Bitget

Spot. WebSocket snapshot, then deltas; a REST snapshot fetched about 2 s after subscribing is used only if the WebSocket snapshot has not arrived.

Live in productionWebSocketFull-depth channel; REST seed of 150 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.

Open live books Replay

How we connect

Market
Spot
WebSocket
wss://ws.bitget.com/v2/ws/public
Channels
books — full-depth book: snapshot, then incremental updates (200 ms)
trade — trades
Update model
WebSocket snapshot, then deltas; a REST snapshot fetched about 2 s after subscribing is used only if the WebSocket snapshot has not arrived.
Snapshot (REST)
https://api.bitget.com/api/v2/spot/market/orderbook?symbol={SYMBOL}&type=step0&limit=150
Sequencing
seq on each update. Updates before the snapshot are buffered and replayed if newer; anything at or below the last applied seq is dropped. Gaps between seq values are not detected and the checksum is not verified.
On a gap
No in-stream resync; on reconnect (socket error or 30 s without data) sync state is cleared, the client resubscribes for fresh WebSocket snapshots and refetches REST snapshots.
Depth
Full-depth channel; REST seed of 150 levels
Authentication
none
Heartbeat
Client sends "ping" every 30 s; WebSocket pings answered; reconnect after 30 s without data.
Symbol format
BTCUSDT

Subscribe message

{"op":"subscribe","args":[{"instType":"SPOT","channel":"books","instId":"BTCUSDT"},{"instType":"SPOT","channel":"trade","instId":"BTCUSDT"},...]}

What our handler takes care of

Instruments

loading...

Official documentation

Bitget — spot WebSocket depth channel ↗www.bitget.comBitget — spot WebSocket trades channel ↗www.bitget.comBitget — spot order book depth (REST) ↗www.bitget.comBitget — WebSocket intro (limits, ping) ↗www.bitget.com

Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.