---
title: "Get Quant Positioning Ladder"
method: GET
path: "/api/v1/quant/positioning/ladder"
tags: ["Quant"]
---

# Get Quant Positioning Ladder

`GET /api/v1/quant/positioning/ladder`

## Request

- Base URL: `https://cryptodataapi.com`
- URL: `https://cryptodataapi.com/api/v1/quant/positioning/ladder`
- Auth: API key in header `X-API-Key`

Full-universe liquidation ladder for one coin, split by account class (Pro Plus).

Every account >= $100k in the HL universe, binned on a 0.5%-of-mark grid
(clamped ±50%):

* `bins` / `flip` — all classes (the full book);
* `bins_directional` / `flip_directional` — market-maker + vault liqs
  excluded (the cleaner walls; MM liquidations are hedged noise);
* `bins_by_class` — `{market_maker, whale, other}` on the same grid; an
  account's class is its primary tag, so the three sum to `bins`;
* `levels` — the 3 nearest non-empty all-class clusters above and below
  mark: `{price, dist_pct (signed vs mark), total_usd, side (dominant
  liquidation side — long = downside fuel), n_accounts}`.

Same builder as the archived `liquidation_map` snapshot type (which carries
`bins_by_class` from 2026-09-09), so live and history agree. `positions_as_of`
is the liqmap poll cycle the ladder is built from.

## Query parameters

- `symbol` string, required: One coin, e.g. BTC or kPEPE (case-insensitive)

## Response `200`

Successful Response

- unknown

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