Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt

Use this file to discover all available pages before exploring further.

Historical market data work starts when one live 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

Data familyTypical useStart
Order booksDepth-aware research, liquidity analysis, local book seedsOrder Book Routes
Trades and liquidationsFlow, realized activity, stress windowsTrades And Liquidations
Funding, OI, candlesPerp context, trend windows, model featuresFunding, Open Interest, And Candles
Orders and L4 lifecycleReconstruction, order changes, TP/SL and flowOrders And L4 Lifecycle Routes
ReplayEvent order, incident review, deterministic playbackWebSocket Backtesting
ExportsFile-style research or warehouse loadingData Catalog

​
Historical Request Packet

Every historical pull should carry the same request packet from the first curl command through the final file or chart.
FieldExample
Venue familyHyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter
SymbolBTC, HYPE-USDC, km:US500, HIP-4 outcome ID, or Lighter market symbol
Data familyorder book, trades, candles, funding, OI, liquidations, L3, L4, orders, or replay
Time windowexplicit start and end, usually Unix milliseconds for REST history routes
Paginationcursor chain, page limit, and final meta.next_cursor state
Quality statecoverage, freshness, incidents, gaps, and any decision to stop or mark output
If that packet 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

0xArchive is strongest 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 gates. Use a broad vendor when the primary need is many unrelated exchanges or asset classes. Use a native venue API when the job is official venue behavior rather than managed historical retrieval.

​
Output Choice

Use API responses when the application needs live 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 May 18, 2026