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.
See Get market data to choose between API access and Parquet exports. Use Venue coverage to confirm support. This page covers the REST API; WebSocket has its own connection, streaming, and replay guides.
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.
Check venue coverage
Available data types, API namespaces, and observed history by market 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 a client integration, capture the fields that determine the correct API namespace.Route selection rules
Choose the API namespace before choosing the endpoint. Standard Hyperliquid perpetual 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/*, and Lighter on Robinhood Chain markets, from Lighter’s second deployment, use /v1/rh-lighter/*. Account positions sit under the same namespaces: /wallets/{address}/positions on Hyperliquid and HIP-3, /accounts/{account_index}/positions on both Lighter deployments. See Account positions.
Endpoint reference pages define parameters and schemas. The market-type 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 fit than a REST list.