Skip to main content
Lighter is a separate top-level venue family, not a Hyperliquid namespace. Use /v1/lighter/* for Lighter market data, L2 depth, L3 order-level history, trades, candles, funding, open interest, liquidations, and reconstruction-oriented jobs.

​
Route Groups

FamilyUse it for
InstrumentsDiscover Lighter markets and symbol metadata
Order bookCurrent and historical L2 depth
L3 order bookOrder-level Lighter history where available to your key
TradesHistorical and current trade data
Funding and OITime-series market-state data
LiquidationsLiquidation events and volume buckets

​
First Request

curl "https://api.0xarchive.io/v1/lighter/orderbook/BTC" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

{
  "success": true,
  "data": {
    "coin": "BTC",
    "symbol": "BTC",
    "timestamp": "2026-06-05T17:09:50.450Z",
    "bids": [
      { "px": "61363.2", "sz": "0.41549", "n": 1 },
      { "px": "61363.1", "sz": "0.20367", "n": 1 }
    ],
    "asks": [
      { "px": "61363.3", "sz": "0.00014", "n": 1 },
      { "px": "61363.4", "sz": "0.0002", "n": 1 }
    ],
    "mid_price": "61363.25",
    "spread": "0.1",
    "spread_bps": "0.0163"
  },
  "meta": { "request_id": "req_1a6f3b08c5d24e79" }
}
Lighter L2 matches the Hyperliquid order-book shape (px/sz/n as decimal strings; see the field dictionary). The difference is depth: Lighter also serves an order-level L3 book at /v1/lighter/l3orderbook/{symbol}, individual orders rather than aggregated levels, closer to Hyperliquid L4 than to L2.
Use Data quality before long Lighter history jobs, especially when reconstruction depends on depth continuity.

​
Choosing Depth

Use L2 order-book routes for price-level depth. Use the L3 route at /v1/lighter/l3orderbook/{symbol} for order-level detail or reconstruction; it returns individual orders, the Lighter equivalent of Hyperliquid L4. For long windows, begin with one bounded request, paginate deliberately, and store meta.request_id per page. Pair Lighter history with data-quality checks when the output feeds a backtest, model, alert, dashboard, or export.

​
Lighter Request Checklist

Use this checklist before a Lighter workflow enters code, tests, or an agent task.
FieldLighter value
Namespace/v1/lighter/*
Symbol styleLighter market symbols, kept separate from Hyperliquid names
Depth choiceL2 order book for levels; L3 order book when order-level detail matters
First probeInstrument lookup, order book, trades page, funding/OI request, liquidation page, or freshness check
Stop ruleDo not substitute Hyperliquid examples or L4 terminology for Lighter L3 routes

​
Generated Client Guidance

When the user says Lighter or Lighter.xyz, map to /v1/lighter/* and keep Lighter fixtures and data-quality checks in their own tests. If a generated client has one generic exchange string, confirm Lighter still resolves to the Lighter namespace rather than a relabeled Hyperliquid symbol. Open Order book routes for L2 versus L3 selection, Lighter Historical Data API for August 2025+ history boundaries, WebSocket replay when sequence matters, Lighter API Quickstart for a focused first request, or Best Market Data API for broader evaluation context.
Last modified on June 29, 2026