Export schemas - 0xArchive

Export schemas are the contract between Data Catalog selections and downstream files for L2, L3, L4, trades, funding, open interest, and liquidation exports. Export schemas describe file-style historical datasets. They are related to API response schemas, but they are not the same thing. API schemas describe JSON responses. Export schemas describe Parquet datasets, coverage keys, estimated size, pricing units, and the columns a buyer should expect.

Export Format

Data Catalog exports are delivered as Apache Parquet with ZSTD compression. Date ranges use UTC dates. Schema availability depends on venue family, market, coverage, and plan or purchase path. The cart matrix below covers the current selectable file schemas; individual market pages can expose a narrower set based on coverage.

Schema Matrix

Schema key	Label	Coverage key	Rough columns	Public pricing unit
`l2_orderbook`	L2 Order Book	`orderbook`	`timestamp`, symbol, bids, asks, mid price, spread	`$6/GB`, `$10 minimum`
`l3_orderbook`	Individual-Order Book (L3)	`l3_orderbook`	timestamp, symbol, individual orders, bid/ask counts, mid price, spread	`$6/GB`, `$10 minimum`
`l4_orderbook`	Order-Level Book (L4)	`l4_orderbook`	book changes and saved states with user address, side, price, size, change type, snapshots	`$8/GB`, `$25 minimum`
`l4_orders`	Order Events / TP/SL	`l4_orders`	timestamp, symbol, user address, order ID, status, side, price, size, order type	`$8/GB`, `$25 minimum`
`trades`	Trades	`trades`	timestamp, symbol, side, price, size, trade ID, user address, fee, direction	`$8/GB`, `$15 minimum`
`funding`	Funding Rates	`funding`	timestamp, symbol, funding rate, premium	`$1/GB`, `$5 minimum`
`oi`	Open Interest	`oi`	timestamp, symbol, open interest, mark price, oracle price	`$1/GB`, `$5 minimum`
`liquidations`	Liquidations	`liquidations`	timestamp, symbol, liquidated user, price, size, side, mark price, direction	`$8/GB`, `$25 minimum`

Candles and order flow have no standalone export schema. For files, export trades and aggregate to candles, or export l4_orders and aggregate to order flow. Schema availability is per venue: l2_orderbook and trades exist on every venue; l3_orderbook is Lighter-only; l4_orderbook and l4_orders are Hyperliquid-family only; liquidations is core and HIP-3 only; funding is core, HIP-3, and Lighter; oi is core, HIP-3, HIP-4, and Lighter. The cart shows the selectable set for each market. Lighter funding records are exportable where the cart offers that schema, but currently served values must not be compared across venues or annualized pending normalization repair.

Export Schema Checklist

Use this checklist before mapping an export to a warehouse table or model input.

Decision	Rule
Book depth and order events	Keep L2 price-level snapshots, L3 individual-order depth, L4 resting-book records, and separate order-event records in distinct tables unless a downstream model explicitly joins them.
Coverage key	Use the schema coverage key when checking availability; `l2_orderbook` maps to `orderbook`, and `oi` maps to open-interest coverage.
Venue family	Preserve Hyperliquid core, Spot, HIP-3, HIP-4, or Lighter in every file manifest and table partition.
Date range	Store UTC start/end dates and the coverage window used for the estimate.
Pricing unit	Record rate and minimum alongside the quote so a later order can explain cost changes.
Rights context	Attach the Data Rights decision for the transformation/source-exposure test and any benchmark, index, financial-product, raw-redistribution, standalone/substitute, white-label, or OEM use.

Coverage And Range Rules

Catalog schema availability starts from the symbols feed row. A schema is selectable when the row’s data_types includes the schema key, the schema coverage key, or a documented alias. l2_orderbook maps to orderbook, and oi can map to open-interest coverage when an upstream surface uses that name. For each selected schema, use coverage_by_type[schema.coverageKey] when it exists, then fall back to coverage_from. When multiple schemas or HIP-4 outcome sides are selected together, the valid export start date is the latest coverage start across the selected rows and schemas. For settled HIP-4 outcomes, cap the export end date at coverage_to; for live markets, use today as the default end date. The Data Catalog defaults to a 90-day range when coverage allows it, otherwise it uses all available history. Custom ranges still have to stay inside the selected schema coverage window. Hyperliquid core trades and liquidations, plus Hyperliquid Spot trades, should not be requested before 2025-03-22 through the export flow even when a broader market row has older coverage metadata.

How Schemas Map To API Concepts

Order-book exports can represent different depths. L2 snapshots are not L3 individual orders or L4 per-order book records. L4 order-book and separate L4 order-event exports should stay distinct from ordinary order-book JSON responses in code, warehouses, and docs. Trades, liquidations, funding, and open interest can have different coverage starts for the same market. HIP-4 exports need side and event context. Outcome prices should be treated as probability-like values, not ordinary USD prices. HIP-3 exports need the builder prefix preserved. Spot exports need pair symbols. Lighter exports should stay under the Lighter venue family.

Choosing Schemas

Start with the research question

If the question only needs top-of-book or daily aggregates, do not default to L4.

Check coverage by schema

Schema history can differ within the same market.

Estimate size before checkout

High-depth schemas can be much larger than funding or OI datasets.

Store schema keys with output

A downstream warehouse table should know the schema key and venue family that produced it.

Use Data catalog for the product flow, Schemas for JSON response schemas, Export manifest schemas for generator-backed export manifest JSON Schema, and Data rights for benchmark, index, financial-product, raw-redistribution, standalone/substitute, white-label, or data-as-product OEM use.

​Export Format

​Schema Matrix

​Export Schema Checklist

​Coverage And Range Rules

​How Schemas Map To API Concepts

​Choosing Schemas

​Related Pages