Skip to main content
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. 
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:
FieldWhat it tells you
liquidated_userThe wallet whose position was closed
liquidator_userThe wallet or vault on the other side of the forced fill
sideB (buy) or A (sell), the direction of the forced execution
price and sizeExecution price and size, decimal strings
mark_priceThe mark at the moment the event fired
closed_pnlRealized PnL on the closed position
directionPosition effect, such as Close Long
trade_id and tx_hashJoin 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 questionRoute
Events for one symbol and window/v1/hyperliquid/liquidations/{symbol}
Long and short volume in time buckets/v1/hyperliquid/liquidations/{symbol}/volume
Liquidation levels around the current price/v1/hyperliquid/liquidations/{symbol}/levels
Everything one wallet liquidated or was liquidated for/v1/hyperliquid/liquidations/user/{user}
HIP-3 builder markets/v1/hyperliquid/hip3/liquidations/{symbol}
Liquidation history begins December 2025. For longer context, pair liquidations with order book, trade, and funding history for the same markets, which reach back to April 2023; 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.
Last modified on July 4, 2026