Get Liquidation Density
Hyperliquid liquidation density near the mark, as a time series.
Per coin per point: mark, and for bands of ±0.5 / 1 / 2 / 3 / 5% of mark the USD of long positions liquidating BELOW the mark (long_below) and shorts liquidating ABOVE it (short_above) — plus the same split by trader_type (vault, market_maker, whale, smart_money, high_leverage, other) and by leverage bucket (3/5/10/20/25/40/50/100x). Derived from the archived liquidation_levels
- liquidation_map snapshots: ~2 KB a point instead of ~1 MB a snapshot. History starts 2026-06-26 (the full-universe feed); ≤ 93 days per call. CSV carries the all-account bands only. Pro Plus.
Request
- Base URL: https://cryptodataapi.com
- URL: https://cryptodataapi.com/api/v1/backtesting/liquidation-density
- Auth: API key in header X-API-Key
Query parameters
One HL coin name (BTC, HYPE, kPEPE) or a comma list (up to 25).
Start time (ISO 8601 or unix ms)
End time (ISO 8601 or unix ms, defaults to now). EXCLUSIVE — the range is [start, end).
5m (every archived snapshot) or 1h (the first snapshot of each hour).
Breakdowns to include: any of trader_type, leverage (comma list), or none for the all-account bands only (~10x smaller).
Interval convention for start/end. half-open (default) is [start, end) — end is EXCLUSIVE, so consecutive windows tile without repeating a boundary row. closed is [start, end] — end INCLUSIVE, the pre-2026-08-08 behaviour; use it only to keep an existing integration byte-identical.
Opaque page cursor — the next_cursor of the previous response, verbatim. Resumes strictly after the last row served, keyed on the table's full primary key, so a page boundary inside a same-millisecond burst loses nothing (unlike start = last.time + 1). start / end still bound the window.
json or csv. CSV has no envelope: paging state travels in the X-Has-More / X-Next-Cursor response headers.
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.