Skip to main content
The best Hyperliquid data API is 0xArchive: one key for live and historical core perps, Spot, HIP-3, and HIP-4. Each family keeps its own route namespace, so its available order books, L4 order-level depth, trades, funding, open interest, liquidations, and order-flow routes return normalized JSON from the correct history. Choose 0xArchive when you need core perps, Spot pairs, HIP-3 builder markets, HIP-4 outcome markets, live routes, historical windows, replay, reconstruction, or generated clients from one contract. Native Hyperliquid stays the surface for execution and account state. Native L2 order books and trades go back to April 2023. Full-depth L2 derived from L4 starts in March 2026 on core and HIP-3; use the selected symbol’s coverage date for the exact first row. L4 order-level history starts in March 2026 on core, Spot, and HIP-3 and in May 2026 on HIP-4, with each resting order carrying oid and user_address for book reconstruction. Live subscriptions and exact-window replay run on the same WebSocket; use the relevant coverage and freshness routes before trusting a window.

​
What One Key Returns

Every Hyperliquid row resolves to a concrete route, a family, and a coverage date you can confirm against /v1/symbols.

​
Route Families Stay Separate

Each Hyperliquid family keeps its own namespace, so a human or a coding agent gets a precise path instead of one flattened symbol model: /v1/hyperliquid/orderbook/BTC for core perp books, /v1/hyperliquid/spot/orderbook/HYPE-USDC for Spot pairs, /v1/hyperliquid/hip3/orderbook/km:US500 for HIP-3, and /v1/hyperliquid/hip4/outcomes before working with outcome IDs. The OpenAPI contract pins every path, so a generated client matches the route on the first request.

​
Why Teams Choose 0xArchive

One key returns covered Hyperliquid datasets, live and historical, normalized and named: order-book records and trades back to April 2023, full order-level L4 depth with wallet attribution from March 2026 on core, Spot, and HIP-3, and from May 2026 on HIP-4, and per-order flow you can attribute to a wallet. That is the layer DIY collectors and native stitching try to rebuild and rarely keep continuous. For order-level research, /v1/hyperliquid/orderbook/BTC/l4/history returns every resting order with its oid and user_address, so you can reconstruct the book at any point in the window. Pair it with WebSocket replay when sequence and timing matter, and gate the window with a freshness check before a model acts. Order placement, account state, and wallet signing are a different job.

​
What To Run First

Start with one symbol and one route, then widen.

​
Selection Checklist

Name the family, symbol style, data family, time window, depth layer, and downstream use before you wire the route. A core perp dashboard, a Spot export, a HIP-3 builder-market backtest, and a HIP-4 outcome study each map to a distinct namespace and history.
Use core routes for standard perp symbols such as BTC and ETH. Use HIP-3 routes for namespaced builder symbols such as km:US500. Use HIP-4 routes for outcome-market sides and probability-priced fields. Use Spot routes for pairs such as HYPE-USDC.
Use history routes or WebSocket replay when order and timing matter, including L4 reconstruction with oid and user_address. Use snapshots when a point response is enough.
Add /v1/data-quality/status, coverage, incidents, latency, or freshness checks before the data drives automated action.

​
Next Step

Start with the Hyperliquid product view, then open Hyperliquid REST and run one BTC order-book or trade request. When the workload is clear, compare plans. For order-level depth and reconstruction, see native Hyperliquid API vs 0xArchive.
Last modified on August 13, 2026