Skip to main content
A trade is a single fill: side, price, size, the wallets involved, and the chain transaction. Trades exist on every venue family.

Get trades

Routes: /v1/hyperliquid/trades/{symbol}, /recent. Plain perp symbols such as BTC.

Request parameters

A trade returns:

Response fields

Each item in the data array: Builder and HIP-3 fills also carry builder_address, builder_fee, deployer_fee, and priority_gas; order_id, cloid, maker_address, taker_address, and twap_id appear where applicable. price, size, and fee are decimal strings. Paginate with meta.next_cursor and keep meta.request_id per page. Full field meanings live in the field dictionary.

Stream it live

Every venue streams trades. Subscribe to trades for Hyperliquid core, or the venue-prefixed channel for the rest: spot_trades, hip3_trades, hip4_trades, lighter_trades. Keep the symbol shape that matches the family.
Connection, keep-alive, and reconnect handling live in the WebSocket tab; the full channel list is on WebSocket channels.

Export in bulk

For the historical tape as files, use the trades export schema ($8/GB, $15 minimum), delivered as Parquet with ZSTD compression. Build a selection in the Data catalog; columns and coverage keys are on Export schemas.

Next

Use Order books for resting depth, Liquidations for forced exits, Example responses for more payload shapes, or Data quality before trades feed a model. For the Hyperliquid fills workflow with wallet attribution and TP/SL context, start with the Hyperliquid Fills Data API.
Last modified on July 4, 2026