/v1/hyperliquid/trades/{symbol} returns fill-level rows with user_address where the venue reports it, with native trade coverage reaching back to April 2023; verify the selected symbol’s exact window and gaps before relying on it.
Trades route
Fill-level trade routes by venue family.
Hyperliquid REST
Core perp route family.
Why it matters
The fill tape is the right starting point for execution research, but wallet and builder attribution are response data, not server-side trades filters. Pull a bounded venue, market, and time window, paginate with cursor, and filter rows client-side. Use the corresponding export schema for large market-wide studies.What A Fill Row Carries
Each row is one execution with the context most fills APIs drop:maker_address, taker_address, order_id, and cloid appear where applicable, so a fill can be joined back to the order that produced it. Prices, sizes, and fees are decimal strings.
Fills Intent To Route Map
These route families use the standard
{success, data, meta} envelope. Cursor types and page-size rules remain route-specific; preserve meta.next_cursor and meta.request_id for each page.
Wallet Attribution
Hyperliquid fills carryuser_address wherever the venue reports it, so the tape answers wallet-level questions directly: what one account filled in a window, whether it made or took liquidity on each execution, and what each fill did to its position. The TP/SL and order-history routes accept a user filter (the query parameter is user, not the user_address field name each record carries), which turns one wallet’s risk management and order behavior into a bounded query instead of a full-tape scan.
The user filter on order-history is order lifecycle, not fill retrieval. Use it when the question is about an order’s placed, partially filled, filled, or canceled state, not as a replacement for the fill tape.
Native userFills terminology
Native Hyperliquid userFills maps to 0xArchive trades. 0xArchive has no WebSocket channel named userFills; subscribe to the venue’s trades channel and apply client-side attribution instead.
TP/SL Lifecycle Around Fills
A take-profit or stop-loss rests as a trigger order until its price condition fires, and when it fires it becomes an ordinary fill. To follow that lifecycle, pair/v1/hyperliquid/orders/{symbol}/tpsl for the triggers with /v1/hyperliquid/trades/{symbol} for the resulting executions, joining on the order that placed the trigger. A trigger that never fired and one that fired are different events; the status field separates them.
Coverage Window
Hyperliquid native L2 and trade rows have observed floors in April 2023. Core and HIP-3 order-level (L4) history has an observed floor of March 10, 2026; HIP-4 begins May 2, 2026. Spot order-event diffs can precede the first reconstructable checkpoint, so probe those routes separately. Check the exact window and any gaps for your symbols on Venue coverage and Data quality before a backtest or export depends on the output.Maker And Taker Analysis
Thecrossed flag and fee sign support maker/taker studies when those fields are present. Count taker fills against maker fills for one wallet, sum signed fees to separate cost from rebate income, and use direction with start_position to tell opening flow from closing flow inside the same window. Treat optional attribution and position fields as nullable; do not assume every row carries the same enrichment.
Stream Fills Live
Thetrades channel streams fills as they execute. Order events, including trigger placements and cancels, stream through l4_orders.