Exchange Wire Formats

Hyperliquid Spot wire format

This page shows how Hyperliquid 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 Hyperliquid 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.

Spot subscriptions have "spot": true. Hyperliquid identifies most spot markets as @<index> (HYPE/USDC is @107). We publish them with the pair name and _, for example HYPE_USDC. The examples use PURR/USDC. This is the only spot market that Hyperliquid names by its pair.

  • 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 market.

  • WebSocket trades

Trade

WebSocket message · tradesreceived 2026-10-05 19:27:53.011457 UTC
{
"channel": "trades",
"data": [
{
"coin": "PURR/USDC",
"side": "A",
"px": "0.15967",
"sz": "1055.0",
"time": 1791228472658,
"hash": "0x10fa35a3dfc5ea3512730445ea37be0201fe00897ac90907b4c2e0f69ec9c41f",
"tid": 816377306689042,
"users": ["0x9266865bb6afb4c4f618544dd3b8c970f17aa664", "0xc6df8428e2b9bade2485e9733da37f423b7238aa"]
}
]
}

Published row

received_time1791228473011457000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Hyperliquid does not send this value.
event_time1791228472658data[].timeCopied. Milliseconds. Hyperliquid sends one time for each trade, thus event_time is equal to trade_time.
symbolPURR_USDCdata[].coinThe pair of the market in upper case, with _ in place of /. Hyperliquid names spot markets @<index> (HYPE/USDC is @107), except PURR/USDC. The collector uses spotMeta to find the base and quote token names for each index.
trade_id816377306689042data[].tidCopied. The Hyperliquid 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.
price0.15967data[].pxCopied as the exact decimal string that Hyperliquid sent.
quantity1055.0data[].szCopied as the exact decimal string. Base asset units.
trade_time1791228472658data[].timeCopied. Milliseconds.
is_buyer_makertruedata[].sideside is the aggressor side. A (ask, the seller was the aggressor) gives true. B (bid, the buyer was the aggressor) gives false.
order_typemarket—Always market. Hyperliquid does not send an order type. This constant identifies the row as a taker fill.

Recent trades sent after a subscription

The first trades message after a subscription repeats the latest 30 trades of the market. On quiet markets, these trades can be hours or months old. This message came 46 seconds after the start of the hour. We discard trades with a time more than 5 seconds before the start of the hour. We publish trades from the last 5 seconds of the previous hour in this hour, if that hour did not already publish them.

Shortened: The message contained 30 trades: 4 from more than 5 seconds before the hour, 4 from the last 5 seconds of the previous hour and 22 from this hour. This example shows two of each.

WebSocket message · tradesreceived 2026-10-05 20:00:46.348537 UTC
{
"channel": "trades",
"data": [
{
"coin": "PURR/USDC",
"side": "B",
"px": "0.15543",
"sz": "80.0",
"time": 1791230361434,
"hash": "0xf08ba9f8823c8bb8f2050445eaa01e0201dd00de1d3faa8b9454554b413065a3",
"tid": 586859438661648,
"users": ["0x19ae423cbb2b06701a64896d12bb318e26e3e64f", "0x2ad22b8c322e3322461aa339f60193576aa34698"]
},
{
"coin": "PURR/USDC",
"side": "B",
"px": "0.15536",
"sz": "321.0",
"time": 1791230362732,
"hash": "0xffcb89c730ed035b01450445eaa03102036100accbe0222ea3943519efe0dd46",
"tid": 270882739007052,
"users": ["0xa5954b9a62ecde4a077c8c12ab66c8093917fde0", "0x9266865bb6afb4c4f618544dd3b8c970f17aa664"]
},
{
"coin": "PURR/USDC",
"side": "A",
"px": "0.1549",
"sz": "644.0",
"time": 1791230397375,
"hash": "0xf58f8171d9341951f7090445eaa22402042f00577437382499582cc49837f33c",
"tid": 344755378042620,
"users": ["0x9266865bb6afb4c4f618544dd3b8c970f17aa664", "0xc5549b1aac5a98a9f4bebe37cc70cd48c064d514"]
},
{
"coin": "PURR/USDC",
"side": "B",
"px": "0.155",
"sz": "1124.0",
"time": 1791230397912,
"hash": "0x132c735ed531f0db14a60445eaa22b02058c004470350fadb6f51eb19435cac5",
"tid": 1123349272790135,
"users": ["0xc6df8428e2b9bade2485e9733da37f423b7238aa", "0x9266865bb6afb4c4f618544dd3b8c970f17aa664"]
},
{
"coin": "PURR/USDC",
"side": "A",
"px": "0.1549",
"sz": "35.0",
"time": 1791230400602,
"hash": "0xeceeb6ef08083168ee680445eaa24e02125200d4a30b503a90b76241c70c0b53",
"tid": 359068625617933,
"users": ["0x9266865bb6afb4c4f618544dd3b8c970f17aa664", "0xd440715f2ce6f7ed1924f282e0096c863e7049f7"]
},
{
"coin": "PURR/USDC",
"side": "A",
"px": "0.15489",
"sz": "199.0",
"time": 1791230400602,
"hash": "0xeceeb6ef08083168ee680445eaa24e02125200d4a30b503a90b76241c70c0b53",
"tid": 252307041241746,
"users": ["0x50fef8d71afce6404d0cbb2a8bb0df65f87b1685", "0xd440715f2ce6f7ed1924f282e0096c863e7049f7"]
}
]
}

Published rows · 4

received_time1791230446348537000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Hyperliquid does not send this value.
event_time1791230397375data[].timeCopied. Milliseconds. Hyperliquid sends one time for each trade, thus event_time is equal to trade_time.
symbolPURR_USDCdata[].coinThe pair of the market in upper case, with _ in place of /. Hyperliquid names spot markets @<index> (HYPE/USDC is @107), except PURR/USDC. The collector uses spotMeta to find the base and quote token names for each index.
trade_id344755378042620data[].tidCopied. The Hyperliquid 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.
price0.1549data[].pxCopied as the exact decimal string that Hyperliquid sent.
quantity644.0data[].szCopied as the exact decimal string. Base asset units.
trade_time1791230397375data[].timeCopied. Milliseconds.
is_buyer_makertruedata[].sideside is the aggressor side. A (ask, the seller was the aggressor) gives true. B (bid, the buyer was the aggressor) gives false.
order_typemarket—Always market. Hyperliquid does not send an order type. This constant identifies the row as a taker fill.

Notes

  • We do not publish hash and users (the addresses of the buyer and the seller). Some fills have a hash that is all zeros.
  • One message can contain several fills of one taker order (with the same time, side and hash). Each fill is a separate row with its own tid.
  • 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 that tid is 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.

WebSocket message · l2Bookreceived 2026-10-05 19:18:01.709503 UTC
{
"channel": "l2Book",
"data": {
"coin": "PURR/USDC",
"time": 1791227881323,
"levels": [
[
{
"px": "0.15963",
"sz": "1000.0",
"n": 1
},
{
"px": "0.15962",
"sz": "2165.0",
"n": 3
},
{
"px": "0.15952",
"sz": "1263.0",
"n": 1
}
],
[
{
"px": "0.15983",
"sz": "2879.0",
"n": 2
},
{
"px": "0.15985",
"sz": "103.0",
"n": 1
},
{
"px": "0.15998",
"sz": "610.0",
"n": 1
}
]
]
}
}

Published rows · 6

received_time1791227881709503000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Hyperliquid does not send this value.
event_time1791227881323data.timeCopied. Milliseconds.
transaction_time1791227881323data.timeCopied from the same time. Milliseconds.
symbolPURR_USDCdata.coinThe pair of the market in upper case, with _ in place of /. Hyperliquid names spot markets @<index> (HYPE/USDC is @107), except PURR/USDC. The collector uses spotMeta to find the base and quote token names for each index.
event_typesnapshot—snapshot for every l2Book message.
first_update_idnull—Null. Hyperliquid order books have no update IDs.
final_update_id1791227881323data.timeThe time of the snapshot. Hyperliquid has no update ID, thus the time identifies the snapshot.
prev_final_update_idnull—Null. Snapshots do not chain.
last_update_id1791227881323data.timeThe time of the snapshot, as in final_update_id.
sidebiddata.levels[0]data.levels[1]bid for levels in levels[0], ask for levels in levels[1]. One row per level.
price0.15963data.levels[0][].pxdata.levels[1][].pxCopied as the exact decimal string.
quantity1000.0data.levels[0][].szdata.levels[1][].szCopied as the exact decimal string. It is the total resting size at that price. Base asset units.
order_count1data.levels[0][].ndata.levels[1][].nCopied. Number of resting orders at that price.

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 side noop and with price and quantity 0. 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_time is the start of the hour and transaction_time is null. event_time, final_update_id and last_update_id are the time of 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 activeSpotAssetCtx message for each market.

  • WebSocket activeSpotAssetCtx

The collector subscribes to activeAssetCtx for each spot market. Hyperliquid sends the response on the activeSpotAssetCtx channel.

WebSocket message · activeSpotAssetCtxreceived 2026-10-05 19:18:01.768875 UTC
{
"channel": "activeSpotAssetCtx",
"data": {
"coin": "PURR/USDC",
"ctx": {
"prevDayPx": "0.17128",
"dayNtlVlm": "2160182.4432799988",
"markPx": "0.15971",
"midPx": "0.159735",
"circulatingSupply": "594788239.0212099552",
"coin": "PURR/USDC",
"totalSupply": "594788250.3277299404",
"dayBaseVlm": "12955450.0"
}
}
}

Published row

received_time1791227881768875000—Our collector's clock when it received the message, in nanoseconds since the Unix epoch. Hyperliquid does not send this value.
event_time1791227881768—Our receive clock in milliseconds (received_time / 1,000,000). Asset contexts have no exchange timestamp.
symbolPURR_USDCdata.coinThe pair of the market in upper case, with _ in place of /. Hyperliquid names spot markets @<index> (HYPE/USDC is @107), except PURR/USDC. The collector uses spotMeta to find the base and quote token names for each index.
mark_price0.15971data.ctx.markPxCopied. If markPx is missing, we use midPx.
index_pricenull—Null. Hyperliquid spot contexts have no oracle price (oraclePx).
estimated_settle_pricenull—Null. Spot markets do not settle.
funding_ratenull—Null. Spot markets have no funding.
next_funding_timenull—Null. Spot markets have no funding.

Notes

  • Hyperliquid does not document the frequency of spot asset context pushes. In October 2026, a push comes about one time each second, thus a market has about 3,500 rows per hour. Each push becomes a row, also if no value changed.
  • We do not publish the 24h fields (prevDayPx, dayNtlVlm, dayBaseVlm), midPx (we use it only if markPx is missing), circulatingSupply and totalSupply.
  • If a context has no markPx and no midPx, we do not publish it.
  • In files that we wrote before the October 2026 pipeline update, event_time is in nanoseconds (the receive clock, equal to received_time). Divide those values by 1,000,000.

For the column types and descriptions, refer to the Mark Price schema.

Not published

  • Ticker: Hyperliquid has no 24h ticker channel. We do not publish the 24h fields of the asset contexts.
  • Open Interest: Spot markets have no open interest.
  • Liquidations: Spot markets have no liquidations.

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

Contact support