---
title: "Get Hl Liquidation Bars"
method: GET
path: "/api/v1/backtesting/hl-liquidation-bars"
tags: ["Backtesting"]
---

# Get Hl Liquidation Bars

`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`

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).

## Query parameters

- `coin` string: 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.
- `interval` string: Bucket width: 5m, 15m or 1h (UTC clock-aligned)
- `start` string, required: Start time (ISO 8601 or unix ms); floored to the interval
- `end` string: End time (ISO 8601 or unix ms, defaults to now); floored to the interval, EXCLUSIVE
- `bounds` string: 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.
- `limit` integer
- `cursor` string, 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.
- `format` string: json or csv. CSV has no envelope: paging state travels in the `X-Has-More` / `X-Next-Cursor` response headers.

## Response `200`

Successful Response

- BacktestHLLiquidationBarsResponse
  - `grain` GrainDescriptor: What ONE ROW of a series is, stated on the payload so it cannot be mis-summed. ``kind``: ``event`` (one fill), ``bar`` (a closed bucket), ``rate_snapshot`` (the live rate sampled on a timer), ``rolling_window`` (a trailing total sampled on a timer), ``settled_payment`` (one settlement print). ``sum_ok`` — adding rows across time is meaningful. ``is_cumulative`` — a row already contains its predecessors' flow. ``settlements_per_day`` is set for funding series only.
    - `kind` string, required
    - `cadence` string, nullable
    - `is_cumulative` boolean
    - `sum_ok` boolean
    - `window` string, nullable
    - `settlements_per_day` integer, nullable
    - `note` string, required
  - `coverage` CoverageInfo: Local retention bounds (ms) for the queried scope. ``archive_hint`` is set when the window starts before ``local_first`` — those rows are not missing, they live in the daily Parquet archive.
    - `local_first` integer, nullable
    - `local_last` integer, nullable
    - `archive_hint` string, nullable
  - `next_cursor` string, nullable
  - `has_more` boolean
  - `coin` string, nullable, required
  - `interval` string, required
  - `count` integer, required
  - `data` BacktestHLLiquidationBar[], required
    - `time` integer, required
    - `coin` string, nullable
    - `long_usd` number, required
    - `short_usd` number, required
    - `total_usd` number, required
    - `n_long` integer, required
    - `n_short` integer, required
    - `max_fill_usd` number, nullable
  - `audit` object, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/cryptodataapi/apis/crypto-data-api.md) · [All operations](https://skmtc.dev/cryptodataapi/apis/crypto-data-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cryptodataapi/apis/crypto-data-api/revisions/8628b754ca81?raw)