/v1/hyperliquid/hip3/*: trades, order books, candles, funding, open interest, CVD, liquidations, oracle prices, and L4 depth. HIP-3 symbols carry a builder prefix, such as xyz:TSLA or km:US500, and the prefix stays part of the symbol in every request and stored record. Find a market with List HIP-3 instruments, and check each data type’s history start in Venue coverage.
First request
Symbols
A builder-prefixed symbol such asxyz:TSLA is a different kind of instrument from a core Hyperliquid BTC, even though both sit under the Hyperliquid venue. Keep the prefix and its case exactly as the instruments route lists it, and do not URL-decode the colon in a way that changes the symbol. A namespaced symbol given without a venue most likely belongs to HIP-3. Store venue_family=hip3, or an equivalent field, with persisted results.
HIP-3 serves the same data families as core perps: order books, trades, candles, funding, open interest, CVD, liquidation events, liquidation levels, and freshness. Only the namespace and symbol differ. Exact routes and parameters are in the HIP-3 endpoint reference.
Aliases and historical continuity
Similar tickers or namespaces are not presumed predecessors. Do not stitch histories across distinct market IDs. REST routes acceptxyz:WTIOIL as an alias for canonical xyz:CL; both names refer to the same market identity. Use xyz:CL for discovery and coverage checks. This is one same-identity REST alias, not a general alias or predecessor registry. Do not assume this alias works for WebSocket subscriptions or Data Catalog exports.
Analytics and oracle routes
These routes add cumulative volume delta, projected liquidation levels, pending trigger-order clustering around price, and HIP-3 oracle state to trades, candles, funding, open interest, and depth. Both projected liquidation-level routes also serve
/history variants with cursor pagination; snapshots are retained from 2026-07-27. CVD buckets run from 1m to 1w and page with cursor and limit, like the core CVD route; see Pagination for joining pages.
Breadth above session VWAP
These aggregate routes track the share of eligible HIP-3 instruments trading above their current UTC-session VWAP:
Each eligible instrument contributes one vote. The routes return aggregate breadth only, not per-symbol VWAPs. Eligibility excludes instruments with no current-session volume or with a last completed 1-minute candle close older than 5 minutes, so eligibility changes with trading activity and candle freshness.
Data collection begins 2026-08-28. There is no synthetic pre-launch history, so earlier ranges contain no backfilled snapshots. When
counts.eligible is zero, value_pct is null, not 0.
The history route accepts start and end as Unix timestamps in milliseconds. Its optional interval selects the last stored snapshot in each bucket; percentages are never averaged, because the eligible denominator can vary. Pass the cursor from meta.next_cursor unchanged and treat it as exclusive. Market breadth covers the methodology, response fields, and how HIP-3 breadth differs from core-perps breadth.