Hyperliquid Liquidations Data API

0xArchive serves completed Hyperliquid liquidation events by symbol on /v1/hyperliquid/liquidations/{symbol}. BTC and ETH currently reach 2025-07-27; other symbols have their own coverage_by_type.liquidations start. These rows are real forced executions, not estimates. Projected forced-liquidation price-level endpoints and pending TP/SL trigger concentrations are separate routes described below. For a practical liquidation workflow, use the Hyperliquid liquidations guide, then return here for the exact route contract.

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

{
  "success": true,
  "data": [
    {
      "coin": "BTC",
      "timestamp": "2026-06-04T14:00:02.429Z",
      "liquidated_user": "0x32fe14732b5b54dc08c6eee46b9ba319ca38e9f4",
      "liquidator_user": "0xd4bb18ef8d1bc1bfadfcc034ca69628b58b42a4c",
      "side": "A",
      "price": "64234",
      "size": "0.03929",
      "mark_price": "64215",
      "closed_pnl": "15.719929",
      "direction": "Close Long",
      "trade_id": 77865977922623,
      "tx_hash": "0x0bf847b31c71cf920d72043d23653902065a0098b774ee64afc0f305db75a97c"
    }
  ],
  "meta": { "count": 1, "next_cursor": "1780581602429_228090607300425", "request_id": "req_9f1c0a7e5b2d4480" }
}

Liquidations route

Liquidation route family.

Hyperliquid REST

Core perp routes.

What Each Row Carries

Every liquidation is a real forced execution, not an estimate, and each row names both sides of it:

Field	What it tells you
`liquidated_user`	The wallet whose position was closed
`liquidator_user`	The wallet or vault on the other side of the forced fill
`side`	`B` (buy) or `A` (sell), the direction of the forced execution
`price` and `size`	Execution price and size, decimal strings
`mark_price`	The mark at the moment the event fired
`closed_pnl`	Realized PnL on the closed position
`direction`	Position effect, such as `Close Long`
`trade_id` and `tx_hash`	Join keys back to the trade tape and the chain transaction

Responses use the same {success, data, meta} envelope as every other route, with cursor pagination through meta.next_cursor and a meta.request_id per page.

Routes And Windows

Liquidation question	Route
Events for one symbol and window	`/v1/hyperliquid/liquidations/{symbol}`
Long and short volume in time buckets	`/v1/hyperliquid/liquidations/{symbol}/volume`
Projected forced-liquidation price-level endpoints computed from positions and margin state (snapshots about every 45 minutes)	`/v1/hyperliquid/liquidations/{symbol}/levels`
Pending stop-loss and take-profit trigger orders bucketed around price	`/v1/hyperliquid/orders/{symbol}/trigger-levels`
Everything one wallet liquidated or was liquidated for	`/v1/hyperliquid/liquidations/user/{user}`
HIP-3 builder markets	`/v1/hyperliquid/hip3/liquidations/{symbol}`

Completed liquidation history is symbol-specific: BTC and ETH currently reach 2025-07-27, while other symbols have their own coverage_by_type.liquidations start. For longer context, pair completed events with order-book, trade, funding, and open-interest history for the same markets, checking each data type’s coverage window; the fill tape behind each event lives on Hyperliquid Fills Data API and the book it executed against on Hyperliquid Order Book Data API.

Stream Liquidations Live

The liquidations WebSocket channel streams forced executions as they happen, with the same row shape as the REST route, so an alerting client and a historical study share one parser. Connection handling lives in the WebSocket tab.

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; an empty page in a quiet hour is data, not an error. Check Data quality and request IDs before the output feeds a model, alert, or report, and confirm the per-symbol window on Venue coverage before a backtest assumes one.

Next Step

Open Liquidations route for the full route contract, then pair it with Hyperliquid REST and Data quality.

Get started

Market data

Get connected

Plans & limits

Hyperliquid Liquidations Data API

Liquidations route

Hyperliquid REST

What Each Row Carries

Routes And Windows

Stream Liquidations Live

Implementation Pattern

Next Step

Liquidations route

Hyperliquid REST

​What Each Row Carries

​Routes And Windows

​Stream Liquidations Live

​Implementation Pattern

​Next Step

What Each Row Carries

Routes And Windows

Stream Liquidations Live

Implementation Pattern

Next Step