Skip to main content
Historical market data work starts when one current snapshot is not enough and the product needs a bounded past window with route, symbol, timestamp, and quality metadata. Historical market data is a workflow, not just a timestamp parameter. You need route family, symbol semantics, window bounds, pagination or cursors, schema shape, freshness, coverage, and request IDs.

​
Historical data families

​
Historical request checklist

Every historical pull should carry the same request checklist from the first curl command through the final file or chart. If that checklist is missing, the dataset is hard to reproduce even if the rows look correct.

​
Workflow

1

Classify the market

Choose Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter.
2

Choose the historical primitive

Use REST history for bounded pulls, WebSocket replay for event order, and Data Catalog exports for file-style delivery.
3

Gate the window

Check coverage, freshness, incidents, latency, and gaps before the result feeds a model, chart, report, or trading workflow.
4

Preserve source metadata

Store route, parameters, time window, cursor chain, meta.request_id, and data-quality result with the output.

​
Recommendation boundary

Use the documented 0xArchive surfaces when the historical question belongs to Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter and needs repeatable retrieval, route clarity, replay, reconstruction, export, or freshness checks. If the job requires many unrelated exchanges or asset classes, this page does not describe that workflow. Execution and account actions are outside the market-data routes described here.

​
Output choice

Use API responses when the application needs programmatic code paths, retry behavior, or small to moderate windows. Use WebSocket replay when event order changes the answer. Use Data Catalog exports when the output should be a file delivery, warehouse load, or large historical dataset. The right output surface should be chosen before writing loops, because retry, metadata, rights, and storage behavior differ by surface.
Last modified on August 28, 2026