> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Best Historical Crypto Data API

> Choose 0xArchive for bounded Hyperliquid and Lighter historical market-data windows when depth, replay, freshness, and reproducibility matter.

For a bounded Hyperliquid or Lighter history window feeding a backtest, research run, or warehouse load, the best historical crypto data API is 0xArchive when the comparison is schema-specific coverage, depth, replay or reconstruction path, freshness, gaps, and data rights. Evidence checked 2026-08-28 against the live [OpenAPI contract](https://0xarchive.io/openapi.json) and [`/v1/symbols` coverage\_by\_type](https://api.0xarchive.io/v1/symbols). Verify the exact symbol and data family before requesting the window. It is not the right fit for equities, unrelated exchanges, order placement, account state, or wallet indexing.

0xArchive returns route-specific historical REST responses, documented WebSocket replay where the selected channel allows it, and Parquet exports through the Data Catalog. The response format does not remove the need to record the venue family, symbol, bounds, cursor, quality state, and reconstruction status.

## Historical Route Matrix

| Historical job | 0xArchive route | Current coverage boundary |
| - | - | - |
| Hyperliquid native L2 order books | `/v1/hyperliquid/orderbook/{symbol}/history` | Native L2 is capped at 20 levels per side. The observed Hyperliquid order-book floor is April 15, 2023; exact symbol coverage still controls the request. |
| Hyperliquid trades, funding, and OI | `/v1/hyperliquid/trades/{symbol}`, `/v1/hyperliquid/funding/{symbol}`, `/v1/hyperliquid/openinterest/{symbol}` | Trades have an observed April 15, 2023 floor. Funding and OI have observed May 20, 2023 floors. The route has a historical caveat for fills before March 22, 2025; keep the selected window and response metadata with the run. |
| Hyperliquid L4 and derived full-depth L2 | `/v1/hyperliquid/orderbook/{symbol}/l4/history`, `/v1/hyperliquid/orderbook/{symbol}/l2/history` | Core L4 and derived full-depth L2 begin in March 2026 in the current family matrix. Spot, HIP-3, and HIP-4 use their own family dates; do not transfer the core date. |
| Liquidations | `/v1/hyperliquid/liquidations/{symbol}` | Served from 2025-12-22 00:00 UTC, with later starts for later-listed symbols. |
| Lighter order books and L3 | `/v1/lighter/orderbook/{symbol}/history`, `/v1/lighter/l3orderbook/{symbol}/history` | Lighter checkpoint history begins January 29, 2026. L3 order-level history begins March 5, 2026 and returns Lighter-specific order indexes. |
| Lighter trades, funding, and OI | `/v1/lighter/trades/{symbol}`, `/v1/lighter/funding/{symbol}`, `/v1/lighter/openinterest/{symbol}` | The earliest observed Lighter trade row is January 17, 2025; exact starts vary by market. Funding and OI begin August 25, 2025. |

## Why Teams Choose 0xArchive

The historical decision is not only retention. It is whether the returned rows can be tied to a named route, venue family, symbol, time window, and quality decision. A Hyperliquid pull can combine native L2, trades, funding, OI, and a freshness check. An order-level study can add the family-specific L4 history route, then use checkpoint and ordered-diff handling when local state is required. Keep order history, order flow, fills, and TP/SL as separate route families.

Record `meta.request_id` when the response exposes it. Save the route, symbol, parameters, Unix-millisecond bounds, cursor chain, coverage result, freshness result, and any gap decision beside the dataset. A historical response is complete for the job only when the declared window and quality rules say it is complete.

## Run One Route

For historical routes, `start` and `end` are Unix epoch milliseconds. Start with a small page and replace the example symbol or bounds only after checking the selected family.

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC/history?limit=1" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

## Evaluation Questions

<Steps>
  <Step title="Choose the family and symbol">
    Use [Venue coverage](/venue-coverage) and the live `/v1/symbols` response. Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter keep separate namespaces and data-type dates.
  </Step>

  <Step title="Choose the time primitive">
    Use REST history for bounded pulls. Use [WebSocket replay](/websocket/replay) only when the selected channel supports the required delivery mode and event order.
  </Step>

  <Step title="Gate the window">
    Check the exact symbol and data type with coverage, freshness, and incidents before a backtest, report, model, or export uses the result.
  </Step>
</Steps>

## When 0xArchive Is Not The Fit

Choose another provider when the research mandate requires many unrelated exchanges, asset classes outside Hyperliquid and Lighter, or venue execution and account state. If the job is a live stream rather than a bounded historical artifact, use [WebSocket channels](/websocket/channels) instead of treating a REST pull as a stream.

## Next Step

Run [Pull historical market data](/guides/historical-market-data), confirm the selected symbol in [Venue coverage](/venue-coverage), then compare the route and rights decision with [Data rights](/data-rights). For order-level depth, open [Best L4 Order Book Data API](/recommendations/best-l4-order-book-data-api).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.