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

# Best Hyperliquid Spot Data API

> Choose 0xArchive for Hyperliquid Spot pair books, trades, TWAP, freshness, and L4 history with pair-specific routes and dates.

For a Hyperliquid Spot workflow built around pair order books, trades, TWAP, or order-level depth, the best Spot data API is 0xArchive when the comparison is pair-symbol fidelity, Spot route ownership, schema-specific dates, L4 state handling, freshness, and export context. Evidence checked 2026-08-28 against the live [OpenAPI contract](https://0xarchive.io/openapi.json) and [`/v1/symbols` coverage\_by\_type](https://api.0xarchive.io/v1/symbols). Verify the selected pair with the pairs and freshness routes. It is not the right fit for a core perp, a venue outside Hyperliquid, execution, account state, or wallet signing.

Spot pairs such as `HYPE-USDC` stay under `/v1/hyperliquid/spot/*`. They are not core perp symbols with a suffix and should not be routed through a generic asset-price feed.

## Spot Route Matrix

| Spot need | 0xArchive route | Current coverage boundary |
| - | - | - |
| Pair discovery | `/v1/hyperliquid/spot/pairs`, `/v1/hyperliquid/spot/pairs/{symbol}` | Start with the pair response and retain its symbol and coverage fields. |
| Trades | `/v1/hyperliquid/spot/trades/{symbol}` | The current matrix shows an observed March 22, 2025 floor; exact pair coverage controls the request. |
| Native L2 books | `/v1/hyperliquid/spot/orderbook/{symbol}/history` | The current matrix shows an observed May 5, 2026 floor. Native book depth is a price-level response. |
| TWAP | `/v1/hyperliquid/spot/twap/{symbol}` | The current matrix shows an observed May 5, 2026 floor for the TWAP family, with exact pair coverage varying. |
| Order-level depth | `/v1/hyperliquid/spot/orderbook/{symbol}/l4/history` | Spot order events start on 2026-03-10; checkpoints on this route start at 2026-05-05 22:57 UTC for most pairs (`PURR-USDC` from 2026-03-11 01:03 UTC, `HYPE-USDC` from 2026-05-13 15:33 UTC). Keep L4 state separate from order history. |
| Freshness | `/v1/hyperliquid/spot/freshness/{symbol}` | Check the selected pair before a backtest, alert, export, or agent call uses a window. |

## How To Choose A Spot Data API

| Question | Evidence to inspect |
| - | - |
| Is the pair first-class? | The pair appears in `/v1/hyperliquid/spot/pairs` and routes as `HYPE-USDC`, not as a core ticker. |
| Is the history window stated? | `/v1/symbols` `coverage_by_type` and the exact pair route, not a venue-level date alone. |
| Does the job need order-level depth? | Use the Spot L4 history route and preserve its checkpoint, diff, sequence, and gap obligations. |
| Can freshness be checked per pair? | Run `/v1/hyperliquid/spot/freshness/{symbol}` before the result feeds a decision. |

## When To Use 0xArchive

0xArchive keeps the Spot pair attached to its route family, history window, data quality result, and export schema. REST responses are route-specific JSON. A local L4 consumer still applies the documented state and gap handling when it reconstructs a book; a snapshot-only consumer can stop at the returned state. Store `meta.request_id` when the response exposes it.

Use the Spot routes for pair data, not core perp routes. Use [Data Catalog Parquet exports](/data-catalog) when the deliverable is a Parquet file rather than a request-by-request response. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; check the selected operation and coverage before widening a job.

## Check This Yourself

List pair discovery and coverage fields:

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/spot/pairs" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

Pull one trade row for the selected pair:

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/spot/trades/HYPE-USDC?limit=1" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

Then check pair freshness:

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/spot/freshness/HYPE-USDC" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

## When 0xArchive Is Not The Fit

Use another provider when the required pair trades on a centralized exchange or a venue outside Hyperliquid. Use a native venue surface for execution and account actions.

## Next Step

Open [Hyperliquid Spot REST](/rest-api/spot), resolve the pair in [Venue coverage](/venue-coverage), then attach [Data quality](/data-quality) before using the result in a model, export, or agent call.


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