Bitget Spot wire format
This page shows how Bitget Spot 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 Spot 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 with instType SPOT for every online spot pair that Bitget does not restrict by region (areaSymbol no). The examples use BTCUSDT. The messages and the conversion are the same as for Bitget Futures.
- Public WebSocket V2 (order book, trades, ticker):
wss://ws.bitget.com/v2/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": "SPOT","channel": "trade","instId": "BTCUSDT"→ symbol},"data": [{"ts": "1791227477947",→ event_time · trade_time"price": "85640.81",→ price"size": "0.000167",→ quantity"side": "sell",→ is_buyer_maker"tradeId": "1491081603666657280"→ trade_id},{"ts": "1791227476436",→ event_time · trade_time"price": "85640.82",→ price"size": "0.000292",→ quantity"side": "buy",→ is_buyer_maker"tradeId": "1491081597329063936"→ trade_id},{"ts": "1791227476429",→ event_time · trade_time"price": "85638.99",→ price"size": "0.000292",→ quantity"side": "buy",→ is_buyer_maker"tradeId": "1491081597299703808"→ trade_id}],"ts": 1791227482019}
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": "SPOT","channel": "trade","instId": "BTCUSDT"→ symbol},"data": [{"ts": "1791227494878",→ event_time · trade_time"price": "85639.46",→ price"size": "0.000583",→ quantity"side": "sell",→ is_buyer_maker"tradeId": "1491081674680418304"→ trade_id}],"ts": 1791227494879}
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": "SPOT","channel": "books","instId": "BTCUSDT"→ symbol},"data": [{"asks": [→ side["85639.47", "0.329203"],→ side · price · quantity["85643.99", "0.000527"],→ side · price · quantity["85644", "0.000527"]→ side · price · quantity],"bids": [→ side["85639.46", "0.316465"],→ side · price · quantity["85638.38", "0.00253"],→ side · price · quantity["85638.37", "0.060218"]→ side · price · quantity],"ts": "1791227481900",→ transaction_time"seq": 885104208381,→ final_update_id"pseq": 0}],"ts": 1791227481952→ 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 no bid levels and 9 ask levels in this update. This example shows 3 of the ask levels.
{"action": "update",→ event_type"arg": {"instType": "SPOT","channel": "books","instId": "BTCUSDT"→ symbol},"data": [{"asks": [→ side["85645.91", "0"],→ side · price · quantity["85666.66", "0.233691"],→ side · price · quantity["85679.99", "0.233541"]→ side · price · quantity],"bids": [],→ side"ts": "1791227482000",→ transaction_time"seq": 885104210890,→ final_update_id"pseq": 885104208381→ prev_final_update_id}],"ts": 1791227482001→ event_time}
Published rows · 3
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. The Bitget spot documentation does not listpseq, but the spotbookschannel sends it. Rows from messages withoutpseqhave a nullprev_final_update_id. - 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": "SPOT","channel": "ticker","instId": "BTCUSDT"},"data": [{"instId": "BTCUSDT",→ symbol"lastPr": "85640.81",→ last_price"open24h": "85265.09",→ open_price"high24h": "86993.9",→ high_price"low24h": "84980.62",→ low_price"change24h": "0.00301",→ price_change_percent"bidPr": "85639.46","askPr": "85639.47","bidSz": "0.310626","askSz": "0.507108","baseVolume": "2723.070875",→ base_asset_volume"quoteVolume": "234243302.169137",→ quote_asset_volume"openUtc": "86511.00","changeUtc24h": "-0.01006","ts": "1791227482089"}],"ts": 1791227482092→ 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),openUtcorchangeUtc24h.
For the column types and descriptions, refer to the Ticker schema.
Not published
- Mark Price: Spot markets have no mark price. We published empty
mark_pricefiles from 2025-07-15 to 2026-09-20. We plan to remove these files. - Open Interest: Spot markets have no open interest. We published empty
open_interestfiles from 2025-07-15 to 2026-09-20. We plan to remove these files. - Liquidations: Bitget does not publish a spot liquidation feed. Its
liquidationtopic covers only the futures product types.