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