Aster Futures wire format
This page shows how Aster Perpetual 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 Aster Perpetual 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 market data API of Aster uses the message formats of Binance USDⓈ-M Futures, and the conversions are the same. The Aster documentation does not list the <symbol>@trade and <symbol>@depth@0ms streams that the collector subscribes to. Both streams send trade and depthUpdate events in the Binance format.
- Trades WebSocket:
wss://fstream.asterdex.com/stream?streams=<symbol>@trade/… - Depth WebSocket:
wss://fstream.asterdex.com/stream?streams=<symbol>@depth@0ms/… - Ticker WebSocket:
wss://fstream.asterdex.com/stream?streams=!ticker@arr - Mark price WebSocket:
wss://fstream.asterdex.com/stream?streams=!markPrice@arr@1s - Liquidations WebSocket:
wss://fstream.asterdex.com/stream?streams=!forceOrder@arr - REST:
https://fapi.asterdex.com
Exchange API reference: github.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
{"stream": "btcusdt@trade","data": {"e": "trade","E": 1791227773292,→ event_time"T": 1791227773250,→ trade_time"s": "BTCUSDT",→ symbol"t": 148500896,→ trade_id"p": "85600.9",→ price"q": "0.002",→ quantity"X": "MARKET",→ order_type"m": false→ is_buyer_maker}}
Published row
true means the seller was the aggressor.MARKET if Aster does not send the field.Notes
- We remove trades with a zero or negative
quantityand do not publish them.
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
{"stream": "btcusdt@depth@0ms","data": {"e": "depthUpdate",→ event_type"E": 1791227773380,→ event_time"T": 1791227773350,→ transaction_time"s": "BTCUSDT",→ symbol"U": 585621556224,→ first_update_id"u": 585621557091,→ final_update_id"pu": 585621555794,→ prev_final_update_id"b": [→ side["85590.6", "4.298"]→ side · price · quantity],"a": [→ side["85599.7", "0.000"],→ side · price · quantity["85604.3", "6.949"],→ side · price · quantity["85648.6", "0.000"]→ side · price · quantity]}}
Published rows · 4
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.
{"lastUpdateId": 585621541676,→ final_update_id · last_update_id"E": 1791227772674,→ event_time"T": 1791227772650,→ transaction_time"bids": [→ side["85600.8", "0.109"],→ side · price · quantity["85599.6", "0.058"],→ side · price · quantity["85594.3", "0.025"],→ side · price · quantity["85594.2", "0.263"],→ side · price · quantity["85594.1", "0.722"]→ side · price · quantity],"asks": [→ side["85600.9", "0.963"],→ side · price · quantity["85604.0", "0.125"],→ side · price · quantity["85604.1", "0.025"],→ side · price · quantity["85604.2", "6.206"],→ side · price · quantity["85604.3", "6.949"]→ 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
- Aster can send a removal (quantity
0) for a level that is not in the order book. The Aster documentation says that this is normal. Ignore the removal when you replay. - 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. - 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 symbol whose statistics changed, from the !ticker@arr stream, at most one per symbol per second.
- WebSocket !ticker@arr
The all-market frame contains only the tickers that changed in the last second. This frame contained 2. Each entry becomes its own row.
{"stream": "!ticker@arr","data": [{"e": "24hrTicker","E": 1791227773292,→ event_time"s": "BTCUSDT",→ symbol"p": "254.9",→ price_change"P": "0.299",→ price_change_percent"w": "85953.6",→ weighted_average_price"c": "85600.9",→ last_price"Q": "0.002",→ last_quantity"o": "85346.0",→ open_price"h": "86964.9",→ high_price"l": "84942.4",→ low_price"v": "7310.230",→ base_asset_volume"q": "628340740.71",→ quote_asset_volume"O": 1791141360000,→ statistics_open_time"C": 1791227773250,→ statistics_close_time"F": 148456821,→ first_trade_id"L": 148500896,→ last_trade_id"n": 44075→ total_trades},{"e": "24hrTicker","E": 1791227772893,→ event_time"s": "TRADOORUSDT",→ symbol"p": "0.0106000",→ price_change"P": "1.529",→ price_change_percent"w": "0.6992235",→ weighted_average_price"c": "0.7038000",→ last_price"Q": "1",→ last_quantity"o": "0.6932000",→ open_price"h": "0.7055000",→ high_price"l": "0.6880000",→ low_price"v": "87356",→ base_asset_volume"q": "61081.3700000",→ quote_asset_volume"O": 1791147960000,→ statistics_open_time"C": 1791227772850,→ statistics_close_time"F": 384877,→ first_trade_id"L": 385481,→ last_trade_id"n": 605→ total_trades}]}
Published rows · 2
0.299 means +0.299 %.Notes
- A symbol with no change in its statistics gets no row for that second. Continue to use the last row for that symbol.
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 771 symbols. This example shows only BTCUSDT. Each entry becomes its own row.
{"stream": "!markPrice@arr@1s","data": [{"e": "markPriceUpdate","E": 1791227773000,→ event_time"s": "BTCUSDT",→ symbol"p": "85606.06731160",→ mark_price"P": "85585.57423237",→ estimated_settle_price"i": "85630.89804348",→ index_price"r": "0.00006494",→ funding_rate"T": 1791244800000→ next_funding_time}]}
Published row
0.00006494 is 0.006494 %.For the column types and descriptions, refer to the Mark Price schema.
Liquidations
One row per forceOrder event on the !forceOrder@arr stream.
- WebSocket !forceOrder@arr
{"stream": "!forceOrder@arr","data": {"e": "forceOrder","E": 1791228276231,→ event_time"o": {"s": "PAIDUSDT",→ symbol"S": "SELL",→ side"o": "LIMIT",→ order_type"f": "IOC",→ time_in_force"q": "14270",→ quantity"p": "0.0037107",→ price"ap": "0.0040600",→ average_price"X": "FILLED",→ order_status"l": "14270",→ last_filled_quantity"z": "14270",→ filled_quantity"T": 1791228276200→ trade_time}}}
Published row
BUY closes a liquidated short position. SELL closes a liquidated long position.Notes
- Aster sends at most one liquidation per symbol per 1,000 ms: the latest in each window. Thus, the rows are a sample and do not include every liquidation. Counts and totals are a lower bound.
For the column types and descriptions, refer to the Liquidations schema.
Not published
- Open Interest: The collector does not poll the open interest of Aster, so we do not publish open interest files.