BTC and ETH under /v1/hyperliquid/*: order books, trades, candles, funding, open interest, liquidations, order lifecycle, and L4 depth. For an overview of the venue, see Hyperliquid market data.
Core routes take plain perp symbols. A Spot pair (HYPE-USDC), a HIP-3 builder symbol (km:US500), a HIP-4 outcome side (#0), or a Lighter market each has its own namespace, and sending one to a core route reads the wrong market.
First request
meta.request_id, add history, funding, open interest, or L4 for the same symbol.
Route groups
Core routes cover current and historical market state:- Order books: current and historical depth, from native L2 to L4.
- Trades: fill-level rows with per-trade wallet attribution. The Hyperliquid Fills Data API page maps fills questions to the right routes.
- Candles, Funding, and Open interest: time series for each perp.
- Order history, Order flow, and Take profits and stop losses: order lifecycle.
Breadth above session VWAP
/v1/hyperliquid/breadth/above-vwap/current returns the latest core-perps snapshot and /v1/hyperliquid/breadth/above-vwap returns history. Each snapshot measures the percent of eligible core perps above their UTC-session VWAP, not a per-symbol VWAP.
Market breadth covers eligibility, null values, pagination, and history from August 24, 2026, including recomputed pre-launch values. HIP-3 has a separate breadth series; neither series includes Spot or HIP-4.
Store what makes a pull reproducible
For backtests, store the route, query parameters, time window, cursor, andrequest_id for each page. Check the same window with the /v1/data-quality/* routes so downstream users know whether it was complete and fresh enough to trust.
These routes serve market data only. Execution, wallet signing, and venue account actions are outside them.