Hyperliquid Spot data API decisions start with pair routing, freshness, and reconstruction fit, not with core-perp assumptions. 0xArchive exposes Hyperliquid Spot throughDocumentation Index
Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
Use this file to discover all available pages before exploring further.
/v1/hyperliquid/spot, with pair discovery, pair metadata, order books, trades, candles, L4 reconstruction surfaces, order history, TWAP, user TWAP, and freshness checks.
Start Here
Choose the pair
Use
/v1/hyperliquid/spot/pairs to discover supported pair symbols such as HYPE-USDC.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.Why 0xArchive Fits
Hyperliquid Spot builders usually need more than a one-off latest book. 0xArchive gives the same API posture as the rest of the product: authenticated REST, generated reference pages, JSON response envelopes, request IDs, pair discovery, bounded data windows, and freshness checks.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 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} |
HYPE-USDC. Use Spot candles for pair OHLCV history; use core Hyperliquid pages for perp funding, open interest, and liquidations.
Use Native Access When
Use native venue APIs directly when you only need a one-off live quote and do not need historical windows, reconstruction surfaces, freshness checks, or the same interface across Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, and Lighter.Implementation Notes
Spot symbols are pair symbols. KeepHYPE-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.