Backtesting

Get Hl Liquidations

Query the per-event Hyperliquid liquidation tape.

Exact liquidation fills (market + backstop) across the full HL perp universe — time, coin, liquidated side, px, sz, USD notional, method, mark price, liquidated user and tx hash — unlike /backtesting/liquidations' venue-merged rolling-24h totals. Rows are ordered by the full (time, tid) key and next_cursor resumes exactly there: one liquidation order sweeping N book levels is N rows at ONE time, so start = last.time + 1 paging silently drops the siblings that fell past a page boundary — use the cursor.

Live capture began 2026-07-23 (coverage.local_first is authoritative); the hl_liquidations daily Parquet archive additionally holds a pilot backfill 2026-04-24 → 2026-05-05. A window that starts before local retention returns [] with coverage.archive_hint set rather than silently. Pro (Pro Plus included) since 2026-09-07; the archive itself stays Pro Plus. Bucketed flow from these fills: /backtesting/hl-liquidation-bars.

get/api/v1/backtesting/hl-liquidations

Request

  • Base URL: https://cryptodataapi.com
  • URL: https://cryptodataapi.com/api/v1/backtesting/hl-liquidations
  • Auth: API key in header X-API-Key

Query parameters

coinstring

One HL universe coin name (BTC, kPEPE) or a comma list (up to 25; every value rides the index). Omit for all coins.

startstring required

Start time (ISO 8601 or unix ms)

endstring

End time (ISO 8601 or unix ms, defaults to now). EXCLUSIVE — the range is [start, end), so consecutive windows do not repeat a boundary row.

boundsstring

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.

limitinteger
cursorstring nullable

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.

formatstring

json or csv. CSV has no envelope: paging state travels in the X-Has-More / X-Next-Cursor response headers.

Response

Successful Response

next_cursorstring nullable
has_moreboolean
coinstring nullable required
countinteger required

Changes

No recorded changes to this operation across all 1 revision of this API.