Bybit real-time market data — spot, perpetual swaps and dated futures on one WebSocket feed, bought by the day
The Bybit feed across spot, perpetual swaps and dated futures — the Level-2 order book at the top 50 levels per side, a separate top-of-book stream, every trade and the derivatives topics, nothing sampled — over a plain WebSocket in JSON or SBE, captured at the venue in Tokyo and delivered at our London, Frankfurt, Ashburn or Ohio endpoints over dedicated lines, and at source at our Tokyo endpoint. You buy whole UTC calendar days for a single instrument or the whole market, self-serve, and connect with one API key.
Endpoints and one-way latency
Bybit real-time market data at our London, Frankfurt, Ashburn, Ohio or Tokyo endpoints: the data is captured at the venue in Tokyo, you connect at the endpoint. The market listens on the same port wherever it is served, and access is bought per endpoint and market.
| Endpoint | Site | Line | Latency | Buy |
|---|---|---|---|---|
| London | LD4 / AWS London | Bybit (Tokyo) → London, dedicated fiber | ~69.8 ms one-way | Bybit → |
| Frankfurt | AWS eu-central-1 | Bybit (Tokyo) → Frankfurt, dedicated fiber | ~68.2 ms one-way | Bybit → |
| Ashburn | AWS us-east-1 | Bybit (Tokyo) → Ashburn, dedicated fiber | ~67.7 ms one-way | Bybit → |
| Ohio | AWS us-east-2 | Bybit (Tokyo) → Ohio, dedicated fiber | ~64.1 ms one-way | Bybit → |
| Tokyo | AWS ap-northeast-1 | Bybit (Tokyo), same site · no line | At source | Bybit → |
Bybit lines: ~69.8 ms Tokyo → London, ~68.2 ms Tokyo → Frankfurt, ~67.7 ms Tokyo → Ashburn and ~64.1 ms Tokyo → Ohio.
Latency is one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top.
At source means the normalized feed is handed over at the site where the venue is captured — no dedicated line, so there is no line latency to quote.
What the feed carries
Every topic below is the same stream our own systems consume — the historical files in the shop are recordings of it, so a backtest maps 1:1 onto production.
| Topic | What you receive | Bybit port 14009 · London, Frankfurt, Ashburn, Ohio, Tokyo |
|---|---|---|
| Order book | Snapshot of the top 50 levels per side on subscribe, then changed levels only; every event chained by prevEventId → eventId. | ✓ |
| Top of book | Best bid and ask as its own stream; optional coalescing for slow consumers. | ✓ |
| Trades | Every public trade: aggressor side, price, quantity, trade id, exchange timestamp. | ✓ |
| Mark price | The venue's mark price as it is republished. | ✓ |
| Index price | The underlying index price. | ✓ |
| Funding rate | Current rate, next settlement time and the venue's predicted next rate. | ✓ |
| Liquidations · opt-in | Liquidation orders as the venue publishes them: side, price, quantity, exchange timestamp — off by default, opt in per subscribe. | ✓ |
- Market-data streams only — a dedicated route, not general-purpose bandwidth
- Every instrument of the market: the order book at the top 50 levels per side and every trade
- Bybit adds a separate realtime top-of-book stream
- Bybit adds mark price, index price, funding rate and liquidations
- On Bybit the topics follow the instrument type: spot carries the order book, top of book and trades; derivatives add mark price, index price and liquidations, perpetual swaps also the funding rate
- WebSocket, JSON or SBE — the port selects the market, one API key per account
How access works
One day or thirty — paid days start at the next 00:00 UTC and the rest of the purchase day is included free, so access begins the moment the order clears. Longer runs cost less per day. Extend any time from your account, invoice on checkout.
A market day unlocks every instrument of that market; an instrument day unlocks exactly the instruments you pick. €49 per instrument-day or €99 per market-day; longer runs cost less per day: €90 per market-day from 14 days, €80 from 30, €70 from 180, €60 from 365. Single Bybit instruments: spot and perpetual swaps — dated futures come with the whole market.
The key is created with your first purchase and shown in your account together with the endpoints. It authenticates the feed and the master-data export, and you can rotate it whenever you want. 3 parallel connections per key and endpoint included (one connection can subscribe to every instrument); +5 more for €10 per day, up to 28, added from your account.
WebSocket in JSON or SBE, the same protocol and subscribe flow as our documented market-data API: Bybit (port 14009). Instrument master data is a free export from the shop.
Price
€49 / instrument · day · €99 / market · day
At source: €35 / instrument · day · €69 / market · day
Captured at the venue in Tokyo and delivered at our London, Frankfurt, Ashburn or Ohio endpoints over dedicated lines, and at source at our Tokyo endpoint — over a dedicated line, that line is what the per-day price pays for; at source, the normalized feed at the venue's site. London, Frankfurt, Ashburn, Ohio and Tokyo are the self-serve locations today; more will follow, and enterprise subscriptions already cover further locations and venues. See the enterprise tiers for order entry, T+1 history and monthly API swaps.
Realtime market data for other venues
One API key, one protocol — each venue has its own page with its endpoints, line latency and price.
Questions about Bybit realtime access
Where is Bybit market data captured, and where do I connect?
Captured at the venue in Tokyo and delivered at our London, Frankfurt, Ashburn or Ohio endpoints over dedicated lines, and at source at our Tokyo endpoint. London, Frankfurt, Ashburn, Ohio and Tokyo are the endpoints serving Bybit today; more will follow, and enterprise subscriptions already cover further locations and venues — see the enterprise tiers.
How is the Bybit latency measured?
Bybit lines: ~69.8 ms Tokyo → London, ~68.2 ms Tokyo → Frankfurt, ~67.7 ms Tokyo → Ashburn and ~64.1 ms Tokyo → Ohio — one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top. The line is a dedicated route from the capture site to the endpoint, and enterprise subscriptions already cover further locations and venues — see the enterprise tiers.
Which Bybit instruments can I buy one at a time?
Single Bybit instruments: spot and perpetual swaps — dated futures come with the whole market. Dated contracts expire — the shortest-dated ones within a week — so a paid run of single-instrument days could outlive its contract; a market day covers every Bybit instrument listed that day, and you subscribe to the ones you trade.
What does Bybit realtime access cost?
€49 per instrument-day or €99 per market-day. At source — the normalized feed at the venue's site, no dedicated line — €35 per instrument-day or €69 per market-day. A market day covers every instrument of that market, an instrument day only the ones you select. Longer runs cost less per day: over a dedicated line €90 per market-day from 14 days, €80 from 30, €70 from 180, €60 from 365; at source €63, €56, €49 and €42. 3 parallel connections per key and endpoint included (one connection can subscribe to every instrument); +5 more for €10 per day, up to 28, added from your account. Realtime access is paid by card — credits apply to historical data only.
Which streams does the Bybit feed serve, and how are events identified?
Bybit serves order book, top of book, trades, mark price, index price, funding rate and liquidations. A topic a market does not carry never emits there. The order book arrives as a snapshot of the top 50 levels per side on subscribe, then every changed level within that range; the best bid and ask also arrive as their own top-of-book stream. Where a venue offers more than one order-book feed, we take the one with the lowest latency, at the depth that feed carries. On Bybit the topics follow the instrument type: spot carries the order book, top of book and trades; derivatives add mark price, index price and liquidations, perpetual swaps also the funding rate. Every order-book update carries an eventId and the prevEventId it follows. On Bybit the order book and top of book follow the venue's own sequence (eventIdType ORDERED), while trade ids are opaque (UNORDERED): compare ids for equality only, in arrival order — never sort or subtract them. A prevEventId that does not equal the last eventId you saw means data was missed: unsubscribe, subscribe again and rebuild from the fresh snapshot.
When does Bybit realtime access start and end?
Access runs over whole UTC calendar days. Paid days start at the next 00:00 UTC, and the remainder of the day you buy on is included free — there is no start date to pick. Your account lists every run and lets you extend it.
Can a coding agent implement the Bybit connection for me?
Yes — hand it the machine-readable spec: login, subscribe, message types and reconnect rules in one markdown document. Give the agent the key through the CRYPTOSTRUCT_REALTIME_API_KEY environment variable, never inside the prompt.