---
title: "Hyperliquid Historical Data API | 0xArchive"
description: "Run Hyperliquid historical market data for order books, trades, funding, open interest, liquidations, candles, replay, and exports."
canonical_url: "https://0xarchive.io/blog/introducing-0xarchive"
markdown_url: "https://0xarchive.io/blog/introducing-0xarchive.md"
route: "/blog/introducing-0xarchive"
robots: "index, follow"
generated_from: "prerendered_html"
---

# Hyperliquid Historical Data API | 0xArchive
Run Hyperliquid historical market data for order books, trades, funding, open interest, liquidations, candles, replay, and exports.
## Hyperliquid Historical Data API

Getting clean Hyperliquid history used to mean stitching raw S3 dumps, rate-limited venue calls, and a weekend of reconstruction code. 0xArchive launched to make it one account, one API key, and one set of routes you can rerun. The first job was Hyperliquid core perp history: order books, trades, funding, open interest, liquidations, and candles, for builders who need the same window twice.

## What you can pull

- **Order books** - point snapshots, historical windows, and L4 order-level routes.
- **Trades** - every fill with time, side, price, and size.
- **Funding and open interest** - derivatives context for backtests, dashboards, and risk views.
- **Liquidations** - liquidation events for risk and cascade analysis.
- **Candles** - OHLCV history for time-series work.
- **Replay and exports** - WebSocket replay and Data Catalog Parquet files for bounded jobs.

## Data Coverage

Hyperliquid history starts in April 2023: more than 24.6 billion order-book snapshots and over 2.3 billion fills, plus funding, open interest, liquidations, and candles. Coverage has since grown into Hyperliquid Spot, HIP-3, HIP-4, and Lighter, and each family keeps its own namespace and symbol rules. Live counts are on the status page.

## Run one route

Create a key, then confirm the response shape before you wire anything around it:

```
curl "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC?depth=20" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

Then pick the surface that matches the job:

- [Hyperliquid REST docs](https://docs.0xarchive.io/rest-api/hyperliquid) for route contracts and examples.
- [Historical market data guide](https://docs.0xarchive.io/guides/historical-market-data) for bounded windows and request checks.
- [Data Catalog](https://0xarchive.io/data/catalog) for Parquet exports by market, schema, and UTC range.
- [Pricing](https://0xarchive.io/pricing) for plans, replay, and export credits.

## What you get

- **REST API** - route-family endpoints with cursor pagination for long windows.
- **WebSocket replay** - historical playback when event order matters.
- **Python, TypeScript, and Rust SDKs** - client libraries for REST and replay.
- **Machine-readable surfaces** - OpenAPI, llms.txt, MCP, CLI, and a Claude skill for generated clients and agents.