> ## 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.

# Hyperliquid Spot Data API

> Hyperliquid Spot data API: pairs like HYPE-USDC with order books, trades, candlestick (OHLCV) candles, L4 reconstruction, TWAP, and freshness, from one key.

The Hyperliquid Spot data API returns live and historical market data for dashed pairs like `HYPE-USDC`: order books, trades, candles, full order-level (L4) reconstruction, TWAP, and freshness, all from one key.

0xArchive exposes Hyperliquid Spot through `/v1/hyperliquid/spot`, with pair discovery, pair metadata, order books, trades, candles, L4 reconstruction surfaces, order history, TWAP, user TWAP, and freshness checks. Spot trades go back to March 2025, native 20-level order books to May 2026, and order-level (L4) reconstruction to March 2026.

## Start Here

<Steps>
  <Step title="Choose the pair">
    Use `/v1/hyperliquid/spot/pairs` to discover supported pair symbols such as `HYPE-USDC`.
  </Step>

  <Step title="Pull a bounded result">
    Start with `/v1/hyperliquid/spot/orderbook/HYPE-USDC?depth=10`, `/v1/hyperliquid/spot/trades/HYPE-USDC?limit=50`, or `/v1/hyperliquid/spot/candles/HYPE-USDC?interval=1h&limit=50`.
  </Step>

  <Step title="Check freshness">
    Call `/v1/hyperliquid/spot/freshness/HYPE-USDC` before using the result in alerts, backtests, exports, or model inputs.
  </Step>
</Steps>

## Why 0xArchive Fits

Hyperliquid Spot builders need more than a one-off latest book. 0xArchive gives the same API posture as the rest of the product: authenticated REST, Endpoint Reference pages, JSON response envelopes, request IDs, pair discovery, live and historical windows, full order-level (L4) reconstruction, and freshness checks. One key covers the current book and the full Spot history behind it.

## Spot Route Map

| Need                     | Route                                                                    |
| ------------------------ | ------------------------------------------------------------------------ |
| Pair discovery           | `/v1/hyperliquid/spot/pairs`                                             |
| Pair metadata            | `/v1/hyperliquid/spot/pairs/{symbol}`                                    |
| Current order book       | `/v1/hyperliquid/spot/orderbook/{symbol}`                                |
| Historical order book    | `/v1/hyperliquid/spot/orderbook/{symbol}/history`                        |
| Historical trades        | `/v1/hyperliquid/spot/trades/{symbol}`                                   |
| Historical candles       | `/v1/hyperliquid/spot/candles/{symbol}`                                  |
| L4 checkpoint or history | `/v1/hyperliquid/spot/orderbook/{symbol}/l4` and history or diffs routes |
| Order history            | `/v1/hyperliquid/spot/orders/{symbol}/history`                           |
| TWAP                     | `/v1/hyperliquid/spot/twap/{symbol}` and user TWAP routes                |
| Freshness                | `/v1/hyperliquid/spot/freshness/{symbol}`                                |

Keep Spot examples on dashed pair symbols such as `HYPE-USDC`. Use Spot candles for pair OHLCV history; use core Hyperliquid pages for perp funding, open interest, and liquidations.

## Implementation Notes

Spot symbols are pair symbols. Keep `HYPE-USDC`-style values separate from core perp symbols such as `BTC`, HIP-3 namespaced symbols such as `km:US500`, and HIP-4 outcome identifiers. Use pair discovery before allowing a user or agent to submit arbitrary symbols.

For L4 and TWAP workflows, treat empty results or unavailable checkpoints as a state the client must handle. Preserve the error or response `request_id`, check freshness, and avoid filling missing reconstruction data with synthetic state.

## First Pair Evaluation

Start with one pair and one route before building a Spot data layer. Store the pair, route, query parameters, returned timestamp, request ID, freshness result, and the downstream job that will use the response. If the job is a backtest or export, add coverage and incident checks before widening the date range.

## Next Step

Open [Hyperliquid Spot REST](/rest-api/spot), then use [Choose an interface](/tooling) if the job should run through CLI, MCP Server, Skill, SDKs, OpenAPI, or a coding agent.