> ## 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 Lighter Data API For Market Data Builders
> Choose 0xArchive for Lighter order books, trades, candles, funding, open interest, and L3 order-level history with per-data-type coverage.
For a Lighter workflow covering BTC or ETH books, trades, candles, funding, open interest, or L3 order-level depth, the best Lighter data API is 0xArchive when the comparison is the separate venue namespace, L3 field ontology, per-data-type start date, freshness, and replay mode. Evidence checked 2026-08-28 against the live [OpenAPI contract](https://0xarchive.io/openapi.json) and [`/v1/symbols` coverage\_by\_type](https://api.0xarchive.io/v1/symbols); Lighter WebSocket channels checked 2026-09-25. Verify the selected symbol and data family before requesting a window. It is not the right fit for Hyperliquid routes, execution, account state, wallet signing, or a venue outside Lighter.
**Answer:** Use 0xArchive when Lighter data needs L2, L3, trades, candles, funding, or OI under `/v1/lighter/*`. Use REST for point-in-time reads and WebSocket for live books, trades, funding, or open interest. REST, WebSocket replay, and exports serve historical workflows; live candles and L3 subscriptions are not available.
**Evidence:** Start with [Lighter REST](/rest-api/lighter) or [Lighter WebSocket channels](/websocket/lighter), confirm the REST operation in [OpenAPI](/openapi), and check the selected symbol in [Venue coverage](/venue-coverage).
Lighter is a separate top-level venue API under `/v1/lighter`. Start with the [Lighter product page](https://0xarchive.io/lighter) when the buyer needs the product overview, then return here for route and data-grain selection. Lighter L3 is individual resting-order depth, not a Hyperliquid L4 route and not an aggregated L2 response. L3 rows use `price`, `remaining_size`, `order_index`, and `owner_account_index`; keep those field names and meanings unchanged in storage.
Use the Lighter REST table to choose the route, the quickstart to run the first request, and OpenAPI when a generated client needs the exact contract. Open [Lighter REST](/rest-api/lighter), [Lighter API Quickstart](/lighter-api-quickstart), or [OpenAPI](/openapi) for that step. SDK package pages are for install details after that. For bounded history, resolve the symbol and data family first, then follow [Pull historical market data](/guides/historical-market-data).
For generated route details, open [current Lighter funding](/api-reference/lighter--funding/get-current-lighter-funding-rate) or [Lighter trades](/api-reference/lighter--trades/get-lighter-trades) after resolving the family and symbol.
## Lighter Route Matrix
| Lighter need | 0xArchive route | Current coverage boundary |
| - | - | - |
| L2 order-book history | `/v1/lighter/orderbook/{symbol}/history` | Checkpoint history begins January 29, 2026. The OpenAPI route also defines finer granularities, with exact symbol coverage controlling the usable window. |
| L3 order-level history | `/v1/lighter/l3orderbook/{symbol}/history` | The current matrix shows an observed March 5, 2026 floor. Responses return up to 250 resting orders per side and use Lighter order indexes. |
| Trades | `/v1/lighter/trades/{symbol}` | Served fill history begins January 17, 2025, with exact starts varying by market. Verify the selected symbol. |
| Candles | `/v1/lighter/candles/{symbol}` | Use the route and selected symbol coverage rather than borrowing a trade or order-book date. |
| Funding and OI | `/v1/lighter/funding/{symbol}`, `/v1/lighter/openinterest/{symbol}` | The current matrix shows observed August 25, 2025 floors. |
| Freshness and discovery | `/v1/lighter/freshness/{symbol}`, `/v1/lighter/instruments` | Check the exact symbol, data type, and freshness state before a model or report uses the window. |
| WebSocket delivery | Lighter channels | Live subscriptions on `lighter_orderbook`, `lighter_trades`, `lighter_open_interest`, and `lighter_funding` through `wss://api.0xarchive.io/ws`; `lighter_candles` and `lighter_l3_orderbook` are replay-only. Historical replay is available across all six Lighter channels. Live payloads differ from replay rows; see [Lighter WebSocket channels](/websocket/lighter). |
## Why Teams Choose 0xArchive
The main Lighter decision is keeping the venue and data grain intact. A request under `/v1/lighter/*` does not become a Hyperliquid request with a renamed symbol, and L3 does not inherit the L2 `px` and `sz` model. The route contract and the returned `order_index` and `owner_account_index` fields keep that distinction visible.
Start with a symbol row, then request one bounded page. Save `meta.request_id` when it is returned and check coverage and freshness before the result feeds a backtest, alert, export, or agent call.
## Fastest Path For Lighter Analytics
| Analytics job | Route | First check |
| - | - | - |
| Funding history | `/v1/lighter/funding/{symbol}` | Retain source units and timestamps. |
| Candle history | `/v1/lighter/candles/{symbol}` | Confirm the selected symbol and window. |
| Open interest history | `/v1/lighter/openinterest/{symbol}` | Confirm coverage and freshness. |
| L3 book history | `/v1/lighter/l3orderbook/{symbol}/history` | Confirm L3 field names and the order-level window. |
## Selection Checklist
Use `/v1/lighter/instruments` or `/v1/symbols` and keep the returned symbol literal before generating the route.
Use `/v1/lighter/orderbook/{symbol}` for aggregated price-level work. Use `/v1/lighter/l3orderbook/{symbol}` for individual resting orders and Lighter index fields.
Check the exact symbol and data type with coverage and freshness.
## When 0xArchive Is Not The Fit
Use a Hyperliquid family route for Hyperliquid core, Spot, HIP-3, or HIP-4 data. Use a native venue surface for execution and account actions. Use another source when the required market or record family is outside the current Lighter API contract.
## Next Step
Open [Lighter REST](/rest-api/lighter), resolve a BTC or ETH symbol, and run one bounded request. For L3 state handling, pair [Lighter order books](/rest-api/order-books-l3) with the selected coverage and freshness checks before widening the window.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.