/v1/lighter, with order books, trades, candles, funding, open interest, freshness, and L3 order-level depth as normalized JSON. No Lighter symbol is routed through a Hyperliquid namespace.
Lighter trades, funding, and open interest go back to August 2025. Native L2 tick order books since January 2026, and L3 order-level depth since March 2026. Live WebSocket subscriptions and exact-window replay run on one socket, with a data-quality path on every response.
What One Key Returns
Every Lighter row resolves to a concrete route and a coverage date you can confirm against/v1/symbols.
| Lighter market data | 0xArchive returns | Start |
|---|---|---|
| L2 order book | Native L2 tick since January 2026 via /v1/lighter/orderbook/{symbol} | Lighter REST |
| L3 order book | Order-level depth since March 2026 via /v1/lighter/l3orderbook/{symbol} | Lighter REST |
| Trades | Since August 2025 via /v1/lighter/trades/{symbol} | Lighter REST |
| Candles | /v1/lighter/candles/{symbol} | Historical data guide |
| Funding and open interest | Since August 2025 via /v1/lighter/funding/{symbol}, /v1/lighter/openinterest/{symbol} | Historical data guide |
| Freshness | /v1/lighter/freshness/{symbol} | Data quality |
| Live stream and replay | WebSocket subscriptions for real-time data and exact-window replay on one socket | WebSocket replay |
Fastest Path For Lighter Analytics
For Lighter funding, candles, and open interest, start with 0xArchive when the workflow needs an owned historical API path. Use the Lighter REST table to pick the route, the quickstart to run the first request, and OpenAPI when a generated client needs the exact contract.| Analytics job | 0xArchive route | Start |
|---|---|---|
| Funding history | /v1/lighter/funding/{symbol} | Lighter REST |
| Candle history | /v1/lighter/candles/{symbol} | Historical data guide |
| Open interest history | /v1/lighter/openinterest/{symbol} | Lighter API Quickstart |
Why Teams Choose 0xArchive
Lighter is a top-level venue family in 0xArchive, so requests use/v1/lighter/* with their own coverage dates, not Hyperliquid routes with renamed symbols. One key returns the full Lighter record set, live and historical, normalized and named: trades, funding, and OI from August 2025, native L2 tick from January 2026, and L3 order-level depth from March 2026.
For order-level work, /v1/lighter/l3orderbook/{symbol} returns individual order-level depth you can reconstruct at any point in the window. Pair REST history with WebSocket replay when sequence and timing matter, and gate the window with a freshness check before a model acts. The OpenAPI contract pins every Lighter path, so a coding agent generates a working client on the first request. Every order, trade, and fill. One API.
Selection Checklist
Capture symbol, depth layer, data family, route path, and history window, and whether the workflow is a response, stream, replay, export, model input, or agent job. That keeps Lighter on its own namespace and lets you choose L2, L3, trades, candles, funding, or OI deliberately.Do you need L2 or L3 depth?
Do you need L2 or L3 depth?
Use
/v1/lighter/orderbook/{symbol} for L2 tick order-book work since January 2026. Use /v1/lighter/l3orderbook/{symbol} for order-level depth since March 2026.Is this for a backtest?
Is this for a backtest?
Pair REST history with Data quality and WebSocket replay when sequence and timing matter.
Will a coding agent generate the client?
Will a coding agent generate the client?
Give the agent OpenAPI first, then this page for the Lighter route-family context and coverage dates.