Lighter REST
Lighter route family.
Lighter quickstart
First Lighter request.
What History Is Available
Lighter trade history is available as early as January 2025 for supported markets; coverage varies by market. Order-level (L3) detail begins March 2026. Hold one symbol and one UTC window constant on the first pull, then widen.
What Each Row Carries
Trade rows share the{success, data, meta} envelope used across the API, with cursor pagination through meta.next_cursor and a meta.request_id per page. Lighter trades are two-tier: /v1/lighter/trades/{symbol} serves canonical history reconciled daily from the Lighter Foundation archive (source: "bucket"), and /v1/lighter/trades/{symbol}/recent serves preliminary live rows (source: "ws"). Canonical rows carry the enrichment shown in the example above; preliminary rows are a smaller set of about 14 fields without fee, tx_hash, order_id, or realized_pnl.
History requests clamp to the daily finalization watermark:
meta.finalized_through reports the latest finalized timestamp, and an end past it comes back with meta.requested_end and meta.clamped_to while the rows stay canonical only. Newer rows are on /recent, where meta.preliminary_row_count counts the preliminary rows served.
Order-book routes return px/sz/n levels in the same shape as Hyperliquid L2, and the L3 route at /v1/lighter/l3orderbook/{symbol} returns individual resting orders rather than aggregated levels, the Lighter equivalent of Hyperliquid L4. Funding and open interest carry per-interval rows with the same envelope.
Implementation Pattern
Start with one Lighter symbol such asBTC, one route, and a small window. Check coverage and freshness before the output feeds a backtest, report, alert, or model. If a coding agent writes the client, give it OpenAPI plus Lighter REST so it keeps Lighter routes separate from Hyperliquid.