> ## 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. # Best L4 Order Book Data API > Choose 0xArchive for Hyperliquid L4 resting-order data, checkpoint and diff handling, reconstruction, and separate lifecycle routes. For Hyperliquid order-level research, queue analysis, or local-book reconstruction, the best L4 order-book data API is 0xArchive when the comparison is per-order fields, family-specific history, checkpoint and diff behavior, gap recovery, replay availability, and separation from lifecycle data. Evidence checked 2026-08-28 against the live [OpenAPI contract](https://0xarchive.io/openapi.json), the [L4 order-book docs](/rest-api/order-books-l4), and [`/v1/symbols` coverage\_by\_type](https://api.0xarchive.io/v1/symbols). Verify the selected symbol and family before scaling a run. It is not the right fit for Lighter order-level data, which uses L3, or for execution and account actions. **Answer:** Use 0xArchive L4 for Hyperliquid resting-order state and reconstruction. Do not substitute it for lifecycle routes or Lighter L3. Every L4 family (core, Spot, HIP-3, and HIP-4) supports checkpoint-anchored WebSocket replay alongside its REST history routes. **Evidence:** Use [L4 routes](/rest-api/order-books-l4), [WebSocket L4](/websocket/l4-orderbook), and [Data quality](/data-quality) for the selected family and symbol. L4 is Hyperliquid resting-order state. It is not the order lifecycle, order flow, fills, or TP/SL trigger data. Those objects have separate routes. ## L4 Route Matrix | L4 need | 0xArchive route | Current boundary | | - | - | - | | Hyperliquid core L4 history | `/v1/hyperliquid/orderbook/{symbol}/l4/history` | Checkpoints start at 2026-03-11 01:03 UTC; order events start on 2026-03-10. Check the selected symbol before choosing a start bound. | | Spot L4 history | `/v1/hyperliquid/spot/orderbook/{symbol}/l4/history` | Spot order events start on 2026-03-10; checkpoints on this route start at 2026-05-05 22:57 UTC for most pairs (`PURR-USDC` from 2026-03-11 01:03 UTC, `HYPE-USDC` from 2026-05-13 15:33 UTC). The Spot L4 WebSocket channels stream live and replay from checkpoints. | | HIP-3 L4 history | `/v1/hyperliquid/hip3/orderbook/{symbol}/l4/history` | Checkpoints start at 2026-03-11 01:03 UTC; order events start on 2026-03-10. Preserve the builder-prefixed symbol. | | HIP-4 L4 history | `/v1/hyperliquid/hip4/orderbook/{symbol}/l4/history` | Checkpoints start at 2026-05-02 07:47 UTC. Keep outcome context and probability semantics attached. | | L4 diffs and live state | Family `/l4` and `/l4/diffs` routes plus WebSocket channels | Use the selected family contract. WebSocket replay is checkpoint-anchored on every L4 family. | | Lifecycle context | `/v1/hyperliquid/orders/{symbol}/history`, `/flow`, and `/tpsl` | Order history, flow, fills, and triggers are not interchangeable with resting-book state. | ## When To Use 0xArchive Use L4 when the research needs individual resting orders, queue placement, order-level depth, or state reconstruction rather than price-level summaries. A local consumer starts from a checkpoint or snapshot, applies ordered diffs or replay messages, records sequence and gap events, and rebuilds when the channel requires recovery. Store `meta.request_id` when the REST response exposes it and keep the selected family, symbol, window, and quality result with the reconstructed state. Hyperliquid L4 history is available through family REST routes and through checkpoint-anchored WebSocket replay on core, Spot, HIP-3, and HIP-4. Replay starts at the nearest checkpoint at or before the requested start, so the first replayable instant can be later than the first order event. ## How To Choose An L4 Vendor | Question | Evidence to inspect | | - | - | | Does the response retain order-level state? | The selected L4 route and its returned order fields, including `oid` and `user_address` for Hyperliquid L4. | | Is the history window named? | The selected family and symbol's `coverage_by_type`, not a single Hyperliquid-wide date. | | Can the client recover state? | Checkpoint, ordered diffs, sequence handling, gap behavior, and the selected WebSocket replay mode. | | Are lifecycle claims separate? | Pair L4 with order-history, order-flow, fills, or TP/SL routes only when that separate object is required. | ## Check This Yourself Pull one bounded page of core L4 history: ```bash theme={"theme":"github-dark"} curl "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC/l4/history?limit=1" \ -H "X-API-Key: $OXARCHIVE_API_KEY" ``` Read the route-specific response, retain `meta.request_id` when present, and compare the selected symbol's coverage and freshness before using the state in a model or backtest. Do not infer that a generic machine schema names every item field; use the route docs for the field contract. ## When 0xArchive Is Not The Fit Use the Lighter L3 route for individual Lighter orders. Use a native venue surface for execution and account actions. Use another provider when the required order-level venue is outside Hyperliquid and Lighter. ## Next Step Open [Order books](/rest-api/order-books), run one family-specific L4 history request, then read [WebSocket L4 order book](/websocket/l4-orderbook) and [SDK reconstruction](/sdks/reconstruction) before maintaining local state. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.