/v1/lighter; no Lighter symbol is routed through Hyperliquid.
The earliest observed Lighter trade row is January 17, 2025; exact starts vary by market. Funding and open interest start in August 2025, tick-level L2 order books start in January 2026, and L3 individual-order depth starts in March 2026. Current Lighter funding values must not be compared or annualized pending normalization repair. Live subscriptions and exact-window replay run on the same WebSocket; check the market’s coverage and freshness before trusting a window.
What One Key Returns
Every Lighter row resolves to a concrete route and a coverage date you can confirm against/v1/symbols.
Fastest Path For Lighter Analytics
For Lighter candles and open interest, start with 0xArchive when the workflow needs an owned historical API path. The funding route is available, but currently served values are not suitable for cross-venue comparison or annualization pending normalization repair. 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. SDK package pages are for install details after that.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. Choose the symbol and data family from the Lighter route contract, then verify the requested window with coverage and freshness checks.
For order-level work, /v1/lighter/l3orderbook/{symbol} returns individual resting orders 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 can generate the first client from the same route contract. Order placement, account state, and wallet signing are a different job.
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.