Feeds / Crypto exchanges (live)

Bybit

Spot. WebSocket snapshot (type "snapshot"), then deltas (type "delta"); a REST snapshot is also fetched at startup.

Live in productionWebSocket200 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://stream.bybit.com/v5/public/spot
Channels
orderbook.200.<symbol> — 200-level book, snapshot then deltas, 100 ms
Update model
WebSocket snapshot (type "snapshot"), then deltas (type "delta"); a REST snapshot is also fetched at startup.
Snapshot (REST)
https://api.bybit.com/v5/market/orderbook?category=spot&symbol={SYMBOL}&limit=200
Sequencing
data.seq from each delta. Deltas that arrive before the snapshot are buffered and only those newer than the snapshot are replayed; live deltas with seq <= the last applied are dropped. No gap check.
On a gap
A new snapshot message replaces the whole book; otherwise books are rebuilt on reconnect (socket error, close, or 30 s without data; 5 s backoff, doubling), with REST snapshots re-fetched.
Depth
200 levels
Authentication
none
Heartbeat
Application-level {"op":"ping"} every 20 s, as Bybit recommends; we also answer WebSocket pings. A 30 s no-data watchdog forces a reconnect.
Symbol format
BTCUSDT

Subscribe message

{"op":"subscribe","args":["orderbook.200.BTCUSDT","orderbook.200.ETHUSDT",...]}

What our handler takes care of

Instruments

loading...

Upcoming and recent changes

2026-11-20InfoNew endpoint: Query Card List
Bybit added a new endpoint to query the Bybit card list.
Details

A new endpoint for querying the Bybit card list was added. It relates to card features, not public order book or trade data. No action is needed for market data handlers.

Our handler: Card list endpoint is an account-related feature outside the public spot orderbook channel and REST orderbook snapshot.

Source ↗

2026-11-20InfoNew endpoint: Query Card Limit
Bybit added a new endpoint to query the Bybit card limit.
Details

A new endpoint for querying the Bybit card limit was added. It relates to card features, not public order book or trade data. No action is needed for market data handlers.

Our handler: Card limit endpoint is an account-related feature outside the public spot orderbook.200 channel and /v5/market/orderbook snapshot.

Source ↗

2026-11-17InfoNew endpoint: Get Institution Connection Limit
A new REST endpoint, GET /v5/ins/connection-limit, returns JSON and SBE connection limits and current usage per dedicated endpoint.
Details

This is an additive, authenticated institutional endpoint. Our handler uses public data with no auth, so no action is needed.

Our handler: It is an institutional account endpoint (/v5/ins/connection-limit) that our public handler does not use.

Source ↗

2026-11-12InfoTrading and matching engine migrated to AWS TokyoMay affect market data
Bybit says it moved its trading and matching engine service to AWS Tokyo (apne1-az4) on 12 Nov 2026.
Details

The banner gives no endpoint or format changes. Feed latency and routing from the matching engine may differ, so check latency and sequence behaviour on the spot orderbook.200 stream and the REST snapshot. No client action is stated.

Our handler: The matching engine move could change latency for wss://stream.bybit.com/v5/public/spot orderbook data, though no change to it is announced.

Source ↗

2026-11-09InfoAuto repay settings changes (spot margin)
Set Auto Repay Mode becomes a global switch when currency is omitted, and new get/set trade auto repay endpoints are added.
Details

New endpoints are GET /v5/spot-margin-trade/get-trade-auto-repay and POST /v5/spot-margin-trade/set-trade-auto-repay. These are account settings only.

Our handler: Spot margin account settings are not part of the public orderbook feed.

Source ↗

2026-11-03InfoTokyo Dedicated Host has extra connection limit for JSON Market DataMay affect market data
The JSON market data documentation notes that the Tokyo Dedicated Host gets an extra connection limit.
Details

No details are given about the host name or limit size. If we use or plan to use a dedicated host in Tokyo, review the documented connection limits. Our current public stream host is unchanged.

Our handler: It concerns JSON market data connection limits, which could matter for our WebSocket connections, but we use the standard stream.bybit.com host.

Source ↗

Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed

Official documentation

Bybit V5 — WebSocket orderbook ↗bybit-exchange.github.ioBybit V5 — WebSocket connect (ping) ↗bybit-exchange.github.ioBybit V5 — Get orderbook (REST) ↗bybit-exchange.github.ioBybit V5 — rate limits ↗bybit-exchange.github.ioBybit V5 — changelog ↗bybit-exchange.github.io

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