Recipe 3 of 65
Was this wallet liquidated? Hyperliquid liquidation history by wallet
Pass the address to /liquidations as wallet and you get every liquidation recorded for it, newest first; an empty list means none was recorded.
GET /v1/hyperliquid/liquidations answers it in one call with wallet set: every liquidation recorded for that
address, newest first, with the market, the side that was closed, the size and the mark price. A wallet with none gets
an empty list and a null cursor, not an error. The full parameter list is on
Liquidations.
Quick answer
Pass the address as wallet.
# every liquidation recorded for one wallet, newest first
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/hyperliquid/liquidations?wallet=0xffbdde0c5392ae87f4a56c2095787e96fb241546&limit=5"Example response
Captured from the live API on 2026-10-24 at 17:15 UTC: the whole answer, one row. label_computed is cut to its first keys and the legacy
asset copy of symbol is left out.
This wallet lost a 0.05124 BTC long, about $4,000 of notional, on 2026-09-03. side is the side of the position that
was closed, so long means a long was liquidated as price fell. nextCursor is null, so there is no older row.
{
"liquidations": [
{
"liq_ts": "2026-09-03T07:54:00+00:00",
"wallet": "0xffbdde0c5392ae87f4a56c2095787e96fb241546",
"symbol": "BTC",
"side": "long",
"size_token": 0.05124,
"size_usd": 3997.28364,
"mark_price": 78011.0,
"size_cohort": null,
"pnl_cohort": "unknown",
"pnl_cohort_basis": "point_in_time"
}
],
"label_computed": {
"grading": "realized",
"lookahead": false,
"resolution": "hourly"
},
"nextCursor": null
}Variations
One market, one period. Add symbol, start and end to check a single position or a single day.
# this wallet's BTC liquidations in September 2026
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/hyperliquid/liquidations?wallet=0xffbdde0c5392ae87f4a56c2095787e96fb241546&symbol=BTC&start=2026-09-01T00:00:00Z&end=2026-10-01T00:00:00Z&limit=100"Only longs or only shorts. direction filters on the side that was closed.
# only the long positions this wallet lost to liquidation
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/hyperliquid/liquidations?wallet=0xffbdde0c5392ae87f4a56c2095787e96fb241546&direction=long&limit=100"Is it close to liquidation now? The history says nothing about open risk. Read the wallet's open positions and their liquidation prices.
# the wallet's open positions with liquidation price and liq_progress
curl -H "X-API-Key: $VIKE_API_KEY" \
"https://data.vike.io/v1/hyperliquid/positions?wallet=0xffbdde0c5392ae87f4a56c2095787e96fb241546&limit=200"Before you rely on it
A row is a position that vanished near its liquidation price
Current rows are detected from position snapshots taken about every 5 minutes: a position over $100 that was within 5%
of its liquidation price in one snapshot and is gone in the next. So liq_ts is the snapshot time, and size_usd and
mark_price are the last values seen before it vanished. A position closed by hand near its liquidation price is
counted, while a partial liquidation, or one that came in a move faster than the 5% band, is missed.
An empty list is not proof
Liquidation history reaches back to 2026-01-01. An empty list means no liquidation was recorded for the address in that period, under the detection rule above. The route does not check that the address ever traded.
Ask your agent
Connected to the Vike MCP server (https://vike.io/mcp) in Claude, ChatGPT or Cursor, ask it in plain words.
The hl_liquidations tool answers with view: fills and the wallet, at 1 credit a call.
Has Hyperliquid wallet 0xffbdde0c5392ae87f4a56c2095787e96fb241546 ever been liquidated?