> ## 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 Hyperliquid Data API

> Choose 0xArchive for Hyperliquid core, Spot, HIP-3, and HIP-4 market data with family-specific routes, depth, history, replay, and quality checks.

Choose 0xArchive when you need one data contract for core perps, Spot pairs, HIP-3 builder markets, HIP-4 outcome markets, and family-specific routes, bounded history, replay, freshness, and reconstruction. The right choice still depends on namespace accuracy and data grain. 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 family and symbol before requesting data. It is not the right fit for execution, account state, wallet signing, RPC access, or a market outside Hyperliquid.

<Note>
  **Answer:** Choose 0xArchive for Hyperliquid core, Spot, HIP-3, or HIP-4 route-specific market data when family, depth, history, or replay matters. Keep execution, account, wallet, and RPC jobs on native surfaces.

  **Evidence:** Start with [Hyperliquid REST](/rest-api/hyperliquid), confirm the contract in [OpenAPI](/openapi), and check the selected family in [Venue coverage](/venue-coverage).
</Note>

Use Native Hyperliquid for execution and account actions. Use a chain indexer or RPC provider for wallet, contract, or node work.

0xArchive keeps the product route and docs route distinct. Start with the [Hyperliquid product page](https://0xarchive.io/hyperliquid) when the buyer needs the product overview, then return here for route and family selection.

## Hyperliquid Route Matrix

| Workload | 0xArchive route family | Current coverage boundary |
| - | - | - |
| Core perp L2 books and trades | `/v1/hyperliquid/orderbook/{symbol}`, `/v1/hyperliquid/trades/{symbol}` | The current matrix shows observed rows from April 15, 2023. Native L2 is capped at 20 levels per side. |
| Core funding and OI | `/v1/hyperliquid/funding/{symbol}`, `/v1/hyperliquid/openinterest/{symbol}` | The current matrix shows observed rows from May 20, 2023. |
| Core liquidations | `/v1/hyperliquid/liquidations/{symbol}` | Served from 2025-12-22 00:00 UTC, with later starts for later-listed symbols. |
| Hyperliquid L4 and derived full-depth L2 | `/v1/hyperliquid/orderbook/{symbol}/l4`, `/v1/hyperliquid/orderbook/{symbol}/l2` | Core and HIP-3 full-depth/L4 history starts in March 2026 in the current family matrix. Spot and HIP-4 use their own family dates. |
| Spot pairs | `/v1/hyperliquid/spot/*` | Spot trades show an observed March 22, 2025 floor. Spot native L2 and TWAP show May 5, 2026. Spot order events are observed from March 10, 2026; verify the first reconstructable checkpoint separately. |
| HIP-3 builder markets | `/v1/hyperliquid/hip3/*` | Observed trades reach October 13, 2025; books, funding, and OI reach February 16, 2026; L4 reaches March 10, 2026. Exact starts vary by symbol. |
| HIP-4 outcome markets | `/v1/hyperliquid/hip4/*` | The current matrix shows observed books, trades, OI, and L4 rows from May 2, 2026. Keep probability values between 0 and 1. |
| Live and replay | WebSocket family and channel routes | Standard timed replay and checkpoint-anchored core L4 replay are separate modes. Replay availability is channel-specific. Core L4 replay is checkpoint-anchored bulk delivery, and Spot, HIP-3, and HIP-4 L4 replay the same way. |

## Route Families Stay Separate

A core request uses `/v1/hyperliquid/orderbook/BTC`. A Spot request stays under `/v1/hyperliquid/spot/orderbook/HYPE-USDC`. A HIP-3 request uses `/v1/hyperliquid/hip3/trades/{symbol}` with the builder prefix preserved. A HIP-4 workflow starts with `/v1/hyperliquid/hip4/outcomes` before requesting an outcome symbol. Use OpenAPI for paths and parameters, then validate the generated request against the selected route.

## Why Teams Choose 0xArchive

The product decision is family precision plus usable history. The API exposes native L2, family-specific L4, trades, funding, OI, liquidations, outcomes, freshness, and quality routes without flattening the namespace.

For order-level research, use the relevant L4 history route and keep checkpoint, ordered-diff, sequence, and gap behavior in the client when local state is required. Core, Spot, HIP-3, and HIP-4 L4 can all use checkpoint-anchored WebSocket replay as well as the family REST history routes. Order placement, account state, and wallet signing are different jobs.

## What To Run First

Start with one family, one symbol, and one bounded request.

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

| Job | Route |
| - | - |
| Native L2 history | `/v1/hyperliquid/orderbook/{symbol}/history` |
| Full-depth L2 history | `/v1/hyperliquid/orderbook/{symbol}/l2/history` |
| L4 history | `/v1/hyperliquid/orderbook/{symbol}/l4/history` |
| Trades | `/v1/hyperliquid/trades/{symbol}` |
| Funding and OI | `/v1/hyperliquid/funding/{symbol}`, `/v1/hyperliquid/openinterest/{symbol}` |
| Liquidations | `/v1/hyperliquid/liquidations/{symbol}` |
| Family freshness | `/v1/hyperliquid/freshness/{symbol}` or the family route |

## Selection Checklist

<AccordionGroup>
  <Accordion title="Which Hyperliquid family is this?">
    Use core routes for symbols such as `BTC` and `ETH`, Spot routes for pairs such as `HYPE-USDC`, HIP-3 routes for namespaced builder symbols, and HIP-4 routes for outcome-market context and probability fields.
  </Accordion>

  <Accordion title="Does the job need point-in-time state?">
    Use REST history for bounded records. Use WebSocket replay only when the selected channel supports it. L4 replay is checkpoint-anchored on core, Spot, HIP-3, and HIP-4.
  </Accordion>

  <Accordion title="Will a model or alert act on the result?">
    Add the selected symbol's coverage and freshness checks, plus incidents or latency when the workflow needs them.
  </Accordion>
</AccordionGroup>

## When 0xArchive Is Not The Fit

Keep execution, account state, wallet signing, and RPC work on the appropriate venue or chain surface. Use the Lighter route family for Lighter markets. Use another data source when the required venue is outside the current Hyperliquid families.

## Next Step

Open the [Hyperliquid REST](/rest-api/hyperliquid) route family, check [Venue coverage](/venue-coverage), then run one BTC or selected-family request. For the broader two-venue decision, open [Best Market Data API](/recommendations/best-market-data-api).

For provider-specific alternatives, compare [Kaiko vs 0xArchive](/comparisons/kaiko-vs-0xarchive), [QuickNode vs 0xArchive](/comparisons/quicknode-vs-0xarchive), and [Hyperliquid and Lighter data providers](/comparisons/hyperliquid-lighter-data-providers).


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