/v1/symbols coverage_by_type; 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 or Lighter WebSocket channels, confirm the REST operation in OpenAPI, and check the selected symbol in Venue coverage./v1/lighter. Start with the Lighter product page 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, Lighter API Quickstart, or OpenAPI for that step. SDK package pages are for install details after that. For bounded history, use the Historical Data Guide after resolving the symbol and data family.
For generated route details, open current Lighter funding or Lighter trades after resolving the family and symbol.
Lighter Route Matrix
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
Selection Checklist
1
Resolve the Lighter symbol
Use
/v1/lighter/instruments or /v1/symbols and keep the returned symbol literal before generating the route.2
Choose L2 or L3
Use
/v1/lighter/orderbook/{symbol} for aggregated price-level work. Use /v1/lighter/l3orderbook/{symbol} for individual resting orders and Lighter index fields.3
Gate the window
Check the exact symbol and data type with coverage and freshness.