Binance Futures wire format
This page shows how Binance USDⓈ-M 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 Binance USDⓈ-M 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.
- Public WebSocket (order book, trades):
wss://fstream.binance.com/public/stream?streams=<symbol>@depth@0ms/<symbol>@trade - Market WebSocket (ticker, mark price, liquidations):
wss://fstream.binance.com/market/stream?streams=!ticker@arr/!markPrice@arr@1s/!forceOrder@arr - REST:
https://fapi.binance.com
Exchange API reference: developers.binance.com. For the conventions that apply to all exchanges, refer to the wire formats overview.
Trades
One row per trade from the <symbol>@trade stream.
- WebSocket <symbol>@trade
Trade
{"stream": "btcusdt@trade","data": {"e": "trade","E": 1791226908849,→ event_time"T": 1791226908849,→ trade_time"s": "BTCUSDT",→ symbol"t": 8148200197,→ trade_id"p": "85583.20",→ price"q": "0.064",→ quantity"X": "MARKET",→ order_type"m": true,→ is_buyer_maker"st": 1}}
Published row
true means the seller was the aggressor.MARKET if Binance does not send the field.Non-market trade (X: "NA")
Binance also sends trade events with the order type NA, and with price and quantity 0. Their trade IDs are in the same sequence as the IDs of market trades. We publish these events without changes.
{"stream": "btcusdt@trade","data": {"e": "trade","E": 1791226491521,→ event_time"T": 1791226491521,→ trade_time"s": "BTCUSDT",→ symbol"t": 8148193400,→ trade_id"p": "0",→ price"q": "0",→ quantity"X": "NA",→ order_type"m": false,→ is_buyer_maker"st": 1}}
Published row
true means the seller was the aggressor.MARKET if Binance does not send the field.Notes
- Rows with
order_typeNAhavepriceandquantity0. Remove these rows before you calculate volume, VWAP or price statistics. Keep them if you usetrade_idto find gaps.
For the column types and descriptions, refer to the Trades schema.
Order Book
One row per price level. Updates come from the <symbol>@depth@0ms stream. REST snapshots set the initial state of the order book.
- WebSocket <symbol>@depth@0ms
- REST GET /fapi/v1/depth
Depth update
Shortened: Binance sent 14 bid levels and 8 ask levels in this message. This example shows the two highest bids and the three lowest asks.
{"stream": "btcusdt@depth@0ms","data": {"e": "depthUpdate",→ event_type"E": 1791226898196,→ event_time"T": 1791226898194,→ transaction_time"s": "BTCUSDT",→ symbol"ps": "BTCUSDT","U": 11742309239582,→ first_update_id"u": 11742309241602,→ final_update_id"pu": 11742309239523,→ prev_final_update_id"b": [→ side["85547.70", "0.020"],→ side · price · quantity["85580.30", "0.355"]→ side · price · quantity],"a": [→ side["85601.90", "2.784"],→ side · price · quantity["85605.10", "0.001"],→ side · price · quantity["85723.10", "0.000"]→ side · price · quantity],"st": 1}}
Published rows · 5
update for every depthUpdate message.u of the previous message. A different value shows a gap.bid for levels in b, ask for levels in a. One row per level.0.000 removes the level.REST depth snapshot
The collector requests a REST snapshot when it connects. It also requests one after a sequence gap, when it must reset its order book. We publish only the snapshots that the collector applied to its order book. Each level becomes one snapshot row.
Shortened: We requested this example with limit=5 to keep it short. The collector requests limit=500, or limit=100 when it resets many order books at the same time.
{"lastUpdateId": 11742279126574,→ final_update_id · last_update_id"E": 1791226529372,→ event_time"T": 1791226529369,→ transaction_time"bids": [→ side["85583.10", "4.900"],→ side · price · quantity["85583.00", "0.016"],→ side · price · quantity["85582.90", "0.002"],→ side · price · quantity["85582.50", "0.001"],→ side · price · quantity["85582.40", "0.002"]→ side · price · quantity],"asks": [→ side["85583.20", "5.022"],→ side · price · quantity["85583.30", "0.003"],→ side · price · quantity["85583.40", "0.060"],→ side · price · quantity["85583.50", "0.006"],→ side · price · quantity["85583.70", "0.002"]→ side · price · quantity]}
Published rows · 10
snapshot for every REST snapshot.first_update_id ≤ this value ≤ final_update_id, or that has prev_final_update_id equal to this value.bid for levels in bids, ask for levels in asks. One row per level.Notes
- We do not publish an update row if its
final_update_idequals thelastUpdateIdof a snapshot in the same hour. The snapshot already contains these updates. - A depth update with no levels becomes one row with
sidenoop, and withpriceandquantity0. This row contains the update IDs and does not change the order book. An empty REST snapshot becomes onenoopsnapshotrow. When you replay this row, clear the order book. - REST snapshots usually contain 500 levels per side. When the collector resets many order books at the same time, the snapshots contain 100 levels per side. Levels outside a snapshot are unknown until an update changes them.
- Binance can send a removal (quantity
0) for a level that is not in the order book. The Binance documentation says that this is normal. Ignore the removal when you replay. - A file can start with a checkpoint. A checkpoint is the order book that we replayed up to the hour boundary, as
snapshotrows. These rows havereceived_timeat the start of the hour and theevent_timeof the last exchange event before that time. Theirtransaction_timeis null. Theirfinal_update_idandlast_update_idcontain the last update ID that we applied. We write a checkpoint only after we make sure that the order book is current. If a file has no checkpoint, continue from the order book of the previous hour or wait for the next snapshot.
For the column types and descriptions, refer to the Order Book schema.
Ticker
One row per entry of each !ticker@arr frame. Binance includes only the symbols whose statistics changed, at most once per second.
- WebSocket !ticker@arr
Shortened: The all-market frame contained 185 tickers. This example shows only BTCUSDT. Each entry becomes its own row.
{"stream": "!ticker@arr","data": [{"e": "24hrTicker","E": 1791226905514,→ event_time"s": "BTCUSDT",→ symbol"ps": "BTCUSDT","p": "283.20",→ price_change"P": "0.332",→ price_change_percent"w": "85961.44",→ weighted_average_price"c": "85583.20",→ last_price"Q": "0.033",→ last_quantity"o": "85300.00",→ open_price"h": "86976.10",→ high_price"l": "84910.00",→ low_price"v": "175409.143",→ base_asset_volume"q": "15078422443.55",→ quote_asset_volume"O": 1791140460000,→ statistics_open_time"C": 1791226905514,→ statistics_close_time"F": 8144678472,→ first_trade_id"L": 8148200173,→ last_trade_id"n": 3507274,→ total_trades"st": 1}]}
Published row
0.332 means +0.332 %.Notes
- A symbol with no change in its statistics gets no row for that second. Continue to use the last row for that symbol.
- We publish only the symbols that USDⓈ-M
exchangeInfolists. The all-market streams of Binance also contain COIN-M contracts (for exampleBTCUSD_PERP) and delisted symbols. We remove their rows. Before the 2026-09 data-integrity release, we published these rows.
For the column types and descriptions, refer to the Ticker schema.
Mark Price
One row per symbol per !markPrice@arr@1s frame, about one per second.
- WebSocket !markPrice@arr@1s
Shortened: The all-market frame contained 745 symbols. This example shows only BTCUSDT. Each entry becomes its own row.
{"stream": "!markPrice@arr@1s","data": [{"e": "markPriceUpdate","E": 1791226902000,→ event_time"s": "BTCUSDT",→ symbol"p": "85583.30000000",→ mark_price"ap": "85583.30000000","P": "85612.13024722",→ estimated_settle_price"i": "85633.04043478",→ index_price"r": "0.00000563",→ funding_rate"T": 1791244800000,→ next_funding_time"st": 1}]}
Published row
0.00000563 is 0.000563 %.Notes
- We publish only the symbols that USDⓈ-M
exchangeInfolists. The all-market streams of Binance also contain COIN-M contracts (for exampleBTCUSD_PERP) and delisted symbols. We remove their rows. Before the 2026-09 data-integrity release, we published these rows.
For the column types and descriptions, refer to the Mark Price schema.
Open Interest
One row per 5-minute open interest point from REST polls.
- REST GET /futures/data/openInterestHist
The USDⓈ-M WebSocket streams of Binance do not include open interest. The collector polls the history of 5-minute open interest every 5 minutes. We publish each point one time, in the hour of the first poll that returned it.
Shortened: We requested this example with limit=3 to keep it short. The collector requests limit=500.
[{"symbol": "BTCUSDT",→ symbol"sumOpenInterest": "95006.41500000",→ sum_open_interest"sumOpenInterestValue": "8130409421.87865450",→ sum_open_interest_value"CMCCirculatingSupply": "20093487.00000000","timestamp": 1791225600000→ timestamp},{"symbol": "BTCUSDT",→ symbol"sumOpenInterest": "94973.61800000",→ sum_open_interest"sumOpenInterestValue": "8127186910.47580000",→ sum_open_interest_value"CMCCirculatingSupply": "20093487.00000000","timestamp": 1791225900000→ timestamp},{"symbol": "BTCUSDT",→ symbol"sumOpenInterest": "94930.31000000",→ sum_open_interest"sumOpenInterestValue": "8122474649.37500000",→ sum_open_interest_value"CMCCirculatingSupply": "20093487.00000000","timestamp": 1791226200000→ timestamp}]
Published rows · 3
Notes
- Each poll returns up to 500 points (about 41 hours). After a pause in the polls, the file of the next hour contains the points that no earlier hour published. Thus,
timestampcan be hours beforereceived_time.
For the column types and descriptions, refer to the Open Interest schema.
Liquidations
One row per forceOrder event on the !forceOrder@arr stream.
- WebSocket !forceOrder@arr
{"stream": "!forceOrder@arr","data": {"e": "forceOrder","E": 1791226913155,→ event_time"o": {"s": "RLCUSDT",→ symbol"S": "BUY",→ side"o": "LIMIT",→ order_type"f": "IOC",→ time_in_force"q": "809.3",→ quantity"p": "0.7135",→ price"ap": "0.7048",→ average_price"X": "FILLED",→ order_status"l": "0.8",→ last_filled_quantity"z": "809.3",→ filled_quantity"T": 1791226913110,→ trade_time"ps": "RLCUSDT","st": 1}}}
Published row
BUY closes a liquidated short position. SELL closes a liquidated long position.Notes
- Binance sends at most one liquidation per symbol per 1,000 ms. Thus, the rows are a sample and do not include every liquidation. Counts and totals are a lower bound.
- We publish only the symbols that USDⓈ-M
exchangeInfolists. The all-market streams of Binance also contain COIN-M contracts (for exampleBTCUSD_PERP) and delisted symbols. We remove their rows. Before the 2026-09 data-integrity release, we published these rows.
For the column types and descriptions, refer to the Liquidations schema.