Feeds / Crypto exchanges (live)
HTX (formerly Huobi)
Spot. Full book in every message; each push replaces the book.
Live in production WebSocket Up to 150 levels per side
Live now
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
Every frame is gzip-compressed and inflated before parsing. The server's ping must be echoed with the same value. One subscribe message per topic. Prices and sizes are JSON numbers, converted to fixed point.
Instruments loading...
Official documentation
Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.
Microverse Systems · feed pages describe how our handlers consume each venue's public market data.
Specifications and documentation linked here are owned by the respective exchanges and operators; we link to them and do not copy them.
Live figures come from data.microversesystems.com.