Feeds / Crypto exchanges (live)

HTX (formerly Huobi)

Spot. Full book in every message; each push replaces the book.

Live in productionWebSocketUp to 150 levels per side

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.huobi.pro/ws
Channels
market.{symbol}.depth.step0 — unaggregated depth, full book every second
market.{symbol}.trade.detail — trades
Update model
Full book in every message; each push replaces the book.
Sequencing
None needed: each message is a complete book; both sides are parsed before the book is touched and empty snapshots are skipped.
On a gap
Not applicable; reconnect and resubscribe after a socket error or 30 s without data.
Depth
Up to 150 levels per side
Authentication
none
Heartbeat
HTX sends {"ping":ts} about every 5 s; we echo {"pong":ts}.
Symbol format
btcusdt

Subscribe message

{"sub":"market.btcusdt.depth.step0","id":"d-btcusdt"}

What our handler takes care of

Instruments

loading...

Official documentation

HTX spot API — WebSocket market depth ↗huobiapi.github.ioHTX spot API — heartbeat and connection (gzip, ping/pong) ↗huobiapi.github.ioHTX spot API — market depth (REST) ↗huobiapi.github.ioHTX spot API — rate limits ↗huobiapi.github.ioHTX API portal ↗www.htx.com

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