Lighter Is Its Own Venue API
0xArchive treats Lighter as its own top-level venue, not a Hyperliquid add-on. Lighter routes live under /v1/lighter/*, so Lighter symbols, depth semantics, and exports stay separate from Hyperliquid core, Spot, HIP-3, and HIP-4. If you already use our Hyperliquid routes the shape is familiar; only the namespace changes.
What's covered
- Order books - L2 price-level depth, tick-level.
- Trades - BTC and ETH trade history from 2025-01-17 (other markets vary), with more than 1.8 billion fills
- Funding and open interest - full time-series market state.
- Candles - OHLCV history at supported intervals.
- Replay and exports - WebSocket replay and Data Catalog Parquet files.
Lighter coverage includes 200+ markets. BTC and ETH trade history starts on 2025-01-17; exact starts vary by market. Live fills were captured from 2025-08-27. Live counts are on the status page.
Why a separate venue
Lighter gives cross-venue desks a second 24/7 book to test against Hyperliquid. Keep it in its own route family when you compare depth, trades, funding, or replay windows across the two venues, so a Lighter L3 route never gets mistaken for a Hyperliquid L4 one.
Run one route
Confirm auth and the envelope on one bounded request, then widen the window:
# Current Lighter order book
curl "https://api.0xarchive.io/v1/lighter/orderbook/BTC?depth=100" \
-H "X-API-Key: $OXARCHIVE_API_KEY"
# Historical Lighter order book
curl "https://api.0xarchive.io/v1/lighter/orderbook/BTC/history?start=1756252800000&end=1756339200000&granularity=10s" \
-H "X-API-Key: $OXARCHIVE_API_KEY"
# Lighter trades
curl "https://api.0xarchive.io/v1/lighter/trades/ETH?start=1756252800000&end=1756339200000" \
-H "X-API-Key: $OXARCHIVE_API_KEY"Granularity options
For Lighter order-book history, choose your resolution:
- checkpoint - ~60 second intervals (default)
- 30s - 30 second intervals
- 10s - 10 second intervals
- 1s - 1 second intervals
- tick - raw checkpoint plus deltas
Export path
For files, use the Data Catalog: pick the Lighter market, schemas, and UTC range, then check out.