> ## 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 Historical Data API

> Lighter historical market data: tick-level order books, L3 order-level depth, trades, funding, and open interest over REST, replay, and Parquet export.

0xArchive serves Lighter as a separate venue under `/v1/lighter/*`. Coverage includes trades, funding, and open interest from August 2025, tick-level order books from January 2026, and L3 order-level depth from March 2026, across more than 200 markets, continuous to the current hour.

Lighter is not part of the Hyperliquid namespace. Keep Lighter symbols and routes separate from Hyperliquid core, Spot, HIP-3, and HIP-4.

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

<CardGroup cols={2}>
  <Card title="Lighter REST" icon="layer-group" href="/rest-api/lighter">
    Lighter route family.
  </Card>

  <Card title="Lighter quickstart" icon="play" href="/lighter-api-quickstart">
    First Lighter request.
  </Card>
</CardGroup>

## What History Is Available

| Route family                  | Earliest     | Detail                                                |
| ----------------------------- | ------------ | ----------------------------------------------------- |
| Trades                        | August 2025  | Per-trade records; more than 1 billion records        |
| Funding and open interest     | August 2025  | Per-interval history to the current hour              |
| Order books (tick L2)         | January 2026 | Tick-level book updates; more than 39 billion records |
| Order books (L3, order-level) | March 2026   | Per-order depth, user-addressed                       |

Lighter trade history begins August 2025; order-level (L3) detail begins March 2026. Hold one symbol and one UTC window constant on the first pull, then widen.

## 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](/openapi) plus [Lighter REST](/rest-api/lighter) so it keeps Lighter routes separate from Hyperliquid.

## Next Step

Open [Lighter REST](/rest-api/lighter), then use [Data quality](/data-quality) before widening to more markets.