Backtesting

Get Hl Liquidation Bars

Incremental liquidation flow per closed bucket, summed from the exact Hyperliquid fill tape — the burst clock /backtesting/liquidations' rolling-24h level cannot give you.

Each row is one UTC clock-aligned interval bucket: long_usd / short_usd (notional liquidated on each side), total_usd, n_long / n_short (fills) and max_fill_usd. Buckets with no fills are not returned. start and end are floored to the grid, so the bucket containing now is never served — its fills are still forming and live on /backtesting/hl-liquidations. Omit coin for one market-wide row per bucket (coin null, window ≤ 31 days); give a coin or comma list for per-coin rows (window ≤ 93 days).

Every bar is auditable: the audit block says how to pull the raw fills that summed to it. Same tier as the tape (Pro, Pro Plus included).

get/api/v1/backtesting/hl-liquidation-bars

Request

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

Query parameters

coinstring

One HL coin name (BTC, kPEPE) or a comma list (up to 25) for per-coin bars. Omit for ONE market-wide series summed over every perp.

intervalstring

Bucket width: 5m, 15m or 1h (UTC clock-aligned)

startstring required

Start time (ISO 8601 or unix ms); floored to the interval

endstring

End time (ISO 8601 or unix ms, defaults to now); floored to the interval, EXCLUSIVE

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
intervalstring required
countinteger required
auditobject required

Changes

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