Backtesting

Get Liquidations

Venue-merged liquidation totals — a ROLLING 24-HOUR level sampled every 5 minutes (OKX + Bybit + Hyperliquid), not that interval's flow.

Each row answers "how much was liquidated in the 24h ending at this sample"; summing rows, or differencing consecutive ones, does not recover a burst. For incremental 5m / 15m / 1h flow from exact fills use /backtesting/hl-liquidation-bars; for the fills themselves, /backtesting/hl-liquidations. Rows are ordered (time, symbol) and next_cursor resumes exactly there.

get/api/v1/backtesting/liquidations

Request

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

Query parameters

symbolstring

One symbol, or a comma list (BTC,ETH,SOL — up to 25; every value rides the index). Omit for all symbols.

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
symbolstring nullable required
countinteger required

Changes

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