Exchange Wire Formats

Bybit Futures wire format

This page shows how Bybit derivatives, linear contracts (USDT and USDC perpetuals and futures) messages become rows in our Parquet files. For each data type below, you see a real message next to the rows that we publish for it. The page also gives the source and the rule for each column. Put the pointer on a line or a column to see how they connect.

Checked against our pipeline

We recorded these messages from Bybit derivatives, linear contracts (USDT and USDC perpetuals and futures) on 2026-10-05. Our test suite replays each message through the production collector parser and the postprocessor. The test fails if the published rows are different from the rows on this page. Files that we wrote before a change to the pipeline can be different. Refer to Known Gaps & Corrections.

The collector subscribes to orderbook.50.<symbol>, publicTrade.<symbol>, tickers.<symbol> and allLiquidation.<symbol> for each linear contract that is open for trade. The ticker rows, mark price rows and open interest rows all come from the tickers topic.

  • Public WebSocket: wss://stream.bybit.com/v5/public/linear
  • REST (trade backfill): https://api.bybit.com

Exchange API reference: bybit-exchange.github.io. For the conventions that apply to all exchanges, refer to the wire formats overview.

Trades

One row for each trade from the publicTrade.<symbol> topic, and for each trade that the collector recovers from REST after a reconnect.

  • WebSocket publicTrade.<symbol>
  • REST GET /v5/market/recent-trade

Trade message

Bybit sends trades in batches. This message contains 2 trades. Each trade becomes a separate row.

WebSocket message · publicTrade.<symbol>received 2026-10-05 19:13:40.218439 UTC
{
"topic": "publicTrade.BTCUSDT",
"type": "snapshot",
"ts": 1791227620120,
"data": [
{
"T": 1791227620119,
"s": "BTCUSDT",
"S": "Buy",
"v": "0.001",
"p": "85629.30",
"L": "PlusTick",
"i": "caa63c3c-3c80-540f-8364-ea18a6824a70",
"BT": false,
"RPI": false,
"seq": 820927598403
},
{
"T": 1791227620119,
"s": "BTCUSDT",
"S": "Buy",
"v": "0.038",
"p": "85629.30",
"L": "ZeroPlusTick",
"i": "e629c952-d70a-5354-8ace-495767ec2770",
"BT": false,
"RPI": false,
"seq": 820927598404
}
]
}

Published rows · 2

received_time1791227620218439000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
event_time1791227620120tsCopied from the message ts. The time when Bybit made the push. Milliseconds. All trades in the message have the same value.
symbolBTCUSDTdata[].sCopied.
trade_id2580710057459900140data[].iBybit sends a UUID. We do not publish the UUID. The column contains a stable 64-bit hash of the UUID string. The hash is FNV-1a over the bytes of the string, with the multiplier 0x1000001b3 instead of the standard FNV prime. Then we clear the sign bit. The same UUID always gives the same ID.
price85629.30data[].pCopied as the exact decimal string that Bybit sent.
quantity0.001data[].vCopied as the exact decimal string. Base asset units.
trade_time1791227620119data[].TCopied. The time when the trade was filled. Milliseconds.
is_buyer_makerfalsedata[].Strue if the taker side S is Sell. false if it is Buy.
order_typeMarket—Always Market. This is a placeholder because Bybit does not send an order type.

REST trade backfill

Bybit does not send old trades again when you subscribe. Each time the trade connection opens or opens again, the collector downloads the latest trades from GET /v5/market/recent-trade. Then it publishes the trades that it did not receive through the WebSocket. If the trade_time of a backfilled trade is not in the hour of the file, we do not publish that trade.

Shortened: We sent this request with limit=1 to keep the example short. The collector sends limit=1000, which is the maximum that Bybit returns.

REST responsereceived 2026-10-05 19:18:35.852907 UTC
GET https://api.bybit.com/v5/market/recent-trade?category=linear&symbol=BTCUSDT&limit=1
{
"retCode": 0,
"retMsg": "OK",
"result": {
"category": "linear",
"list": [
{
"execId": "996d7ec5-7333-5567-a813-a4db019fcec2",
"symbol": "BTCUSDT",
"price": "85743.50",
"size": "0.002",
"side": "Buy",
"time": "1791227915662",
"isBlockTrade": false,
"isRPITrade": false,
"seq": "820929204227"
}
]
},
"retExtInfo": {},
"time": 1791227915757
}

Published row

received_time1791227915852907593—Our collector's clock when it received the REST response, in nanoseconds since the Unix epoch. This time is later than the trade, frequently by some seconds.
event_time1791227915662result.list[].timeThe trade time. REST responses do not have a push time. Thus, event_time is equal to trade_time on backfilled rows. Milliseconds.
symbolBTCUSDTresult.list[].symbolCopied.
trade_id5105926908505611849result.list[].execIdBybit sends a UUID. We do not publish the UUID. The column contains a stable 64-bit hash of the UUID string. The hash is FNV-1a over the bytes of the string, with the multiplier 0x1000001b3 instead of the standard FNV prime. Then we clear the sign bit. The same UUID always gives the same ID.
price85743.50result.list[].priceCopied as the exact decimal string.
quantity0.002result.list[].sizeCopied as the exact decimal string. Base asset units.
trade_time1791227915662result.list[].timeParsed from the string. Milliseconds.
is_buyer_makerfalseresult.list[].sidetrue if the taker side side is Sell. false if it is Buy.
order_typeMarket—Always Market. This is a placeholder because Bybit does not send an order type.

Notes

  • We sort the rows by trade_time, and then by the Bybit cross sequence seq.
  • We do not publish the block-trade flag BT, the RPI flag RPI, the tick direction L or seq. We publish block trades and RPI trades as normal rows.
  • If we receive a trade through the WebSocket and also through the REST backfill, we publish it one time, with the WebSocket values. On a backfilled row, event_time is equal to trade_time. The received_time can be some seconds after the trade.
  • The Bybit REST endpoint returns a maximum of the latest 1,000 trades. Thus, the collector recovers only part of a long reconnect gap on a busy contract.

For the column types and descriptions, refer to the Trades schema.

Order Book

One row for each price level from the orderbook.50.<symbol> topic. We publish each level as Bybit sent it.

  • WebSocket orderbook.50.<symbol>

Order book snapshot

Bybit sends a snapshot of the 50-level order book when the subscription starts. It also sends a snapshot after a problem on its side or after a service restart (u = 1). Each level becomes a snapshot row.

Shortened: Bybit sent 50 bid levels and 50 ask levels. The example shows the best three levels of each side.

WebSocket message · orderbook.50.<symbol>received 2026-10-05 19:13:33.813598 UTC
{
"topic": "orderbook.50.BTCUSDT",
"type": "snapshot",
"ts": 1791227613628,
"data": {
"s": "BTCUSDT",
"b": [
["85626.10", "6.857"],
["85626.00", "0.004"],
["85625.90", "0.415"]
],
"a": [
["85626.20", "1.565"],
["85626.30", "0.392"],
["85626.50", "0.001"]
],
"u": 211266072,
"seq": 820927562650
},
"cts": 1791227613626
}

Published rows · 6

received_time1791227613813598000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
event_time1791227613628tsCopied. The time when Bybit made the push. Milliseconds.
transaction_time1791227613626ctsCopied. The time of the matching engine. Milliseconds.
symbolBTCUSDTtopicThe symbol part of the topic (orderbook.50.BTCUSDT). It is equal to data.s.
event_typesnapshottypesnapshot for type: "snapshot". The message contains all levels of the 50-level order book. A message with u = 1 (Bybit service restart) is also a snapshot.
first_update_idnull—Null for snapshots.
final_update_id211266072data.uCopied. It starts a new chain. The next delta has u + 1.
prev_final_update_idnull—Null. Bybit does not send a previous update ID.
last_update_id820927562650data.seqCopied from the Bybit cross sequence seq. It gives the order of the messages, but it does not always increase by 1.
sidebiddata.bdata.abid for levels in b. ask for levels in a. One row for each level.
price85626.10data.b[][0]data.a[][0]Copied as the exact decimal string.
quantity6.857data.b[][1]data.a[][1]Copied as the exact decimal string.
order_countnull—Null. Bybit does not send order counts.

Order book delta

WebSocket message · orderbook.50.<symbol>received 2026-10-05 19:13:33.814335 UTC
{
"topic": "orderbook.50.BTCUSDT",
"type": "delta",
"ts": 1791227613708,
"data": {
"s": "BTCUSDT",
"b": [
["85619.20", "0.023"],
["85618.80", "0"]
],
"a": [
["85626.20", "1.155"],
["85635.70", "0.005"],
["85636.20", "0.003"]
],
"u": 211266074,
"seq": 820927562975
},
"cts": 1791227613706
}

Published rows · 5

received_time1791227613814335000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
event_time1791227613708tsCopied. The time when Bybit made the push. Milliseconds.
transaction_time1791227613706ctsCopied. The time of the matching engine. Milliseconds.
symbolBTCUSDTtopicThe symbol part of the topic (orderbook.50.BTCUSDT). It is equal to data.s.
event_typeupdatetypeupdate for type: "delta".
first_update_id211266074data.uCopied from u. Each delta has exactly one update ID. Thus, first_update_id = final_update_id.
final_update_id211266074data.uCopied. It is one more than the u of the previous message. A larger step is a gap.
prev_final_update_idnull—Null. Bybit does not send a previous update ID.
last_update_id820927562975data.seqCopied from the Bybit cross sequence seq. It gives the order of the messages, but it does not always increase by 1.
sidebiddata.bdata.abid for levels in b. ask for levels in a. One row for each level.
price85619.20data.b[][0]data.a[][0]Copied as the exact decimal string.
quantity0.023data.b[][1]data.a[][1]Copied as the exact decimal string. It is the new total quantity at that price. 0 removes the level.
order_countnull—Null. Bybit does not send order counts.

Notes

  • The collector subscribes only to the 50-level order book. WebSocket snapshots are the start point of this order book. The Bybit REST depth snapshots contain the update IDs of the 1,000-level stream. Thus, they cannot be a start point for this order book, and we do not publish them.
  • Before the collector writes a delta, it checks that the u of the delta is one more than the u of the previous message. After a gap, the collector connects again and starts from a new WebSocket snapshot.
  • We publish a delta with no levels as one row with side = noop, and with price and quantity = 0. Thus, the update-ID chain has no holes. Do not use these rows when you rebuild the order book.
  • A file can start with a checkpoint snapshot of the order book from the previous hour. In this snapshot, received_time is the start of the hour and transaction_time is null. final_update_id is the last u that was applied, and last_update_id is its seq.
  • Quantities are in base asset units (BTC for BTCUSDT). Bybit does not include Retail Price Improvement (RPI) orders in the order book stream.
  • Files that we wrote before the October 2026 pipeline update can also contain snapshot rows from REST depth snapshots. The update IDs of these rows are from the Bybit 1,000-level stream, and they do not continue the 50-level chain. Do not use these rows when you replay the data.

For the column types and descriptions, refer to the Order Book schema.

Ticker

One row for each tickers.<symbol> message that contains a field of the ticker row (lastPrice, prevPrice24h, price24hPcnt, highPrice24h, lowPrice24h, volume24h or turnover24h). Each row contains the full merged state.

  • WebSocket tickers.<symbol>

Ticker snapshot

Bybit sends one snapshot with all fields when the subscription starts. This snapshot publishes a ticker row, a mark price row and an open interest row. In our captures, the first snapshot was up to 2 seconds old when we received it. The deltas that Bybit sent after that time came immediately after the snapshot.

WebSocket message · tickers.<symbol>received 2026-10-05 19:19:52.187738 UTC
{
"topic": "tickers.BTCUSDT",
"type": "snapshot",
"data": {
"symbol": "BTCUSDT",
"tickDirection": "ZeroPlusTick",
"price24hPcnt": "0.004251",
"lastPrice": "85721.40",
"prevPrice24h": "85358.50",
"highPrice24h": "86986.50",
"lowPrice24h": "84907.70",
"prevPrice1h": "85436.60",
"markPrice": "85730.36",
"indexPrice": "85768.04",
"openInterest": "57163.259",
"openInterestValue": "4900626772.84",
"turnover24h": "5739447395.0800",
"volume24h": "66763.0850",
"fundingIntervalHour": "8",
"fundingCap": "0.00333",
"singleOpenInterest": "28581.63",
"singleOpenInterestValue": "2450313429.29",
"nextFundingTime": "1791244800000",
"fundingRate": "0.00001336",
"bid1Price": "85721.30",
"bid1Size": "2.542",
"ask1Price": "85721.40",
"ask1Size": "10.152",
"preOpenPrice": "",
"preQty": "",
"curPreListingPhase": ""
},
"cs": 820929695495,
"ts": 1791227990283
}

Published row

received_time1791227992187738000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
event_time1791227990283tsCopied. The time when Bybit made the push. Milliseconds.
symbolBTCUSDTdata.symbolCopied.
price_change362.90data.lastPricedata.prevPrice24hlastPrice − prevPrice24h, calculated exactly in decimal.
price_change_percent0.4251data.price24hPcntBybit sends a fraction. We multiply it by 100 exactly, thus the column is in percent. For example, 0.004251 becomes 0.4251.
weighted_average_pricenull—Null. Bybit does not send a weighted average price.
last_price85721.40data.lastPriceCopied.
last_quantitynull—Null. Bybit does not send a last trade quantity.
open_price85358.50data.prevPrice24hCopied from prevPrice24h, the price 24 hours ago.
high_price86986.50data.highPrice24hCopied.
low_price84907.70data.lowPrice24hCopied.
base_asset_volume66763.0850data.volume24hCopied. The 24h volume in base asset units.
quote_asset_volume5739447395.0800data.turnover24hCopied. The 24h turnover in quote asset units.
statistics_open_timenull—Null. Bybit does not send a statistics window.
statistics_close_timenull—Null. Bybit does not send a statistics window.
first_trade_idnull—Null. Bybit does not send trade IDs in tickers.
last_trade_idnull—Null. Bybit does not send trade IDs in tickers.
total_tradesnull—Null. Bybit does not send a trade count.

Ticker delta

A delta contains only the fields that changed. The row shows the merged state. It contains the changed fields from this delta, and the other fields from earlier messages. We replay this message after the snapshot and the 21 deltas that Bybit sent between them. Those messages prepare the state, and the example does not show their rows.

We replay 22 earlier messages (not shown) before this message. These messages set the start state for this message.

WebSocket message · tickers.<symbol>received 2026-10-05 19:19:52.975586 UTC
{
"topic": "tickers.BTCUSDT",
"type": "delta",
"data": {
"symbol": "BTCUSDT",
"tickDirection": "MinusTick",
"price24hPcnt": "0.00425",
"lastPrice": "85721.30",
"turnover24h": "5739467196.7231",
"volume24h": "66763.3160",
"bid1Price": "85721.30",
"bid1Size": "5.212"
},
"cs": 820929708680,
"ts": 1791227992883
}

Published row

received_time1791227992975586000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
event_time1791227992883tsCopied. The time when Bybit made the push. Milliseconds.
symbolBTCUSDTdata.symbolCopied.
price_change362.80data.lastPricelastPrice − prevPrice24h, calculated exactly in decimal from the merged state. prevPrice24h is not in this message, so its value comes from earlier messages.
price_change_percent0.425data.price24hPcntBybit sends a fraction. We multiply it by 100 exactly, thus the column is in percent. For example, 0.00425 becomes 0.425.
weighted_average_pricenull—Null. Bybit does not send a weighted average price.
last_price85721.30data.lastPriceCopied.
last_quantitynull—Null. Bybit does not send a last trade quantity.
open_price85358.50—Not in this message. The value comes from the snapshot and the deltas before this message.
high_price86986.50—Not in this message. The value comes from the snapshot and the deltas before this message.
low_price84907.70—Not in this message. The value comes from the snapshot and the deltas before this message.
base_asset_volume66763.3160data.volume24hCopied. The 24h volume in base asset units.
quote_asset_volume5739467196.7231data.turnover24hCopied. The 24h turnover in quote asset units.
statistics_open_timenull—Null. Bybit does not send a statistics window.
statistics_close_timenull—Null. Bybit does not send a statistics window.
first_trade_idnull—Null. Bybit does not send trade IDs in tickers.
last_trade_idnull—Null. Bybit does not send trade IDs in tickers.
total_tradesnull—Null. Bybit does not send a trade count.

Delta with no ticker field

Most deltas change only the best bid and ask (bid1Price, ask1Price and sizes). We do not publish these fields. If a delta contains no field of a data type, it publishes no row for that data type. This delta publishes no rows. We replay this message after the snapshot and the 17 deltas that Bybit sent between them. Those messages prepare the state, and the example does not show their rows.

We replay 18 earlier messages (not shown) before this message. These messages set the start state for this message.

WebSocket message · tickers.<symbol>received 2026-10-05 19:19:52.375291 UTC
{
"topic": "tickers.BTCUSDT",
"type": "delta",
"data": {
"symbol": "BTCUSDT",
"bid1Price": "85721.30",
"bid1Size": "5.835",
"ask1Price": "85721.40",
"ask1Size": "0.744"
},
"cs": 820929705226,
"ts": 1791227992283
}

Not published

received_time—Not published. This delta contains no field of the ticker row.
event_time—Not published. This delta contains no field of the ticker row.
symbol—Not published. This delta contains no field of the ticker row.
price_change—Not published. This delta contains no field of the ticker row.
price_change_percent—Not published. This delta contains no field of the ticker row.
weighted_average_price—Not published. This delta contains no field of the ticker row.
last_price—Not published. This delta contains no field of the ticker row.
last_quantity—Not published. This delta contains no field of the ticker row.
open_price—Not published. This delta contains no field of the ticker row.
high_price—Not published. This delta contains no field of the ticker row.
low_price—Not published. This delta contains no field of the ticker row.
base_asset_volume—Not published. This delta contains no field of the ticker row.
quote_asset_volume—Not published. This delta contains no field of the ticker row.
statistics_open_time—Not published. This delta contains no field of the ticker row.
statistics_close_time—Not published. This delta contains no field of the ticker row.
first_trade_id—Not published. This delta contains no field of the ticker row.
last_trade_id—Not published. This delta contains no field of the ticker row.
total_trades—Not published. This delta contains no field of the ticker row.

Notes

  • Bybit sends one snapshot message. Then it sends delta messages that contain only the fields that changed. The pipeline merges each message into the full state of the symbol and publishes the merged state. Thus, the values of unchanged fields come from earlier messages. A snapshot replaces the state.
  • The state at the end of an hour continues into the next hour. Sometimes the state of the previous hour is not available (first run, lost state, or an hour without tickers messages). Then, until the next snapshot, an hour contains only the fields from its own messages. Files from before the 2026-09 data-integrity release contain rows with only the changed fields, and nulls for unchanged fields.
  • From the 2026-09 data-integrity release, price_change_percent is in percent. Earlier files contain the Bybit fraction.

For the column types and descriptions, refer to the Ticker schema.

Mark Price

One row for each tickers.<symbol> message that contains a mark price, index price or funding field. Each row contains the full merged state.

  • WebSocket tickers.<symbol>

Ticker snapshot

Bybit sends one snapshot with all fields when the subscription starts. This snapshot publishes a ticker row, a mark price row and an open interest row. In our captures, the first snapshot was up to 2 seconds old when we received it. The deltas that Bybit sent after that time came immediately after the snapshot.

WebSocket message · tickers.<symbol>received 2026-10-05 19:19:52.187738 UTC
{
"topic": "tickers.BTCUSDT",
"type": "snapshot",
"data": {
"symbol": "BTCUSDT",
"tickDirection": "ZeroPlusTick",
"price24hPcnt": "0.004251",
"lastPrice": "85721.40",
"prevPrice24h": "85358.50",
"highPrice24h": "86986.50",
"lowPrice24h": "84907.70",
"prevPrice1h": "85436.60",
"markPrice": "85730.36",
"indexPrice": "85768.04",
"openInterest": "57163.259",
"openInterestValue": "4900626772.84",
"turnover24h": "5739447395.0800",
"volume24h": "66763.0850",
"fundingIntervalHour": "8",
"fundingCap": "0.00333",
"singleOpenInterest": "28581.63",
"singleOpenInterestValue": "2450313429.29",
"nextFundingTime": "1791244800000",
"fundingRate": "0.00001336",
"bid1Price": "85721.30",
"bid1Size": "2.542",
"ask1Price": "85721.40",
"ask1Size": "10.152",
"preOpenPrice": "",
"preQty": "",
"curPreListingPhase": ""
},
"cs": 820929695495,
"ts": 1791227990283
}

Published row

received_time1791227992187738000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
event_time1791227990283tsCopied. The time when Bybit made the push. Milliseconds.
symbolBTCUSDTdata.symbolCopied.
mark_price85730.36data.markPriceCopied.
index_price85768.04data.indexPriceCopied.
estimated_settle_pricenull—Copied from predictedDeliveryPrice. Bybit documents this field for dated futures. BTCUSDT is a perpetual, and its messages do not contain the field. Thus, the value is null.
funding_rate0.00001336data.fundingRateCopied. A fraction for each funding interval. For example, 0.0001 is 0.01 %.
next_funding_time1791244800000data.nextFundingTimeParsed from the string. Milliseconds.

Ticker delta with a new index price

Each delta with markPrice, indexPrice, fundingRate, nextFundingTime or predictedDeliveryPrice publishes a mark price row from the merged state. We replay this message after the snapshot and the 16 deltas that Bybit sent between them. Those messages prepare the state, and the example does not show their rows.

We replay 17 earlier messages (not shown) before this message. These messages set the start state for this message.

WebSocket message · tickers.<symbol>received 2026-10-05 19:19:52.275513 UTC
{
"topic": "tickers.BTCUSDT",
"type": "delta",
"data": {
"symbol": "BTCUSDT",
"indexPrice": "85768.02",
"turnover24h": "5739466939.5592",
"volume24h": "66763.3130",
"ask1Price": "85721.40",
"ask1Size": "0.740"
},
"cs": 820929704683,
"ts": 1791227992183
}

Published row

received_time1791227992275513000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
event_time1791227992183tsCopied. The time when Bybit made the push. Milliseconds.
symbolBTCUSDTdata.symbolCopied.
mark_price85730.22—Not in this message. The value comes from the snapshot and the deltas before this message.
index_price85768.02data.indexPriceCopied.
estimated_settle_pricenull—Copied from predictedDeliveryPrice. Bybit documents this field for dated futures. BTCUSDT is a perpetual, and its messages do not contain the field. Thus, the value is null.
funding_rate0.00001336—Not in this message. The value comes from the snapshot and the deltas before this message.
next_funding_time1791244800000—Not in this message. The value comes from the snapshot and the deltas before this message.

Notes

  • Bybit sends one snapshot message. Then it sends delta messages that contain only the fields that changed. The pipeline merges each message into the full state of the symbol and publishes the merged state. Thus, the values of unchanged fields come from earlier messages. A snapshot replaces the state.
  • The state at the end of an hour continues into the next hour. Sometimes the state of the previous hour is not available (first run, lost state, or an hour without tickers messages). Then, until the next snapshot, an hour contains only the fields from its own messages. Files from before the 2026-09 data-integrity release contain rows with only the changed fields, and nulls for unchanged fields.
  • The Bybit funding interval is different for each contract (fundingIntervalHour, 8 hours for BTCUSDT here). We do not publish the funding interval or the funding cap fundingCap.

For the column types and descriptions, refer to the Mark Price schema.

Open Interest

One row for each tickers.<symbol> message that contains openInterest or openInterestValue. Also, one carried-forward row at the start of each hour.

  • WebSocket tickers.<symbol>

Ticker snapshot

Bybit sends one snapshot with all fields when the subscription starts. This snapshot publishes a ticker row, a mark price row and an open interest row. In our captures, the first snapshot was up to 2 seconds old when we received it. The deltas that Bybit sent after that time came immediately after the snapshot.

WebSocket message · tickers.<symbol>received 2026-10-05 19:19:52.187738 UTC
{
"topic": "tickers.BTCUSDT",
"type": "snapshot",
"data": {
"symbol": "BTCUSDT",
"tickDirection": "ZeroPlusTick",
"price24hPcnt": "0.004251",
"lastPrice": "85721.40",
"prevPrice24h": "85358.50",
"highPrice24h": "86986.50",
"lowPrice24h": "84907.70",
"prevPrice1h": "85436.60",
"markPrice": "85730.36",
"indexPrice": "85768.04",
"openInterest": "57163.259",
"openInterestValue": "4900626772.84",
"turnover24h": "5739447395.0800",
"volume24h": "66763.0850",
"fundingIntervalHour": "8",
"fundingCap": "0.00333",
"singleOpenInterest": "28581.63",
"singleOpenInterestValue": "2450313429.29",
"nextFundingTime": "1791244800000",
"fundingRate": "0.00001336",
"bid1Price": "85721.30",
"bid1Size": "2.542",
"ask1Price": "85721.40",
"ask1Size": "10.152",
"preOpenPrice": "",
"preQty": "",
"curPreListingPhase": ""
},
"cs": 820929695495,
"ts": 1791227990283
}

Published row

received_time1791227992187738000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
symbolBTCUSDTdata.symbolCopied.
sum_open_interest57163.259data.openInterestCopied. Base asset units. The value includes both sides, as Bybit defines openInterest. We do not publish the one-sided Bybit value singleOpenInterest.
sum_open_interest_value4900626772.84data.openInterestValueCopied. Quote currency (USDT for BTCUSDT), both sides.
timestamp1791227990283tsCopied from the message ts. Milliseconds.

Ticker delta with a new open interest value

Each delta with openInterest or openInterestValue publishes an open interest row from the merged state. In this message, only the value changed (together with the mark price). Thus, sum_open_interest comes from earlier messages. We replay this message after the snapshot and the 23 deltas that Bybit sent between them. Those messages prepare the state, and the example does not show their rows.

We replay 24 earlier messages (not shown) before this message. These messages set the start state for this message.

WebSocket message · tickers.<symbol>received 2026-10-05 19:19:53.175339 UTC
{
"topic": "tickers.BTCUSDT",
"type": "delta",
"data": {
"symbol": "BTCUSDT",
"tickDirection": "ZeroPlusTick",
"markPrice": "85730.18",
"openInterestValue": "4900616483.46",
"turnover24h": "5739473711.5495",
"volume24h": "66763.3920",
"ask1Price": "85721.40",
"ask1Size": "0.668",
"singleOpenInterestValue": "2450308284.59"
},
"cs": 820929710650,
"ts": 1791227993083
}

Published row

received_time1791227993175339000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
symbolBTCUSDTdata.symbolCopied.
sum_open_interest57163.259—Not in this message. The value comes from the snapshot and the deltas before this message.
sum_open_interest_value4900616483.46data.openInterestValueCopied. Quote currency (USDT for BTCUSDT), both sides.
timestamp1791227993083tsCopied from the message ts. Milliseconds.

Hour-start carried-forward row

Each hour, each symbol with a known open interest receives a row at the start of the hour. This row contains the state at the hour boundary. The timestamp of this snapshot is just before 20:00 UTC, and we received it just after 20:00 UTC. Thus, it goes into the 20:00 file. It publishes its own row (with the timestamp 19:59), and it is also merged into the hour-start row.

WebSocket message · tickers.<symbol>received 2026-10-05 20:00:00.011956 UTC
{
"topic": "tickers.BTCUSDT",
"type": "snapshot",
"data": {
"symbol": "BTCUSDT",
"tickDirection": "PlusTick",
"price24hPcnt": "0.003552",
"lastPrice": "85688.40",
"prevPrice24h": "85385.10",
"highPrice24h": "86986.50",
"lowPrice24h": "84907.70",
"prevPrice1h": "85604.10",
"markPrice": "85684.30",
"indexPrice": "85720.48",
"openInterest": "57257.185",
"openInterestValue": "4906041816.70",
"turnover24h": "5713818688.2134",
"volume24h": "66461.5850",
"fundingIntervalHour": "8",
"fundingCap": "0.00333",
"singleOpenInterest": "28628.593",
"singleOpenInterestValue": "2453020951.19",
"nextFundingTime": "1791244800000",
"fundingRate": "0.00002009",
"bid1Price": "85688.40",
"bid1Size": "5.141",
"ask1Price": "85688.50",
"ask1Size": "0.261",
"preOpenPrice": "",
"preQty": "",
"curPreListingPhase": ""
},
"cs": 820941027667,
"ts": 1791230398283
}

Published rows · 2

received_time1791230400011956000—Our collector's clock when it received the message, in nanoseconds. The hour-start row uses the latest receive time of the messages with a timestamp before the hour that we received after the hour started. Here, that is the receive time of this message. If there is no such message, the value is the start of the hour.
symbolBTCUSDTdata.symbolCopied.
sum_open_interest57257.185data.openInterestCopied. Base asset units. The value includes both sides, as Bybit defines openInterest. We do not publish the one-sided Bybit value singleOpenInterest.
sum_open_interest_value4906041816.70data.openInterestValueCopied. Quote currency (USDT for BTCUSDT), both sides.
timestamp1791230398283tsCopied from ts for the row of the message itself. This time is before the hour. For the carried-forward row, the value is the start of the hour, 1791230400000 (20:00:00 UTC).

Notes

  • Bybit sends one snapshot message. Then it sends delta messages that contain only the fields that changed. The pipeline merges each message into the full state of the symbol and publishes the merged state. Thus, the values of unchanged fields come from earlier messages. A snapshot replaces the state.
  • The state at the end of an hour continues into the next hour. Sometimes the state of the previous hour is not available (first run, lost state, or an hour without tickers messages). Then, until the next snapshot, an hour contains only the fields from its own messages. Files from before the 2026-09 data-integrity release contain rows with only the changed fields, and nulls for unchanged fields.
  • Bybit documents openInterest and openInterestValue as both sides of the market. We do not publish the single-side values singleOpenInterest and singleOpenInterestValue.
  • In each hour with tickers messages, each symbol with a known open interest receives a row at the start of the hour, with timestamp = the hour start. Its received_time is the hour start. If a message with a timestamp before the hour arrived after the hour started, received_time is later (refer to the example). Before the October 2026 pipeline update, this row always had received_time = the hour start, and it did not include such late messages.
  • We do not publish the output of the REST poller for open interest (GET /v5/market/open-interest).

For the column types and descriptions, refer to the Open Interest schema.

Liquidations

One row for each entry of an allLiquidation.<symbol> message.

  • WebSocket allLiquidation.<symbol>

S is the side of the liquidated position. Sell means that a short position was liquidated. Thus, the published side of the liquidation order is BUY.

WebSocket message · allLiquidation.<symbol>received 2026-10-05 19:13:56.576211 UTC
{
"topic": "allLiquidation.BTCUSDT",
"type": "snapshot",
"ts": 1791227636482,
"data": [
{
"T": 1791227636066,
"s": "BTCUSDT",
"S": "Sell",
"v": "1.312",
"p": "85914.10"
}
]
}

Published row

received_time1791227636576211000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Bybit does not send this value.
event_time1791227636482tsCopied from the message ts. The time when Bybit made the push. Milliseconds.
symbolBTCUSDTdata[].sCopied.
sideBUYdata[].SChanged to the side of the liquidation order. The position side Buy (a long position was liquidated) becomes SELL. Sell becomes BUY.
order_typeMarket—Constant Market placeholder. Bybit does not send an order type.
time_in_forceIOC—Constant IOC placeholder. Bybit does not send a time in force.
quantity1.312data[].vCopied. The executed size, in base asset units.
price85914.10data[].pCopied. The bankruptcy price, not an execution price.
average_price85914.10data[].pThe bankruptcy price again. Bybit does not send an average fill price.
order_statusFILLED—Constant FILLED placeholder. Bybit does not send an order status.
last_filled_quantity1.312data[].vCopied from v. The same as quantity.
filled_quantity1.312data[].vCopied from v. The same as quantity.
trade_time1791227636066data[].TCopied. Milliseconds.

Notes

  • price and average_price both contain the bankruptcy price. order_type, time_in_force and order_status are fixed placeholders. filled_quantity and last_filled_quantity are equal to quantity.
  • data is an array. Each entry becomes a separate row. We sort the rows by trade_time. Bybit documents a push frequency of 500 ms for this topic. Bybit also states that it pushes all liquidations.

For the column types and descriptions, refer to the Liquidations schema.

If you cannot find the information that you need, tell us. We also help with integrations.

Contact support