Exchange Wire Formats

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
WebSocket message · <symbol>@tradereceived 2026-10-05 19:16:13.423571 UTC
{
"stream": "btcusdt@trade",
"data": {
"e": "trade",
"E": 1791227773292,
"T": 1791227773250,
"s": "BTCUSDT",
"t": 148500896,
"p": "85600.9",
"q": "0.002",
"X": "MARKET",
"m": false
}
}

Published row

received_time1791227773423571000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Aster does not send this value.
event_time1791227773292data.ECopied. Milliseconds.
symbolBTCUSDTdata.sCopied.
trade_id148500896data.tCopied.
price85600.9data.pCopied as the exact decimal string that Aster sent.
quantity0.002data.qCopied as the exact decimal string. Base asset units.
trade_time1791227773250data.TCopied. Milliseconds.
is_buyer_makerfalsedata.mCopied. true means the seller was the aggressor.
order_typeMARKETdata.XCopied. MARKET if Aster does not send the field.

Notes

  • We remove trades with a zero or negative quantity and 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

WebSocket message · <symbol>@depth@0msreceived 2026-10-05 19:16:13.512476 UTC
{
"stream": "btcusdt@depth@0ms",
"data": {
"e": "depthUpdate",
"E": 1791227773380,
"T": 1791227773350,
"s": "BTCUSDT",
"U": 585621556224,
"u": 585621557091,
"pu": 585621555794,
"b": [
["85590.6", "4.298"]
],
"a": [
["85599.7", "0.000"],
["85604.3", "6.949"],
["85648.6", "0.000"]
]
}
}

Published rows · 4

received_time1791227773512476000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Aster does not send this value.
event_time1791227773380data.ECopied. Milliseconds.
transaction_time1791227773350data.TCopied. Milliseconds.
symbolBTCUSDTdata.sCopied.
event_typeupdatedata.eupdate for every depthUpdate message.
first_update_id585621556224data.UCopied.
final_update_id585621557091data.uCopied.
prev_final_update_id585621555794data.puCopied. Equal to the u of the previous message. A different value shows a gap.
last_update_idnull—Null. Depth updates do not contain a separate last update ID.
sideaskdata.bdata.abid for levels in b, ask for levels in a. One row per level.
price85599.7data.b[][0]data.a[][0]Copied as the exact decimal string.
quantity0.000data.b[][1]data.a[][1]Copied as the exact decimal string. The value is the new total at that price. 0.000 removes the level.
order_countnull—Null. Aster does not send order counts.

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.

REST responsereceived 2026-10-05 19:16:12.809647 UTC
GET https://fapi.asterdex.com/fapi/v1/depth?symbol=BTCUSDT&limit=5
{
"lastUpdateId": 585621541676,
"E": 1791227772674,
"T": 1791227772650,
"bids": [
["85600.8", "0.109"],
["85599.6", "0.058"],
["85594.3", "0.025"],
["85594.2", "0.263"],
["85594.1", "0.722"]
],
"asks": [
["85600.9", "0.963"],
["85604.0", "0.125"],
["85604.1", "0.025"],
["85604.2", "6.206"],
["85604.3", "6.949"]
]
}

Published rows · 10

received_time1791227772809647978—Our collector's clock when it received the REST response, in nanoseconds since the Unix epoch.
event_time1791227772674ECopied. Milliseconds.
transaction_time1791227772650TCopied. Milliseconds.
symbolBTCUSDT—The symbol that the collector requested.
event_typesnapshot—snapshot for every REST snapshot.
first_update_idnull—Null for snapshots.
final_update_id585621541676lastUpdateIdCopied.
prev_final_update_idnull—Null for snapshots.
last_update_id585621541676lastUpdateIdCopied. Replay from the first later update that has first_update_id ≤ this value ≤ final_update_id, or that has prev_final_update_id equal to this value.
sideaskbidsasksbid for levels in bids, ask for levels in asks. One row per level.
price85600.9bids[][0]asks[][0]Copied as the exact decimal string.
quantity0.963bids[][1]asks[][1]Copied as the exact decimal string.
order_countnull—Null. Aster does not send order counts.

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 side noop, and with price and quantity 0. This row contains the update IDs and does not change the order book. An empty REST snapshot becomes one noop snapshot row. 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 snapshot rows. These rows have received_time at the start of the hour and the event_time of the last exchange event before that time. Their transaction_time is null. Their final_update_id and last_update_id contain 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.

WebSocket message · !ticker@arrreceived 2026-10-05 19:16:13.823719 UTC
{
"stream": "!ticker@arr",
"data": [
{
"e": "24hrTicker",
"E": 1791227773292,
"s": "BTCUSDT",
"p": "254.9",
"P": "0.299",
"w": "85953.6",
"c": "85600.9",
"Q": "0.002",
"o": "85346.0",
"h": "86964.9",
"l": "84942.4",
"v": "7310.230",
"q": "628340740.71",
"O": 1791141360000,
"C": 1791227773250,
"F": 148456821,
"L": 148500896,
"n": 44075
},
{
"e": "24hrTicker",
"E": 1791227772893,
"s": "TRADOORUSDT",
"p": "0.0106000",
"P": "1.529",
"w": "0.6992235",
"c": "0.7038000",
"Q": "1",
"o": "0.6932000",
"h": "0.7055000",
"l": "0.6880000",
"v": "87356",
"q": "61081.3700000",
"O": 1791147960000,
"C": 1791227772850,
"F": 384877,
"L": 385481,
"n": 605
}
]
}

Published rows · 2

received_time1791227773823719000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Aster does not send this value.
event_time1791227773292data[].ECopied. Milliseconds.
symbolBTCUSDTdata[].sCopied.
price_change254.9data[].pCopied.
price_change_percent0.299data[].PCopied. Percent: 0.299 means +0.299 %.
weighted_average_price85953.6data[].wCopied.
last_price85600.9data[].cCopied.
last_quantity0.002data[].QCopied. Base asset units.
open_price85346.0data[].oCopied.
high_price86964.9data[].hCopied.
low_price84942.4data[].lCopied.
base_asset_volume7310.230data[].vCopied. Base asset units.
quote_asset_volume628340740.71data[].qCopied. Quote asset units.
statistics_open_time1791141360000data[].OCopied. Milliseconds.
statistics_close_time1791227773250data[].CCopied. Milliseconds.
first_trade_id148456821data[].FCopied.
last_trade_id148500896data[].LCopied.
total_trades44075data[].nCopied.

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.

WebSocket message · !markPrice@arr@1sreceived 2026-10-05 19:16:13.403169 UTC
{
"stream": "!markPrice@arr@1s",
"data": [
{
"e": "markPriceUpdate",
"E": 1791227773000,
"s": "BTCUSDT",
"p": "85606.06731160",
"P": "85585.57423237",
"i": "85630.89804348",
"r": "0.00006494",
"T": 1791244800000
}
]
}

Published row

received_time1791227773403169000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Aster does not send this value.
event_time1791227773000data[].ECopied. Milliseconds.
symbolBTCUSDTdata[].sCopied.
mark_price85606.06731160data[].pCopied.
index_price85630.89804348data[].iCopied.
estimated_settle_price85585.57423237data[].PCopied. The Aster documentation says that this value is useful only in the last hour before settlement.
funding_rate0.00006494data[].rCopied. A fraction per funding period: 0.00006494 is 0.006494 %.
next_funding_time1791244800000data[].TCopied. Milliseconds.

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
WebSocket message · !forceOrder@arrreceived 2026-10-05 19:24:36.372586 UTC
{
"stream": "!forceOrder@arr",
"data": {
"e": "forceOrder",
"E": 1791228276231,
"o": {
"s": "PAIDUSDT",
"S": "SELL",
"o": "LIMIT",
"f": "IOC",
"q": "14270",
"p": "0.0037107",
"ap": "0.0040600",
"X": "FILLED",
"l": "14270",
"z": "14270",
"T": 1791228276200
}
}
}

Published row

received_time1791228276372586000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Aster does not send this value.
event_time1791228276231data.ECopied. Milliseconds.
symbolPAIDUSDTdata.o.sCopied.
sideSELLdata.o.SCopied. BUY closes a liquidated short position. SELL closes a liquidated long position.
order_typeLIMITdata.o.oCopied.
time_in_forceIOCdata.o.fCopied.
quantity14270data.o.qCopied. The original order quantity, in base asset units.
price0.0037107data.o.pCopied. The limit price of the liquidation order.
average_price0.0040600data.o.apCopied. The average fill price.
order_statusFILLEDdata.o.XCopied.
last_filled_quantity14270data.o.lCopied. The quantity of the last fill of the order.
filled_quantity14270data.o.zCopied. The accumulated filled quantity.
trade_time1791228276200data.o.TCopied. Milliseconds.

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.

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

Contact support