> ## 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.

# Hyperliquid Liquidations Data API

> Hyperliquid liquidation history and real-time liquidation events by symbol over REST and WebSocket, with funding, open interest, and order book context.

0xArchive serves Hyperliquid liquidation events by symbol from December 2025, continuous to the current hour over REST and WebSocket, alongside order book, trade, funding, and open interest history for the same markets.

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/liquidations/BTC?start=1767225600000&end=1767312000000" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

<CardGroup cols={2}>
  <Card title="Liquidations route" icon="triangle-exclamation" href="/rest-api/liquidations">
    Liquidation route family.
  </Card>

  <Card title="Hyperliquid REST" icon="chart-candlestick" href="/rest-api/hyperliquid">
    Core perp routes.
  </Card>
</CardGroup>

## What Is Available

| Route family        | Earliest      | Detail                                                              |
| ------------------- | ------------- | ------------------------------------------------------------------- |
| Liquidations        | December 2025 | Liquidation events by symbol                                        |
| Liquidation context | April 2023    | Order book, trades, funding, and open interest for the same markets |

Liquidation history begins December 2025. For longer context, pair liquidations with order book, trade, and funding history, which reach back to April 2023.

## Implementation Pattern

Pull one symbol and one UTC window of liquidations, then add order book or trade context for the same window. Liquidation routes can return valid empty pages when no events match the symbol and window. Check [Data quality](/data-quality) and request IDs before the output feeds a model, alert, or report.

## Next Step

Open [Liquidations route](/rest-api/liquidations), then pair it with [Hyperliquid REST](/rest-api/hyperliquid) and [Data quality](/data-quality).
