Bitget Futures wire format
This page shows how Bitget USDT-M, USDC-M and Coin-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 Bitget USDT-M, USDC-M and Coin-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.
The collector subscribes to the books, trade and ticker channels for every tradable contract of these product types: USDT-FUTURES, USDC-FUTURES (for example BTCPERP) and COIN-FUTURES. It also subscribes to the liquidation topic one time for each product type. The examples use BTCUSDT. The collector does not use REST polls. Open interest and mark prices come from the ticker channel.
- Public WebSocket V2 (order book, trades, ticker):
wss://ws.bitget.com/v2/ws/public - Public WebSocket V3 (liquidations):
wss://ws.bitget.com/v3/ws/public
Exchange API reference: www.bitget.com. For the conventions that apply to all exchanges, refer to the wire formats overview.
Trades
One row per trade from the trade channel.
- WebSocket trade
Trade snapshot after subscription
Immediately after the collector subscribes, Bitget sends the recent trades again as one snapshot message, newest first. We publish them like all other trades, with the oldest trade first. We remove the trades that we already published in an earlier hour, or earlier in the same hour.
Shortened: The snapshot contained the 50 most recent trades. This example shows the newest three.
{"action": "snapshot","arg": {"instType": "USDT-FUTURES","channel": "trade","instId": "BTCUSDT"→ symbol},"data": [{"ts": "1791227481512",→ event_time · trade_time"price": "85599.9",→ price"size": "0.2581",→ quantity"side": "buy",→ is_buyer_maker"tradeId": "1491081618619383808"→ trade_id},{"ts": "1791227480460",→ event_time · trade_time"price": "85599.9",→ price"size": "0.209",→ quantity"side": "buy",→ is_buyer_maker"tradeId": "1491081614206976018"→ trade_id},{"ts": "1791227480460",→ event_time · trade_time"price": "85599.9",→ price"size": "0.0001",→ quantity"side": "buy",→ is_buyer_maker"tradeId": "1491081614206976016"→ trade_id}],"ts": 1791227482003}
Published rows · 3
data[].ts, not from the envelope ts. Milliseconds.event_time.true when the taker side (side) is sell. false when it is buy.MARKET. Bitget does not send an order type, so this value is a placeholder.Trade update
Later messages contain only new trades. One message can contain several trades, newest first. Each trade becomes its own row.
{"action": "update","arg": {"instType": "USDT-FUTURES","channel": "trade","instId": "BTCUSDT"→ symbol},"data": [{"ts": "1791227487186",→ event_time · trade_time"price": "85599.8",→ price"size": "0.0027",→ quantity"side": "sell",→ is_buyer_maker"tradeId": "1491081642417864704"→ trade_id}],"ts": 1791227487186}
Published row
data[].ts, not from the envelope ts. Milliseconds.event_time.true when the taker side (side) is sell. false when it is buy.MARKET. Bitget does not send an order type, so this value is a placeholder.Notes
- The Bitget
sideis the side of the taker. Bitget does not send an order type, soorder_typeis alwaysMARKET. Useis_buyer_makerfor the aggressor side. - Trade IDs increase over time, but they are not consecutive. Do not use gaps in
trade_idto find trades that the collector did not receive.
For the column types and descriptions, refer to the Trades schema.
Order Book
One row per price level from the books channel. The channel sends a snapshot after the collector subscribes, then incremental updates.
- WebSocket books
Order book snapshot
The first books message after the collector subscribes (and after each reconnection) is a snapshot of the order book. Each level becomes one snapshot row.
Shortened: Bitget sent 500 bid levels and 500 ask levels in this snapshot. This example shows the best three of each.
{"action": "snapshot",→ event_type"arg": {"instType": "USDT-FUTURES","channel": "books","instId": "BTCUSDT"→ symbol},"data": [{"asks": [→ side["85599.9", "0.5811"],→ side · price · quantity["85600", "0.1907"],→ side · price · quantity["85601.9", "0.0002"]→ side · price · quantity],"bids": [→ side["85599.8", "3.4111"],→ side · price · quantity["85599.7", "0.0598"],→ side · price · quantity["85599.2", "0.2628"]→ side · price · quantity],"ts": "1791227482002",→ transaction_time"seq": 1062970931190,→ final_update_id"pseq": 0}],"ts": 1791227482021→ event_time}
Published rows · 6
ts, Bitget's push time. Milliseconds.data[].ts, the matching-engine time. Milliseconds.snapshot when action is snapshot.seq chain. Bitget sends pseq 0 with snapshots.bid for levels in bids, ask for levels in asks. One row per level.books channel does not send order counts.Order book update
The first update after the snapshot above. Its pseq equals the seq of the snapshot, so the sequence chain has no break.
Shortened: Bitget sent 8 bid levels and 17 ask levels in this update. This example shows the first 2 bid levels and the first 3 ask levels.
{"action": "update",→ event_type"arg": {"instType": "USDT-FUTURES","channel": "books","instId": "BTCUSDT"→ symbol},"data": [{"asks": [→ side["85602.2", "0"],→ side · price · quantity["85603.7", "0.0001"],→ side · price · quantity["85603.8", "0.0808"]→ side · price · quantity],"bids": [→ side["85599.8", "3.8911"],→ side · price · quantity["85599.7", "0.0597"]→ side · price · quantity],"ts": "1791227482100",→ transaction_time"seq": 1062970936888,→ final_update_id"pseq": 1062970931190→ prev_final_update_id}],"ts": 1791227482103→ event_time}
Published rows · 5
ts, Bitget's push time. Milliseconds.data[].ts, the matching-engine time. Milliseconds.update when action is update.seq of the previous push on this subscription. If it is different from the final_update_id of the previous message, there is a gap. All rows of one message have the same value. Thus, check it one time per message, not per row.bid for levels in bids, ask for levels in asks. One row per level.0 removes the level.books channel does not send order counts.Notes
- From the October 2026 pipeline update,
transaction_timecontains the matching-engine time. In files that we wrote before this update, it is null. In all files,event_timeis the push time. - The
prev_final_update_id(pseq) of each update equals thefinal_update_id(seq) of the previous message. A different value shows a lost message. If this occurs, start again from the next snapshot. - We publish a message with no bid levels and no ask levels as one row with
sidenoop,price0andquantity0. Thus, theseqchain stays complete. Anoopupdate does not change a level. Anoopsnapshot means that the order book is empty. When you replay it, clear your order book. - A file can start with a checkpoint snapshot of the order book that we kept from the previous hour. Its
received_timeis the start of the hour, and itstransaction_timeis null. Itsfinal_update_idandlast_update_idboth contain theseqof the last message that we applied. Theprev_final_update_idof the next update links to this checkpoint.
For the column types and descriptions, refer to the Order Book schema.
Ticker
One row per ticker push.
- WebSocket ticker
{"action": "snapshot","arg": {"instType": "USDT-FUTURES","channel": "ticker","instId": "BTCUSDT"},"data": [{"instId": "BTCUSDT",→ symbol"lastPr": "85599.9",→ last_price"bidPr": "85599.8","askPr": "85599.9","bidSz": "4.0378","askSz": "0.4618","open24h": "85345.7",→ open_price"high24h": "86966.9",→ high_price"low24h": "84929.5",→ low_price"change24h": "0.00298",→ price_change_percent"fundingRate": "0.000063","nextFundingTime": "1791244800000","markPrice": "85599.9","indexPrice": "85636.34","holdingAmount": "31506.4859999999786","baseVolume": "41733.57",→ base_asset_volume"quoteVolume": "3588373746.3737",→ quote_asset_volume"openUtc": "86473.2","symbolType": "1","symbol": "BTCUSDT","ts": "1791227481990"}],"ts": 1791227481991→ event_time}
Published row
ts, Bitget's push time. Milliseconds.change24h multiplied by 100. Bitget sends a fraction (0.01 is 1 %). The column is in percent.Notes
- From the October 2026 pipeline update,
price_change_percentis in percent. Files that we wrote before this update contain the Bitget fraction without changes (0.01for 1 %). Multiply those values by 100. - We do not publish the best bid and ask of the ticker (
bidPr,askPr,bidSz,askSz) oropenUtc. Mark price, index price and funding go tomark_price. Open interest goes toopen_interest.
For the column types and descriptions, refer to the Ticker schema.
Mark Price
One row per futures ticker push, from the mark price, index price and funding fields of the ticker. The collector does not subscribe to a separate mark price channel.
- WebSocket ticker
The same ticker message as on the ticker page. Every futures ticker push also becomes one mark price row.
{"action": "snapshot","arg": {"instType": "USDT-FUTURES","channel": "ticker","instId": "BTCUSDT"},"data": [{"instId": "BTCUSDT",→ symbol"lastPr": "85599.9","bidPr": "85599.8","askPr": "85599.9","bidSz": "4.0378","askSz": "0.4618","open24h": "85345.7","high24h": "86966.9","low24h": "84929.5","change24h": "0.00298","fundingRate": "0.000063",→ funding_rate"nextFundingTime": "1791244800000",→ next_funding_time"markPrice": "85599.9",→ mark_price"indexPrice": "85636.34",→ index_price"holdingAmount": "31506.4859999999786","baseVolume": "41733.57","quoteVolume": "3588373746.3737","openUtc": "86473.2","symbolType": "1","symbol": "BTCUSDT","ts": "1791227481990"}],"ts": 1791227481991→ event_time}
Published row
ts, Bitget's push time. Milliseconds.deliveryPrice when the push contains it. Bitget documents this field for delivery contracts, and sends it from one hour before delivery. Null here, because this perpetual ticker has no deliveryPrice field.0.000063 is 0.0063 %.For the column types and descriptions, refer to the Mark Price schema.
Open Interest
One row per ticker push, from the ticker's holdingAmount. There is no REST poll.
- WebSocket ticker
The same ticker message again. Every futures ticker push also becomes one open interest row.
{"action": "snapshot","arg": {"instType": "USDT-FUTURES","channel": "ticker","instId": "BTCUSDT"},"data": [{"instId": "BTCUSDT",→ symbol"lastPr": "85599.9","bidPr": "85599.8","askPr": "85599.9","bidSz": "4.0378","askSz": "0.4618","open24h": "85345.7","high24h": "86966.9","low24h": "84929.5","change24h": "0.00298","fundingRate": "0.000063","nextFundingTime": "1791244800000","markPrice": "85599.9",→ sum_open_interest_value"indexPrice": "85636.34","holdingAmount": "31506.4859999999786",→ sum_open_interest · sum_open_interest_value"baseVolume": "41733.57","quoteVolume": "3588373746.3737","openUtc": "86473.2","symbolType": "1","symbol": "BTCUSDT","ts": "1791227481990"→ timestamp}],"ts": 1791227481991}
Published row
…9999786). Base asset units.holdingAmount × markPrice, computed in exact decimal and rounded to 8 decimal places. Quote currency (USDT for USDT-margined contracts, USDC for USDC-margined contracts, USD for coin-margined contracts). Null if the push does not contain one of the two fields.data[].ts, Bitget's data time. Milliseconds.Notes
- Rows repeat at the rate of the ticker, even when open interest does not change.
sum_open_interest_valuewas empty before the 2026-09 data-integrity release.
For the column types and descriptions, refer to the Open Interest schema.
Liquidations
One row per entry of the V3 liquidation topic. The collector subscribes to this topic one time for each product type (usdt-futures, usdc-futures, coin-futures).
- WebSocket liquidation
No BTCUSDT liquidation arrived during our capture, so this example is for ZECUSDT. The sell side means that a short position was liquidated.
{"action": "update","arg": {"instType": "usdt-futures","topic": "liquidation"},"data": [{"symbol": "ZECUSDT",→ symbol"side": "sell",→ side"price": "1348.598068598069",→ quantity · price · average_price · last_filled_quantity · filled_quantity"amount": "775.443889443889",→ quantity · last_filled_quantity · filled_quantity"ts": "1791227617704"→ event_time · trade_time}],"ts": 1791227617724}
Published row
data[].ts. Milliseconds.buy (a long position was liquidated) becomes SELL. sell (a short position was liquidated) becomes BUY.Market. This value is a placeholder, because Bitget does not send an order type.IOC. This value is a placeholder, because Bitget does not send a time in force.amount ÷ price, computed in exact decimal and rounded to 6 decimal places. Base asset units. Bitget sends amount in quote currency.price. Bitget does not send an average fill price.FILLED. This value is a placeholder, because Bitget does not send an order status.quantity.quantity.event_time.Notes
- Bitget sends liquidations one time per second. Each second, it sends at most one record per symbol and position side: the largest record. The rows are a sample that the exchange selects, and do not include every liquidation. Thus, counts and totals are a lower bound.
- We do not publish an entry without a positive
priceandamount, because it has no valid base quantity. Before the October 2026 pipeline update, we published such an entry with the quoteamountas its quantity.
For the column types and descriptions, refer to the Liquidations schema.