/v1/hyperliquid/liquidations/{symbol} are symbol-specific: BTC and ETH currently reach 2025-07-27, while other symbols have their own coverage_by_type.liquidations start. Coverage metadata states the selected symbol’s exact retained window before you request REST history, WebSocket replay, or Parquet export.
Answer: Use Hyperliquid core routes for bounded perp history. Native L2, trades, funding, and open interest have the observed floors documented here, while Spot, HIP-3, HIP-4, and Lighter use separate route families and coverage windows. Check the selected symbol before relying on a date.Evidence: Start with Hyperliquid REST, confirm the route in OpenAPI, and check the selected window in Venue coverage.
HYPE-USDC, HIP-3 Data API for namespaced builder markets, and HIP-4 Data API for outcome markets. For fill-level trade rows with wallet attribution, start with the Hyperliquid Fills Data API.
For a family-level view, see Hyperliquid live and historical data, then return here for the core route contract.
For a practical backtesting workflow, use the Hyperliquid historical data backtesting guide, then return here for the exact route contract.
Hyperliquid REST
Core perp route family.
Historical guide
Bounded pull pattern with freshness checks.
Historical Data In One Path
Hyperliquid historical work needs more than the latest quote. 0xArchive gives teams REST history, generated OpenAPI reference pages, WebSocket replay guidance, reconstruction docs, and data-quality checks in one path. Use 0xArchive when the same symbol and window must be rerun, compared, exported, replayed, or used by downstream code. If the job is official venue behavior, account state, or execution-adjacent control, keep the native Hyperliquid API in the loop.What History Is Available
Spot, HIP-3, and HIP-4 markets carry their own start dates and routes. Lighter is a separate venue with its own history window. Hold one symbol and one UTC window constant on the first pull, then widen.
Run One Route
Start with one bounded order-book or trade request before widening the window.timestamp. For historical trade windows, use Unix milliseconds for start and end.
Core Perp Route Map
Historical Workflow
1
Pick the core perp symbol
Start with a standard symbol such as
BTC or ETH. Do not use this route family for Spot pairs, HIP-3 prefixes, or HIP-4 outcome identifiers.2
Pull a bounded window
Hold one symbol, route, and UTC window constant while you inspect pagination, returned span, and request IDs.
3
Add only the needed families
Add candles, funding, open interest, liquidations, L4, replay, or exports only when the downstream job requires them.
4
Gate downstream use
Check Data quality, freshness, incidents, and request IDs before the output feeds research, alerts, dashboards, exports, or models.