Skip to main content
Plan a historical pull before you write the loop: the route, the symbol, the time window, how you page through it, and the quality checks the window must pass. A past window is only reproducible when that context travels with the rows.

​
Historical data families

​
What to record with every pull

Carry the same fields from the first request through to the final file or chart. Without them, a dataset is hard to reproduce even when 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 Bulk Exports from the Data Catalog 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 the route, parameters, time window, cursor chain, meta.request_id, and data-quality result with the output.

​
Choose the output

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 Bulk Exports when the output should be a file delivery, a warehouse load, or a large historical dataset. Choose the output before writing loops, because retry, metadata, rights, and storage behavior differ between them.

​
Next step

Pull your first bounded window with Pull historical market data.
Last modified on October 6, 2026