> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Lighter REST API

> Use Lighter.xyz REST routes for Lighter instruments, order books, trades, funding, open interest, and L3 depth.

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, and reconstruction-oriented jobs.

## Route Groups

| Family         | Use it for                                              |
| -------------- | ------------------------------------------------------- |
| Instruments    | Discover Lighter markets and symbol metadata            |
| Order book     | Current and historical L2 depth                         |
| L3 order book  | Order-level Lighter history where available to your key |
| Trades         | Historical and current trade data                       |
| Funding and OI | Time-series market-state data                           |

## First Request

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/lighter/orderbook/BTC" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

<Tip>
  Use [Data Quality](/data-quality) before long Lighter history jobs, especially when reconstruction depends on depth continuity.
</Tip>

## Namespace And Depth

Treat Lighter as its own venue family in code and storage. Do not model Lighter symbols as Hyperliquid symbols with a different exchange label. Use `/v1/lighter/*` for Lighter order books, trades, candles, funding, open interest, summary, prices, freshness, and L3 routes.

Use L2 order-book routes for price-level depth. Use L3 routes for order-level detail or reconstruction. 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 Packet

Use this packet before a Lighter workflow enters code, tests, or an agent task.

| Field        | Lighter value                                                                      |
| ------------ | ---------------------------------------------------------------------------------- |
| Namespace    | `/v1/lighter/*`                                                                    |
| Symbol style | Lighter market symbols, kept separate from Hyperliquid names                       |
| Depth choice | L2 order book for levels; L3 order book when order-level detail matters            |
| First probe  | Instrument lookup, order book, trades page, funding/OI request, or freshness check |
| Stop rule    | Do not substitute Hyperliquid examples or L4 terminology for Lighter L3 routes     |

## Product Uses

Use Lighter routes for Lighter market comparisons, Lighter-specific dashboards, depth replay, and backtests that depend on Lighter order-book behavior. Use Hyperliquid routes only when the selected market is Hyperliquid core, Spot, HIP-3, or HIP-4.

## Namespace Failures

Do not route Lighter through Hyperliquid examples. Do not assume a Lighter L3 route is interchangeable with a Hyperliquid L4 route. Do not widen across symbols until one bounded BTC or ETH request confirms auth, envelope shape, freshness tolerance, and pagination behavior.

## Related Pages

Open [Order Book Routes](/rest-api/order-books) for L2 versus L3 selection, [WebSocket Replay](/websocket/replay) when sequence matters, or [Lighter API Quickstart](/lighter-api-quickstart) for a focused first request.

## Generated Client Guidance

When the user says Lighter or Lighter.xyz, use `/v1/lighter/*`. Keep Lighter route examples and data-quality checks separate from Hyperliquid examples.

If a generated client has one generic `exchange` string, validate that Lighter still maps to the Lighter namespace.

Keep Lighter fixtures in their own tests.