Skip to main content
Run Hyperliquid core perp history for research, backtesting, replay prep, dashboards, alerts, exports, or generated clients. Order books and trades go back to April 2023, funding and open interest to May 2023, and completed liquidation events on /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. Use Hyperliquid core routes for standard perp market history. Use Hyperliquid Spot Data API for pair symbols such as 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. Looking for the product view before choosing a route? Explore Hyperliquid live and historical data, then come back here when you are ready to wire the first request. 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.
For timestamped order-book snapshots, use Unix milliseconds for 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.

​
Selection Checklist

Before comparing 0xArchive to a native venue pull, hold one symbol, one window, and one downstream job constant. Record the route, parameters, returned span, cursor chain, request IDs, data-quality result, and any gap or incident notes. That checklist makes the second run easier to compare than a screenshot or row count. Ask whether the workflow needs point snapshots, historical records, replay order, or local reconstruction. REST history is best for bounded data pulls. WebSocket replay is best when event order matters. SDK reconstruction is best when the product maintains a local book. All three should preserve request IDs and data-quality context.

​
Next Step

Open Hyperliquid REST for the contract layer, then run Pull historical market data for one symbol and one window before widening the job.
Last modified on August 13, 2026