Hyperliquid Spot

Hyperliquid Spot lives under /v1/hyperliquid/spot. Use pair symbols such as HYPE-USDC for Spot routes and keep Spot routing separate from perp symbols such as BTC.

Route Family

Data family	REST path pattern	Use
Pairs	`/v1/hyperliquid/spot/pairs`	List Spot pairs
Pair metadata	`/v1/hyperliquid/spot/pairs/{symbol}`	Inspect one Spot pair
Order book	`/v1/hyperliquid/spot/orderbook/{symbol}`	Pull current Spot depth
Order book history	`/v1/hyperliquid/spot/orderbook/{symbol}/history`	Pull historical Spot L2 snapshots
Trades	`/v1/hyperliquid/spot/trades/{symbol}`	Pull bounded historical trades
Candles	`/v1/hyperliquid/spot/candles/{symbol}`	Pull OHLCV candles for pair-level history
L4 checkpoint	`/v1/hyperliquid/spot/orderbook/{symbol}/l4`	Start reconstruction from a checkpoint
L4 diffs	`/v1/hyperliquid/spot/orderbook/{symbol}/l4/diffs`	Apply book diffs over time
L4 history	`/v1/hyperliquid/spot/orderbook/{symbol}/l4/history`	Pull historical resting-book reconstruction windows
Order history	`/v1/hyperliquid/spot/orders/{symbol}/history`	Inspect separate historical order-lifecycle records
TWAP	`/v1/hyperliquid/spot/twap/{symbol}`	Query symbol-level TWAP surfaces
User TWAP	`/v1/hyperliquid/spot/twap/user/{user}`	Query user-scoped TWAP surfaces
Freshness	`/v1/hyperliquid/spot/freshness/{symbol}`	Gate downstream jobs on freshness

Example

curl "https://api.0xarchive.io/v1/hyperliquid/spot/orderbook/HYPE-USDC?depth=10" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

import os
import requests

resp = requests.get(
    "https://api.0xarchive.io/v1/hyperliquid/spot/trades/HYPE-USDC",
    headers={"X-API-Key": os.environ["OXARCHIVE_API_KEY"]},
    params={"limit": 50},
    timeout=30,
)
resp.raise_for_status()
payload = resp.json()
print(payload["meta"]["request_id"])

Implementation Notes

Gate reconstruction jobs

For L4 work, start with a checkpoint route, apply diffs in order, and keep the request ID in logs when a checkpoint is not available for the requested timestamp.

Check freshness before automation

Use the freshness route before alerting, trading research, exports, or model input jobs depend on Spot results.

Spot Request Checklist

Use this checklist before a Spot route enters application code, a generated client, or an agent workflow.

Field	Spot-family value
Namespace	`/v1/hyperliquid/spot/*`
Symbol style	Pair symbols such as `HYPE-USDC`
First probe	Pair metadata, order book, trades page, candles page, or freshness route
Reconstruction inputs	L4 checkpoint, diffs, history window, and request IDs when order-level behavior matters
Do not mix with	Core perp symbols, HIP-3 builder prefixes, HIP-4 outcome IDs, or Lighter symbols

Freshness And Empty Results

Some Spot data families can be present for the route while a specific pair or timestamp has no available checkpoint or no returned records. Treat that as normal market-data behavior, not as permission to fabricate a book. Check /v1/hyperliquid/spot/freshness/{symbol} before reconstruction or automation jobs and preserve the error request_id when a checkpoint is unavailable for the requested timestamp.

Next Step

Open Endpoint Reference, then pair this page with Venue coverage, Data quality, and Historical market data.

Get started

Market data

Get connected

Plans & limits

Route Family

Example

Implementation Notes

Spot Request Checklist

Freshness And Empty Results

Next Step

​Route Family

​Example

​Implementation Notes

​Spot Request Checklist

​Freshness And Empty Results

​Next Step

Route Family

Example

Implementation Notes

Spot Request Checklist

Freshness And Empty Results

Next Step