https://api.0xarchive.io, includes X-API-Key, and returns either a success/data/meta envelope or a JSON error with a request handle. GET /health is unauthenticated liveness and should not be used as an API-key check.
The data map lives in Data, and coverage lives in Market data: one page per data type, each with a venue switch and REST, WebSocket, and export access. This tab is the REST mechanics that apply across all of them.
Parameters
Path symbols, time windows, intervals, depth, limits, and filters.
Pagination
Cursor pagination,
meta.next_cursor, and resumable backfills.Response envelope
The
{ success, data, meta } shape and the field dictionary.Data conventions
Decimal strings vs numbers, UTC timestamps, and the
coin alias.Errors & retries
Status codes,
Retry-After, and request IDs for safe retries.Reliability
Retries, request-ID logging, concurrency, and data-quality gating.
Rate limits
Per-tier request limits and credits, and how to stay inside them.
OpenAPI
The generated contract: every operation, parameter, and schema.
Browse the data
What we cover by venue, with a page per data type.
Base Request
Response Envelope
Most market-data endpoints return a JSON envelope withsuccess, data, and meta. meta can include count, next_cursor, and request_id when relevant. Some auth, system, wallet, and data-quality endpoints return resource-specific bodies; check the REST reference and response headers for the exact response body. Log meta.request_id when it is present, and store route-specific status fields plus x-request-id when a response does not use the standard envelope.
Endpoint Reference
Use the Reference tab for endpoint pages with operation names, parameters, response schemas, auth, and examples, or open the OpenAPI contract directly.REST Request Checklist
Before writing code or handing a route to an agent, capture the request checklist that determines the correct family.| Field | Example |
|---|---|
| Venue family | Hyperliquid core, Spot, HIP-3, HIP-4, Lighter, or data quality |
| Symbol format | BTC, HYPE-USDC, km:US500, HIP-4 outcome ID, or Lighter symbol |
| Data family | Order books, trades, candles, funding, OI, liquidations, L3, L4, freshness, or coverage |
| Route path | Generated REST path from OpenAPI, including namespace and path parameters |
| Request bound | One symbol, one page, one short UTC window, or one status check before widening |
| Response context | Envelope, cursor, error code, decimal handling, and meta.request_id |
| Quality decision | Coverage, freshness, incidents, latency, or SLA context when downstream work depends on the result |
Route Selection Rules
Choose the route family before choosing the endpoint. Standard Hyperliquid perp symbols such asBTC and ETH use /v1/hyperliquid/*. Spot pair symbols such as HYPE-USDC use /v1/hyperliquid/spot/*. HIP-3 builder markets such as km:US500 use /v1/hyperliquid/hip3/*. HIP-4 outcome markets use /v1/hyperliquid/hip4/* and require probability-price handling. Lighter markets use /v1/lighter/*.
Endpoint reference pages define parameters and schemas. Curated pages explain which namespace to use, what the symbol format means, which data-quality check belongs near the request, and when WebSocket replay or SDK reconstruction is a better primitive than a REST list.