/api/liquidations/coin-stats
GETAvailable

Liquidation statistics for one coin

Liquidation statistics for one coin (long/short share, averages, largest order)

GET/api/liquidations/coin-stats

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
coinstringRequired——Base coin symbol (uppercase, e.g. BTC). Example: BTC

Example request

curl -s "https://www.coinboss.com/api/liquidations/coin-stats?coin=BTC"

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).
dataobject—Payload.
data.largestobject—Largest entries.
data.largest.exchangestring—Exchange id, lower case (for example `binance`).
data.largest.symbolstring—Instrument symbol as normalised by CoinBoss (for example BTCUSDT).
data.largest.sidestring—Side of the liquidated position (`long` = a long was liquidated).
data.largest.pricestring(decimal)—Last price in the quote currency (USD or USDT unless stated).
data.largest.value_usdstring(decimal)USDNotional of the liquidation: price × qty × contract multiplier.
data.largest.timestampnumbermsTimestamp.
data.currentobject—Current value.
data.current.totalstring(decimal)—Total.
data.current.t0numbermsTime of the earliest liquidation of the coin in the last hour; null when there was none.
data.current.t1numbermsTime of the latest liquidation of the coin in the last hour; null when there was none.
data.current.cntnumber—Number of liquidation orders.
data.avg7dnumberUSDAverage daily liquidated notional of the coin: total of the last 7 days ÷ 7, all exchanges.
data.avg30dnumberUSDAverage daily liquidated notional of the coin: total of the last 30 days ÷ 30, all exchanges; understated when history is shorter.
data.pricenumber—Last price in the quote currency (USD or USDT unless stated).

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

Example response

/api/liquidations/coin-stats?coin=BTC · Real response captured 2026-11-13 03:57:56 UTC.

  • {
    • "success": true,
    • "coin": "BTC",
    • "data": {
      • "largest": { … 6 },
      • "current": { … 4 },
      • "avg7d": 225998819.292857,
      • "avg30d": 161709550.748,
      • "price": 68933.3
      }
    }

Verified samples

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

ParametersHTTPLatencyResult
coin=ETH200397 msPass
coin=SOL200154 msPass
coin=ARKM2007 msPass

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

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
30s
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
24 h, 7 d and 30 d rolling windows
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
avg7d = 7-day total / 7; avg30d = 30-day total / 30; largest single order in window; reference price = latest 1 h kline close (fallback: last liquidation price)
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:57:56 UTCHTTP 200487 msSchema matchesNewest data point 7s old

Availability, last 30 days

99.76% of 410 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-statsAvailable
Parameters

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

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