Feeds / Crypto exchanges (live)

Gate

Spot. WebSocket diffs, seeded by a REST snapshot; a message flagged full:true is applied as a full snapshot.

Live in productionWebSocketREST snapshot of 100 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://api.gateio.ws/ws/v4/
Channels
spot.order_book_update — diffs, 100 ms
spot.trades — trades
Update model
WebSocket diffs, seeded by a REST snapshot; a message flagged full:true is applied as a full snapshot.
Snapshot (REST)
https://api.gateio.ws/api/v4/spot/order_book?currency_pair={SYMBOL}&limit=100&with_id=true
Sequencing
Diffs are buffered until the REST snapshot arrives; buffered diffs with u <= the snapshot id are dropped and the rest replayed. After that, U is not checked against the previous u + 1.
On a gap
No in-stream gap check; on reconnect (socket error, close, or 30 s without data) sync is reset and REST snapshots re-fetched. Snapshots are also re-applied every 10 minutes.
Depth
REST snapshot of 100 levels
Authentication
none
Heartbeat
WebSocket pings answered; reconnect after 30 s without data.
Symbol format
BTC_USDT

Subscribe message

{"time":1794862821,"channel":"spot.order_book_update","event":"subscribe","payload":["BTC_USDT","100ms"]}

What our handler takes care of

Instruments

loading...

Official documentation

Gate API v4 — WebSocket (spot) ↗www.gate.comGate API v4 — REST (order book, rate limits, changelog) ↗www.gate.com

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