Feeds / Crypto exchanges (live)

Phemex

Spot (USDT pairs). A book snapshot on subscribe and again about every 60 s; between snapshots, incremental level updates (qty 0 deletes the level).

Live in productionWebSocket30 levels (Phemex default)

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 (USDT pairs)
WebSocket
wss://ws.phemex.com/
Channels
orderbook.subscribe — default book (30 levels), snapshot about every 60 s plus incremental updates
trade.subscribe — trades
Update model
A book snapshot on subscribe and again about every 60 s; between snapshots, incremental level updates (qty 0 deletes the level).
Sequencing
The sequence field is read and stored per symbol but not checked for continuity; incrementals are dropped until the symbol's first snapshot arrives.
On a gap
No gap check: the next on-stream snapshot (about every 60 s) rebuilds the book. After 30 s without data the handler reconnects and resubscribes. The book is uncrossed after every update.
Depth
30 levels (Phemex default)
Authentication
none
Heartbeat
Application-level server.ping every 5 s; WebSocket pings answered. Reconnect after 30 s without data.
Symbol format
sBTCUSDT

Subscribe message

{"id":1,"method":"orderbook.subscribe","params":["sBTCUSDT"]}

What our handler takes care of

Instruments

loading...

Official documentation

Phemex API reference — Spot WebSocket API ↗phemex-docs.github.ioPhemex public spot REST & WebSocket API (GitHub) ↗github.comPhemex API reference — rate limits ↗phemex-docs.github.io

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