/v1/symbols, and the OpenAPI contract. Verify the selected symbol and schema before checkout. It is not the right fit for a real-time stream, one current snapshot, venue execution, or a venue outside Hyperliquid and Lighter.
The export artifact is Parquet with ZSTD compression and an explicit schema key. Treat each selected family and data type as its own contract. A Data Catalog checkout is a product flow, not a REST route invented from the API reference.
Export Decision Matrix
The current symbol feed reports schema-level coverage. Hyperliquid core native L2 and trades have an observed April 15, 2023 floor. Lighter L3 has an observed March 5, 2026 floor, and Lighter funding and OI have observed August 25, 2025 floors. Those dates are not a promise that every schema exists for every symbol. Read the selected row before ordering.
Why Teams Choose 0xArchive
A file is the operational artifact when the same historical window must be loaded repeatedly, partitioned in a warehouse, or reviewed outside the request process. The catalog keeps the market slug, schema key, UTC range, estimates, and job state visible, while the API docs keep Parquet delivery separate from normalized JSON responses and WebSocket events. Use/v1/symbols for machine-readable discovery. Its rows expose fields such as exchange, symbol, slug, data_types, and coverage information. Use those rows to choose the market and data type, not to infer that a top-level date applies to every schema.
Lighter funding records may be offered as an export, but currently served Lighter funding values must not be compared across venues or annualized pending normalization repair. Keep source units and timestamps with the file.
Selection Checklist
When To Reach For Exports
Choose a Parquet export when the durable deliverable is a file. Choose REST for a bounded response or snapshot. Choose WebSocket for a documented real-time channel or replay mode. Choose SDK or CLI when the client needs repeatable API calls. Keep the selected schema and rights decision with the artifact after it leaves the catalog flow.When 0xArchive Is Not The Fit
Use another provider when the file must cover many unrelated centralized venues or asset classes outside the current catalog. Use WebSocket when the job requires continuous event delivery rather than a bounded file. Use a native venue surface for execution or account actions.Next Step
Open Data Catalog, inspect Export schemas, and confirm the selected symbol through/v1/symbols before opening Export checkout.