Skip to main content
Lighter coverage is schema-specific. Per-fill trade rows begin August 27, 2025; exact starts vary by market, and the rows carry maker/taker attribution. Funding and open interest have observed floors of August 25, 2025 at roughly 10-second resolution. Native L2 order books have an observed floor of January 29, 2026. Tick-level L3 individual-order depth starts March 5, 2026 with a cap of 250 orders per side. Lighter is not part of the Hyperliquid namespace. Keep Lighter symbols and routes separate from Hyperliquid core, Spot, HIP-3, and HIP-4. For a family-level view, see Lighter live and historical data, then return here for the route contract.

Lighter REST

Lighter route family.

Lighter quickstart

First Lighter request.

What History Is Available

Lighter per-fill trade rows begin August 27, 2025, and exact starts vary by market. L3 individual-order depth begins March 5, 2026 and is capped at 250 orders per side per tick. 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. L2 routes return aggregated price levels with px/sz decimal-string fields and n order counts. The L3 route returns individual resting orders with numeric order_index, owner_account_index, price, remaining_size, and original_size fields; it does not inherit the L2 px/sz level shape. Those index fields are numeric Lighter indexes, not wallet addresses or raw order IDs. Funding and open-interest routes use their documented resource shapes; do not assume they share an identical envelope or interval basis.

Implementation Pattern

Start with one Lighter symbol such as BTC, 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.

Next Step

Open Lighter REST, run the trade request above, then use Data quality and Venue coverage before widening to more markets. For a ranked read on Lighter coverage, see Best Lighter Data API.
Last modified on September 11, 2026