---
title: "Get Hyperliquid liquidation levels history"
method: GET
path: "/v1/hyperliquid/liquidations/{symbol}/levels/history"
tags: ["Hyperliquid - Liquidations"]
---

# Get Hyperliquid liquidation levels history

`GET /v1/hyperliquid/liquidations/{symbol}/levels/history`

## Request

- Base URL: `https://api.0xarchive.io`
- URL: `https://api.0xarchive.io/v1/hyperliquid/liquidations/{symbol}/levels/history`
- Auth: API key in header `X-API-Key`

Historical liquidation-levels snapshots (about every 5 minutes, retained from 2026-07-27), ascending by `snapshot_ts`. Cursor pagination: pass `start`/`end`/`limit` and follow `meta.next_cursor` as the `cursor` parameter. `summary=true` omits only `levels` while retaining `snapshot_ts`, `block_number`, `mid_price`, `total_long`, `total_short`, and `flagged_notional`.

## Path parameters

- `symbol` string, required

## Query parameters

- `start` union: An instant: Unix milliseconds, or an RFC 3339 string such as `2026-01-01T00:00:00Z` (encode a `+` offset as `%2B`). An unparsable value answers 400 `invalid_time_range`.
  - integer: Unix milliseconds.
  - string, date-time: RFC 3339 instant.
- `end` union: An instant: Unix milliseconds, or an RFC 3339 string such as `2026-01-01T00:00:00Z` (encode a `+` offset as `%2B`). An unparsable value answers 400 `invalid_time_range`.
  - integer: Unix milliseconds.
  - string, date-time: RFC 3339 instant.
- `cursor` string
- `limit` integer
- `summary` boolean
- `range_pct` number
- `buckets` integer
- `side` 'bid' | 'ask' | 'buy' | 'sell' | 'B' | 'A'

## Response `200`

Get Hyperliquid liquidation levels history

- ApiResponseLiquidationLevelsHistory: Paginated historical liquidation-levels snapshots, ascending by snapshot_ts. When a page is full, meta.next_cursor carries the cursor for the next page.
  - `success` boolean
  - `data` LiquidationLevelsHistoryItem[]
    - `snapshot_ts` string, required: UTC snapshot time. By default a UTC string in `YYYY-MM-DD HH:MM:SS.mmm` form. With `0xArchive-Version: 2026-10-01` an RFC 3339 UTC string with millisecond precision, and `snapshot_ts_ms` carries the instant as Unix milliseconds.
    - `snapshot_ts_ms` integer: With `0xArchive-Version: 2026-10-01` only: `snapshot_ts` as Unix milliseconds.
    - `block_number` integer, required
    - `mid_price` number, required
    - `total_long` number, required
    - `total_short` number, required
    - `flagged_notional` number, required
    - `levels` LiquidationLevelBucket[]
      - `price` number, required: Bucket center price.
      - `long_notional` number, required: USD notional of long positions projected to liquidate in this bucket.
      - `short_notional` number, required: USD notional of short positions projected to liquidate in this bucket.
      - `long_count` integer, required: Number of long positions in this bucket.
      - `short_count` integer, required: Number of short positions in this bucket.
  - `meta` ResponseMeta: Response metadata. Every 2xx JSON response carries `meta.request_id`; list payloads add `count`; cursor-paged routes add `has_more` and, when another page follows, `next_cursor`; per-symbol routes add `symbol` and `venue`. Fields that do not apply to a route are omitted.
    - `count` integer: Number of records returned
    - `has_more` boolean: Cursor-paged routes: whether another page follows. `next_cursor` is present exactly when this is `true`. A final page can be empty when the previous page was exactly full; `has_more` is `false` on it.
    - `next_cursor` string: Opaque cursor for the next page, present exactly when `has_more` is `true`. Pass it back unchanged as `cursor` with the same filters. Do not parse or construct it.
    - `request_id` string, uuid, required: Unique request ID for support
    - `symbol` string: Per-symbol routes: the canonical public symbol the response describes (for example `BTC`, `xyz:TSLA`, `HYPE-USDC`, `#0`).
    - `venue` 'hyperliquid' | 'hip3' | 'hip4' | 'spot' | 'lighter' | 'rh-lighter': Per-symbol routes: the venue the response describes.
    - `coverage_from` string, date-time: Earliest coverage for the requested symbol and data type. Present only when the requested window ends before coverage begins.
    - `notice` string: Human-readable advisory about the response. Used when the requested window ends before coverage begins for the symbol, and on CVD responses that are one page of several; may carry other advisories in future.
    - `finalized_through` string, date-time: Two-tier datasets (Lighter trades): data at or before this instant is final; later data is preliminary.
    - `requested_end` string, date-time, nullable: The `end` the request asked for, echoed when it was clamped to `finalized_through`.
    - `clamped_to` string, date-time, nullable: The boundary the request's `end` was clamped to, when clamping occurred.
    - `preliminary_row_count` integer, nullable: Number of preliminary rows in this response, on routes that intentionally serve preliminary data (Lighter `/recent`).

## Other responses

- `400`: Invalid request: a parameter, symbol, interval, cursor or time range failed validation. See `error_code`.
- `401`: Authentication required: the API key is missing or invalid.
- `403`: The request is outside the plan's history window or per-request span, or the key is not allowed to make it.
- `429`: Rate limit, concurrency limit or monthly credits exceeded. See `error_code`.
- `default`: Any other error. The body is an `ErrorResponse`; branch on `error_code`. A 503 (`upstream_unavailable`) carries `Retry-After`.

---

[API](https://skmtc.dev/0xarchive/apis/0xarchive-api-2.md) · [All operations](https://skmtc.dev/0xarchive/apis/0xarchive-api-2/llms.txt) · [OpenAPI document](https://skmtc.dev/0xarchive/apis/0xarchive-api-2/revisions/27076f55595f?raw)