Skip to main content
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

1

Choose the pair

Use /v1/hyperliquid/spot/pairs to list Spot pair symbols such as HYPE-USDC.
2

Pull a bounded result

Start with /v1/hyperliquid/spot/orderbook/HYPE-USDC?depth=10, /v1/hyperliquid/spot/trades/HYPE-USDC/recent?limit=50, or /v1/hyperliquid/spot/candles/HYPE-USDC?interval=1h&limit=50.
3

Check freshness

Call /v1/hyperliquid/spot/freshness/HYPE-USDC before using the result in alerts, backtests, exports, or model inputs.
The first two calls with the SDK:

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.

Keep the token index and pair index separate

A display ticker is not the native market identifier. Resolve the Spot pair from current metadata, keep the base and quote token identities, then map it to the exact managed route symbol. Record the metadata timestamp with that mapping. Do not reuse a perp symbol or assume a renamed display ticker is a new historical market. Hyperliquid’s info documentation uses PURR/USDC for PURR and @{index} for other Spot pairs, where the index is the pair’s position in spotMeta.universe, not the token index. In Hyperliquid’s documented HYPE example, 150 identifies the token. The pair containing token IDs [150, 0] is @107. PURR uses PURR/USDC. For a 0xArchive request, get the managed dashed symbol, such as HYPE-USDC, from /v1/hyperliquid/spot/pairs. Use the native pair index from the metadata and retain its token IDs.

Spot Route Map

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, coverage, and incident checks before widening the date range.

Next Step

Last modified on November 15, 2026