When the market moves fast, liquidations are where it shows: positions closed by force, in size, often in clusters. A tracker, a risk desk or a dashboard needs them across every account, as they happen and as they happened. This guide covers how they work on Hyperliquid, what the official API exposes, and how to get them all.
How a position is liquidated
From Hyperliquid's liquidations page:
- First, through the book. "When the account equity drops below maintenance margin, the positions are first attempted to be entirely closed by sending market orders to the book."
- Then, the backstop. "If the account equity drops below 2/3 of the maintenance margin without successful liquidation through the book, a backstop liquidation happens through the liquidator vault", a component strategy of HLP.
- No clearance fee. "Unlike CEXs there is no clearance fee on liquidations."
So a liquidation has a method, market or backstop, and that distinction is in the data.
What the official API shows
Hyperliquid's documented API reports liquidations per account:
userEvents, a WebSocket subscription for one user, carries a liquidation event with the liquidator, the liquidated user and the position's notional.- Fills of a liquidated account carry a
liquidationfield with the method, market or backstop. - Ledger updates of an account list the liquidation and the positions it closed.
Each of these takes a user. The subscriptions list no channel for liquidations across all accounts, and the public trade feed carries no liquidation flag. To see the market's liquidations, you have to know every account in advance, or read them from an index.
Every liquidation, on a key
Hypedexer indexes liquidations across all accounts from its own nodes.
The history, filtered by coin, account, size and time, newest first by default:
curl -H "X-API-Key: $HYPEDEXER_KEY" \
"https://api.hypedexer.com/liquidations/?coin=ETH&amount_dollars=100000&limit=100"Each row carries the time, the coin, the liquidated account, the size and notional, the fill VWAP and mark price, the method, the liquidators and their count, the direction and the transaction hash. Pages chain with next_cursor and has_more, up to 1,000 rows per call (reference).
The live stream, on the WebSocket:
{"method": "subscribe", "subscription": {"type": "liquidations"}}It replays the latest cached events, then streams new ones as they happen, grouped per liquidated account and time (reference).
The stats, for a dashboard tile: GET /analytics/liquidations/stats?days=1 returns the number of liquidations, longs and shorts, the USD amount, the fees and the most liquidated token, over 1 to 30 days, for one coin or all.
Coverage, measured
Liquidations are served from 22 March 2025, with one gap: no rows are served from 25 May to 8 November 2025. Both dates are measured on Research, where every family's range is checked against the live API rather than announced. For a backtest that crosses the gap, plan for it rather than read zero liquidations into it.
FAQ
How do I track Hyperliquid liquidations in real time? Subscribe to the liquidations channel on the Hypedexer WebSocket: it replays the latest events, then streams each new one.
Can I see every liquidation on Hyperliquid, not just mine? Yes, with an index: Hyperliquid's documented API reports them per account; GET /liquidations/ lists them across all accounts.
How far back does liquidation history go? To 22 March 2025, with no rows from 25 May to 8 November 2025.
What is a backstop liquidation? When an account's equity falls below two thirds of its maintenance margin and the book could not close it, the liquidator vault, part of HLP, takes the position over.