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.

Use Hyperliquid core routes for standard perp market history. Use HIP-3 and HIP-4 pages when the market belongs to a builder-perp or outcome-market family.

Hyperliquid REST

Core perp route family.

Historical guide

Bounded pull pattern with freshness checks.
curl "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC?timestamp=1767225600000&depth=20" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

​
Why 0xArchive Fits

Hyperliquid historical work usually needs more than one latest quote. 0xArchive gives core perp builders route-stable REST history, generated OpenAPI reference pages, WebSocket replay guidance, reconstruction docs, and data-quality checks in one portal. Use this page for core perp symbols such as BTC and ETH. Use Hyperliquid Spot Data API for pair symbols such as HYPE-USDC, HIP-3 Data API for namespaced builder markets, and HIP-4 Data API for outcome markets.

​
Core Perp Route Map

NeedRoute family to inspect first
Current or timestamped depth/v1/hyperliquid/orderbook/{symbol}
Historical depth snapshots/v1/hyperliquid/orderbook/{symbol}/history
Trades/v1/hyperliquid/trades/{symbol}
Funding and open interest/v1/hyperliquid/funding/{symbol} and open-interest routes
Candles/v1/hyperliquid/candles/{symbol}
Liquidations/v1/hyperliquid/liquidations/{symbol}
Order-level workL4 and orders routes where the plan and route support them
For timestamped order-book snapshots, use Unix milliseconds for timestamp. For historical trade windows, use Unix milliseconds for start and end.

​
Historical Workflow

Start with one bounded order-book or trade request, then add candles, funding, open interest, liquidations, or L4 routes as the job requires. Store route, query parameters, cursors, timestamps, and request IDs with output. Gate downstream use with Data Quality before the data feeds research, alerts, dashboards, exports, or models.

​
Evaluation Packet

Before comparing 0xArchive to a native venue pull, hold one symbol, one window, and one downstream job constant. Record the route, parameters, returned span, cursor chain, request IDs, data-quality result, and any gap or incident notes. That packet makes the second run easier to compare than a screenshot or row count.

​
Evaluation Notes

Ask whether the workflow needs point snapshots, historical records, replay order, or local reconstruction. Those are different jobs. REST history is best for bounded data pulls. WebSocket replay is best when event order matters. SDK reconstruction is best when the product maintains a local book. All three should preserve request IDs and data-quality context. For generated code, route to OpenAPI after the route family decision is made. Use this page as the intent layer and OpenAPI as the contract layer. Keep data-quality checks in the first implementation pass. Use narrow windows before exports.
Last modified on May 18, 2026