> ## 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 market data for dashed pairs such as HYPE-USDC: native L2, trades, candles, L4 routes, TWAP, pair metadata, and freshness.

The Hyperliquid Spot data API returns live and historical market data for dashed pairs like `HYPE-USDC`: native order books, trades, candles, L4 order-level routes, TWAP, and freshness checks. L4 reconstruction availability varies by symbol and window.

0xArchive exposes Hyperliquid Spot through `/v1/hyperliquid/spot`, with pair discovery, pair metadata, native order books, trades, candles, L4 routes, order history, TWAP, user TWAP, and freshness checks. Current symbol rows show observed floors of March 22, 2025 for trades, May 5, 2026 for native order books, and March 10, 2026 for L4 keys; TWAP and reconstruction windows remain symbol-specific. Spot order-event diffs can precede the first reconstructable checkpoint, so probe diffs and reconstruction separately.

## Start Here

<Steps>
  <Step title="Choose the pair">
    Use `/v1/hyperliquid/spot/pairs` to list Spot 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>

## Route Scope

For a Spot backtest, pair monitor, or TWAP analysis, keep the pair namespace and data grain explicit. The current route set separates pair discovery, pair metadata, native L2, trades, candles, L4 checkpoints and history, order history, TWAP, user TWAP, and freshness. Coverage for one schema does not establish a full Spot history for the others.

## 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 | `/v1/hyperliquid/spot/orderbook/{symbol}/l4` |
| L4 history and diffs | `/v1/hyperliquid/spot/orderbook/{symbol}/l4/history`, `/v1/hyperliquid/spot/orderbook/{symbol}/l4/diffs` |
| Order history | `/v1/hyperliquid/spot/orders/{symbol}/history` |
| TWAP | `/v1/hyperliquid/spot/twap/{symbol}`, `/v1/hyperliquid/spot/twap/user/{user}` |
| 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 [data quality and freshness](/data-quality), 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.


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