https://0xarchive.io/data.
Use the catalog when the job is a bulk historical pull or a file you load into a warehouse or notebook. Use REST or WebSocket when the product needs live or programmatic calls.
Export a dataset
Choose a market
Open
/data and pick a market. The catalog separates Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, and Lighter; browse everything, a curated category, or jump straight to one market’s page.Choose the schemas
Check the data types you want for that market: L2 order book, L3 individual orders, L4 order-level book, order events, trades, funding, open interest, and liquidations. Availability depends on the market, and each schema shows its estimated size and price inline.
Choose a UTC date range
Pick a preset (30D, 90D, 1Y, All) or a custom range. All dates are UTC. Ranges are bounded by coverage; settled HIP-4 outcomes stop at their settlement date, and live markets default the end date to today.
Review the estimate
The cart shows size, row count, subtotal, any subscriber credits applied, any volume discount, and the Total today. Authenticated users see credits before a card is charged.
After you order
Your order lands in the dashboard at/dashboard/exports/:id and moves through Awaiting Payment, Queued, Processing, and Ready to Download. Most exports are ready in a minute or two. Files are Apache Parquet with ZSTD compression; download links last 7 days and a completed order stays available for 30 days. Export checkout covers the states and recovery in detail.
What you can export
Each schema is priced per gigabyte with a per-schema minimum. See Export schemas for the full matrix, coverage keys, and rough columns.Browse by category
The catalog groups markets into curated categories:| Category | Website slug |
|---|---|
| Popular exports | popular-exports |
| Popular equities | equities |
| Crypto majors | crypto |
| Commodities | commodities |
| Indices and FX | indices-fx |
| Pre-IPO markets | pre-ipo-markets |
| HIP-4 BTC outcomes | hip4-outcome-markets |
| Hyperliquid crypto | hyperliquid |
| Lighter crypto | lighter |
/data/markets/hip4/btc-daily-outcomes rather than a generated market slug.
Export order checklist
Keep these with the files so an order stays traceable after purchase.| Field | Why |
|---|---|
| Market and venue family | Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter use different symbol and coverage rules |
| Schema keys | l2_orderbook, l3_orderbook, l4_orderbook, l4_orders, trades, funding, oi, and liquidations produce different files |
| UTC date range | Coverage, estimates, and reproducibility depend on the start and end dates |
| Estimate or quote | Size, rows, price, and credit application explain what was bought |
| Delivery state | Dashboard status, file format, and download links explain readiness |
| Data-rights decision | Review the redistribution boundary before shipping files to customers or partners |
Programmatic discovery
Most people never need this section. It is for building market pickers or export checklists in code, not for running an export. Machine-readable symbol discovery comes fromhttps://api.0xarchive.io/v1/symbols. The response is an object with a top-level symbols array. Use each row’s exchange, symbol, slug, data_types, and coverage fields when building market pickers or export checklists. Do not use website-local API-shaped paths such as /api/v1/*/symbols as symbol feeds; those paths belong to the website shell, not the public market-data API. The symbols feed is live product catalog data, but it is not part of the generated OpenAPI REST reference.
The live feed returns rows for hyperliquid, spot, hip3, hip4, and lighter. Useful fields on a symbol feed row:
| Field | Use |
|---|---|
coverage_by_type | Choose the earliest valid date for each selected schema, by coverage key (orderbook, l3_orderbook, l4_orderbook, l4_orders, trades, funding, oi, liquidations) |
size_per_day | Estimate export size before checkout |
coverage_to | Cap settled-market export end dates; live markets without it default the end date to today |
is_settled, is_active | Preserve settled and active state for HIP-4 outcomes and delisted markets |
/data/markets/:venueSlug/:marketSlug — for example hyperliquid-spot for Spot. Market slugs are generated from venue plus symbol state and include a route hash, so docs and agents should carry the route the UI or a symbol feed row supplies (it is route-specific public metadata) rather than inventing a market URL from a plain symbol.
Related pages
Export schemas
Schema labels, data types, columns, pricing units, and coverage keys.
Export checkout
Quote, credits, checkout, login return, and dashboard job behavior.
Data rights
Decide whether an export is internal use, derived use, or redistribution.
Markets
Bridge chart-first pages, catalog routes, and API route families.