X-API-Key header.
Make one request
With your key inOXARCHIVE_API_KEY, this returns the best bid and ask for BTC:
200:
https://api.0xarchive.io. Market-data routes answer with { success, data, meta } and a meta.request_id. Errors answer with success: false, a stable error_code, and a top-level request_id. A few auth, system, wallet, and data-quality routes return their own body; the endpoint page shows it. GET /health is unauthenticated liveness and does not check your key. The Quickstart walks through the same call and the errors you are most likely to see.
Pull history
Pull historical market data walks one bounded window page by page, with the cursors and request IDs that make it reproducible. The Free plan covers the most recent 30 days; longer history needs Build or above.Choose the endpoint family
Each market type has its own namespace. Pick it first, then the dataset.
Datasets: order books (L2, L3, and L4), trades, candles, funding, open interest, liquidations, orders, account positions, and data quality. Account positions sit under the same namespaces:
/wallets/{address}/positions on Hyperliquid and HIP-3, and /accounts/{account_index}/positions on both Lighter deployments.
Venue coverage shows which datasets each market type has, and from when. Start with one symbol and a short UTC window before widening a job.
Requests and responses
Parameters
Symbols, time windows, intervals, depth, limits, and filters.
Pagination
Cursors and resumable backfills.
Responses
The success shape and every field in it.
Errors
Status codes, retry timing, and request IDs.
Rate limits
Requests, credits, and concurrency per plan.
OpenAPI
Every operation, parameter, and schema, for code generation.