Hyperliquid Futures wire format
This page shows how Hyperliquid perpetuals 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 Hyperliquid perpetuals 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 covers all listed perpetual markets. This includes builder-deployed dexes. Their coins have a dex prefix, for example xyz:XYZ100. All examples use BTC.
- Public WebSocket:
wss://api.hyperliquid.xyz/ws - Info REST (market metadata):
https://api.hyperliquid.xyz/info
Exchange API reference: hyperliquid.gitbook.io. For the conventions that apply to all exchanges, refer to the wire formats overview.
Trades
One row per fill from the trades subscription for each coin.
- WebSocket trades
Trade
{"channel": "trades","data": [{"coin": "BTC",→ symbol"side": "A",→ is_buyer_maker"px": "85628.0",→ price"sz": "0.00046",→ quantity"time": 1791227797187,→ event_time · trade_time"hash": "0x2e861874c0b73d972fff0445ea12f4020157005a5bba5c69d24ec3c77fbb1781","tid": 910713520736797,→ trade_id"users": ["0x368a9c423d0ce3d9887950125b1db4bb306c1b7d", "0x2332a66e6bdf9606d2fd63eed619357536612d4d"]}]}
Published row
event_time is equal to trade_time.kPEPE as KPEPE). Builder-dex coins, for example xyz:XYZ100, keep their case.tid is a hash of the order IDs of the buyer and the seller. It is not a sequence number. It does not increase, and you cannot use it to find gaps.side is the aggressor side. A (ask, the seller was the aggressor) gives true. B (bid, the buyer was the aggressor) gives false.market. Hyperliquid does not send an order type. This constant identifies the row as a taker fill.One taker order, several fills
If a taker order fills against several resting orders, it comes as one message with one element for each fill.
Shortened: The message contained 39 fills. This example shows the first three.
{"channel": "trades","data": [{"coin": "BTC",→ symbol"side": "B",→ is_buyer_maker"px": "85629.0",→ price"sz": "0.0009",→ quantity"time": 1791227799116,→ event_time · trade_time"hash": "0x55b2f804bb3995b3572c0445ea130d02030200ea563cb485f97ba3577a3d6f9d","tid": 590087756771268,→ trade_id"users": ["0xe60a6f40ad907263441fe89236bb67b1a47683dc", "0x4c6988b39fc0904628c2959e7606ef5f8518c152"]},{"coin": "BTC",→ symbol"side": "B",→ is_buyer_maker"px": "85629.0",→ price"sz": "0.00064",→ quantity"time": 1791227799116,→ event_time · trade_time"hash": "0x55b2f804bb3995b3572c0445ea130d02030200ea563cb485f97ba3577a3d6f9d","tid": 775060480000248,→ trade_id"users": ["0xe60a6f40ad907263441fe89236bb67b1a47683dc", "0x338e1b3dbdd72c6601a99e34f2ec6881b89d9c8d"]},{"coin": "BTC",→ symbol"side": "B",→ is_buyer_maker"px": "85629.0",→ price"sz": "0.00064",→ quantity"time": 1791227799116,→ event_time · trade_time"hash": "0x55b2f804bb3995b3572c0445ea130d02030200ea563cb485f97ba3577a3d6f9d","tid": 146242069110799,→ trade_id"users": ["0xe60a6f40ad907263441fe89236bb67b1a47683dc", "0xf86a91bda299b36c7d4fc8a7b57f5e32c34e748f"]}]}
Published rows · 3
event_time is equal to trade_time.kPEPE as KPEPE). Builder-dex coins, for example xyz:XYZ100, keep their case.tid is a hash of the order IDs of the buyer and the seller. It is not a sequence number. It does not increase, and you cannot use it to find gaps.side is the aggressor side. A (ask, the seller was the aggressor) gives true. B (bid, the buyer was the aggressor) gives false.market. Hyperliquid does not send an order type. This constant identifies the row as a taker fill.Notes
- We do not publish
hashandusers(the addresses of the buyer and the seller). Some fills have ahashthat is all zeros. - One message can contain several fills of one taker order (with the same
time,sideandhash). Each fill is a separate row with its owntid. - After each subscription, Hyperliquid first sends the most recent trades of the market (about 30), also if they are old. It does not identify them as a replay. After a reconnect, the collector discards the replayed trades that it already wrote. The postprocessor discards trades with a time more than 5 seconds before the start of the hour of the file. It also discards exact duplicates and trades that we already published in an earlier hour.
- Before the 2026-09 data-integrity release, we could publish a replayed trade again in the file of a later hour. To remove duplicates from older history, use (
symbol,trade_id,trade_time) as the key. Hyperliquid documentation states thattidis unique only together with the coin and the time.
For the column types and descriptions, refer to the Trades schema.
Order Book
One row per price level of each l2Book snapshot.
- WebSocket l2Book
Each l2Book message is a full snapshot of the top of the order book, not a delta. Each message becomes one snapshot row for each level.
Shortened: Hyperliquid sent 20 bid levels and 20 ask levels. This example shows the best 3 of each.
{"channel": "l2Book","data": {"coin": "BTC",→ symbol"time": 1791227796735,→ event_time · transaction_time · final_update_id · last_update_id"levels": [[→ side{→ side"px": "85628.0",→ side · price"sz": "5.71229",→ side · quantity"n": 19→ side · order_count},{→ side"px": "85627.0",→ side · price"sz": "0.005",→ side · quantity"n": 1→ side · order_count},{→ side"px": "85626.0",→ side · price"sz": "0.75919",→ side · quantity"n": 1→ side · order_count}],[→ side{→ side"px": "85629.0",→ side · price"sz": "4.37963",→ side · quantity"n": 39→ side · order_count},{→ side"px": "85630.0",→ side · price"sz": "0.58198",→ side · quantity"n": 23→ side · order_count},{→ side"px": "85631.0",→ side · price"sz": "3.85701",→ side · quantity"n": 9→ side · order_count}]]}}
Published rows · 6
time. Milliseconds.kPEPE as KPEPE). Builder-dex coins, for example xyz:XYZ100, keep their case.snapshot for every l2Book message.time of the snapshot. Hyperliquid has no update ID, thus the time identifies the snapshot.time of the snapshot, as in final_update_id.bid for levels in levels[0], ask for levels in levels[1]. One row per level.Notes
- Each snapshot replaces the full order book. Rebuild your order book from the rows of each
final_update_id. A snapshot contains a maximum of 20 levels for each side, at full price precision. Hyperliquid documentation gives a maximum of one push each 0.5 seconds. In October 2026, the snapshots of a market come about every 5.4 seconds (about 670 per hour). - For a snapshot with no bid levels and no ask levels, we publish one row with
sidenoopand withpriceandquantity0. This row clears the order book. Files that we wrote before the October 2026 pipeline update have no row for an empty snapshot. - If a snapshot has a level with a zero, negative or unparsable price or size, we do not publish any part of the snapshot. We do not publish it as a partial order book. Before the October 2026 pipeline update, we could publish such a snapshot as a partial or empty order book.
- A file can start with a checkpoint snapshot of the order book that continues from the previous hour. In this snapshot,
received_timeis the start of the hour andtransaction_timeis null.event_time,final_update_idandlast_update_idare thetimeof the snapshot that the order book came from.
For the column types and descriptions, refer to the Order Book schema.
Mark Price
One row per market per allDexsAssetCtxs message.
- WebSocket allDexsAssetCtxs
One allDexsAssetCtxs subscription covers all perpetual markets on all dexes. The message has no market names. The array of each dex is in the order of the allPerpMetas universe. The collector reads this universe at startup and at each symbol refresh, and uses it to name each entry. The collector ignores delisted markets.
Shortened: The frame contained 534 markets on 11 perp dexes. This example shows only BTC, the first market of the main dex "". The collector divides each frame into one record for each market.
{"channel": "allDexsAssetCtxs","data": {"ctxs": [["",→ symbol[{"funding": "0.0000125",→ funding_rate"openInterest": "38976.50654","prevDayPx": "85366.0","dayNtlVlm": "2807065618.8274302483","premium": "-0.0001214394","oraclePx": "85639.4",→ index_price"markPx": "85623.0",→ mark_price"midPx": "85628.5","impactPxs": ["85628.0", "85629.0"],"dayBaseVlm": "32630.96689"}]]]}}
Published row
received_time / 1,000,000). Asset contexts have no exchange timestamp.allPerpMetas metadata. BTC is the first market of the main dex "". We change main-dex coins to upper case. Builder-dex coins, for example xyz:XYZ100, keep their case.oraclePx, the oracle price. For main-dex markets, Hyperliquid calculates it as a weighted median of prices on centralized exchanges.0.0000125 is 0.00125 % per hour.Notes
- Hyperliquid does not document the frequency of
allDexsAssetCtxspushes. In October 2026, a push comes about every 15 seconds, thus a market has about 240 rows per hour. Each push becomes a row, also if no value changed. - We do not publish the 24h fields (
prevDayPx,dayNtlVlm,dayBaseVlm),midPx,premiumandimpactPxs. - In files that we wrote before the October 2026 pipeline update,
event_timeis in nanoseconds (the receive clock, equal toreceived_time). Divide those values by 1,000,000.
For the column types and descriptions, refer to the Mark Price schema.
Open Interest
One row per market per allDexsAssetCtxs message, from the same entries as mark price.
- WebSocket allDexsAssetCtxs
One allDexsAssetCtxs subscription covers all perpetual markets on all dexes. The message has no market names. The array of each dex is in the order of the allPerpMetas universe. The collector reads this universe at startup and at each symbol refresh, and uses it to name each entry. The collector ignores delisted markets.
Shortened: The frame contained 534 markets on 11 perp dexes. This example shows only BTC, the first market of the main dex "". The collector divides each frame into one record for each market.
{"channel": "allDexsAssetCtxs","data": {"ctxs": [["",→ symbol[{"funding": "0.0000125","openInterest": "38976.50654",→ sum_open_interest"prevDayPx": "85366.0","dayNtlVlm": "2807065618.8274302483","premium": "-0.0001214394","oraclePx": "85639.4","markPx": "85623.0","midPx": "85628.5","impactPxs": ["85628.0", "85629.0"],"dayBaseVlm": "32630.96689"}]]]}}
Published row
allPerpMetas metadata. BTC is the first market of the main dex "". We change main-dex coins to upper case. Builder-dex coins, for example xyz:XYZ100, keep their case.mark_price.received_time / 1,000,000). Asset contexts have no exchange timestamp.Notes
- We do not publish negative or unparsable open interest values. We still publish the mark price row of the same entry.
- In files that we wrote before the October 2026 pipeline update,
timestampis in nanoseconds (the receive clock, equal toreceived_time). Divide those values by 1,000,000.
For the column types and descriptions, refer to the Open Interest schema.
Not published
- Ticker: Hyperliquid has no 24h ticker channel. We do not publish the 24h fields of the asset contexts.
- Liquidations: Hyperliquid has no public liquidation stream.