24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/liquidations/coin-price-liq
GETAvailable

Price line overlaid with liquidation bars for one coin

Price line overlaid with liquidation bars for one coin

GET/api/liquidations/coin-price-liq

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
coinstringRequired——Base coin symbol (uppercase, e.g. BTC). Example: BTC
rangestringOptional7d1d, 7d, 30d, 90d, allTime window. `all` covers the last 730 days; any other unknown value is treated as `7d`. Example: 7d

Example request

curl -s "https://www.coinboss.com/api/liquidations/coin-price-liq?coin=BTC&range=7d"

Response fields

The field table is generated from real responses, so it lists exactly what the endpoint returns. Paths use a[] for array items and {*} for objects keyed by a dynamic name such as a coin or an exchange.

FieldTypeUnitDescription
successboolean—true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`.
coinstring—Coin symbol, upper case (for example BTC).
rangestring—Window requested.
intervalstring—Interval.
klinesarray—Candles.
klines[]object—Candles.
klines[].open_timenumbermsTimestamp.
klines[].closenumber—Close price of the period.
liqarray—Liquidation value or block.
liq[]object—Liquidation value or block.
liq[].bucketnumbermsStart of the time bucket.
liq[].long_usdnumberUSDLong side.
liq[].short_usdnumberUSDShort side.

Generated 2026-11-11 23:00 UTC from 4 real responses.

Example response

/api/liquidations/coin-price-liq?coin=BTC&range=7d · Real response captured 2026-11-13 04:02:41 UTC. Long arrays and maps are shortened for display: liq had 169 items; klines had 167 items.

  • {
    • "success": true,
    • "coin": "BTC",
    • "range": "7d",
    • "interval": "1h",
    • "klines": [
      • { … 2 },
      • { … 2 }
      ],
    • "liq": [
      • { … 3 },
      • { … 3 }
      ]
    }

Verified samples

Besides the example above, the probe calls this endpoint with these parameters and checks the schema each time.

ParametersHTTPLatencyResult
coin=ETH&range=7d20016 msPass
coin=SOL&range=7d20015 msPass
coin=ARKM&range=7d20014 msPass

Checked 2026-11-13 03:57:56 UTC

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
60s
Edge micro-cache
10s
Update frequency
real-time (exchange WebSocket push); REST polling: okx every 15 s, gate every 25 s, htx every 5 min; hyperliquid node fill batches ingested every 5 s
Window
range param: 1d | 7d | 30d | 90d | all (all = 730 d)
Data sources
Liquidation orders collected in-house from the public liquidation feeds of 11 venues (e.g. binance, okx, bybit, gate, bitget, htx); Hyperliquid liquidations come from the fills of a self-operated Hyperliquid node.
Exchange coverage
11 venues with active collectors (binance USDT-M + COIN-M, okx, bybit linear + inverse, gate USDT + BTC settled, bitget, htx, hyperliquid, aster, lighter, bitfinex, deribit); crypto assets only (tokenized stock / index / commodity / FX contracts are routed to the separate TradFi dataset); binance pushes at most one liquidation per symbol per second, so its totals are a lower bound; minimum stored event size: 100 USD on okx / bitget / htx / bitfinex / deribit / binance COIN-M, 1 USD on gate / hyperliquid / lighter, none on binance USDT-M / bybit / aster
Units
USD notional (price x quantity) per liquidation order; timestamps in Unix ms; side LONG = long position liquidated, SHORT = short position liquidated
Method
price = kline close per bucket; liquidation long_usd / short_usd = SUM(value_usd) per same bucket
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 04:02:41 UTCHTTP 20019 msSchema matchesNewest data point 63m old

Availability, last 30 days

100% of 411 checks passed

Errors

Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →

CodeHTTPMeaningWhat to do
INVALID_PARAM400A required parameter is missing or a value is not accepted. `param` names the parameter when it is known.Do not retry unchanged; fix the request.
UNAUTHORIZED401The `CB-API-KEY` header was sent but the key is unknown or revoked. Public data needs no key — drop the header or use a valid key.Do not retry unchanged.
FORBIDDEN403The route is not part of the public API (internal or account-only).Do not retry.
NOT_FOUND404Unknown route, or the requested coin / exchange / fund does not exist.Do not retry; check the path and identifiers against the catalog.
RATE_LIMITED429More requests than the per-minute limit. `Retry-After` gives the seconds to wait.Wait for `Retry-After`, then retry with backoff.
INTERNAL500Unexpected server error. The message is generic by design; quote `request_id` when reporting it.Retry once after a few seconds; report it with the request id if it persists.
UPSTREAM_FAILED503The data source behind this endpoint did not answer in time. No stale or substitute numbers are returned in its place.Retry with backoff; check the status page.
UNAVAILABLE501 / 503The dataset is temporarily not ready (cache warming) or the endpoint has no lawful public source yet.Retry later; the catalog marks endpoints that are unavailable by design.
REQUEST_FAILED200Some older endpoints answer HTTP 200 with `success: false`. Always check `success`, not only the HTTP status.Depends on the message; treat as a failed request.

Try it

GET/api/liquidations/coin-price-liqAvailable
Parameters

string — Base coin symbol (uppercase, e.g. BTC).

string · default 7d — Time window. `all` covers the last 730 days; any other unknown value is treated as `7d`.

Request URLhttps://www.coinboss.com/api/liquidations/coin-price-liq?coin=BTC&range=7d
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.