Liquidation heatmap (model 1)
Liquidation heatmap (estimated liquidation intensity over price × time)
/api/heatmapRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| symbol | string | Optional | BTC | — | Coin symbol. Example: BTC |
| range | string | Optional | 24h | 12h, 24h, 3d, 7d, 1M | Time window. Example: 24h |
Example request
curl -s "https://www.coinboss.com/api/heatmap?symbol=BTC&range=24h"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.
| Field | Type | Unit | Description |
|---|---|---|---|
| symbol | string | — | Instrument symbol as normalised by CoinBoss (for example BTCUSDT). |
| range | string | — | Window requested. |
| updatedAt | number | ms | When the data was last updated. |
| currentPrice | number | — | Current price. |
| prices | array | — | Price series. |
| prices[] | number | — | Price series. |
| times | array | — | Timestamps of the series. |
| times[] | number | — | Timestamps of the series. |
| grid | array | — | Grid values. |
| grid[] | array | — | Grid values. |
| grid[][] | number | — | Grid values. |
| maxNotional | number | USD | Modelled liquidation notional of the densest cell in the whole grid, i.e. the amount a `grid` value of 250 stands for; model estimate, not exchange data. |
| clusters | array | — | Price clusters. |
| clusters[] | object | — | Price clusters. |
| clusters[].price | number | — | Last price in the quote currency (USD or USDT unless stated). |
| clusters[].strength | number | ratio | Cluster's modelled notional ÷ `maxNotional`, between 0.15 and 1; clusters are the up to 8 strongest local peaks of the latest column. |
| clusters[].usd | number | USD | Value. |
Generated 2026-11-11 23:00 UTC from 3 real responses.
Example response
/api/heatmap?symbol=BTC&range=24h · Real response captured 2026-11-13 03:52:46 UTC. Long arrays and maps are shortened for display: grid had 24 items; times had 24 items; grid[] had 250 items; prices had 250 items; clusters had 8 items.
- "symbol""BTC"
- "range""24h"
- "updatedAt"1794541875384
- "currentPrice"69059.1
- "prices"
- 66165.39
- 66207.97
- 66250.55
- 66293.14
- 66335.72
- 66378.3
- 66420.89
- 66463.47
- "times"
- 1794456000000
- 1794459600000
- 1794463200000
- 1794466800000
- 1794470400000
- 1794474000000
- 1794477600000
- 1794481200000
- "grid"
- "maxNotional"333065235
- "clusters"
Verified samples
Besides the example above, the probe calls this endpoint with these parameters and checks the schema each time.
| Parameters | HTTP | Latency | Result |
|---|---|---|---|
| range=24h&symbol=ETH | 200 | 2 ms | Pass |
| range=24h&symbol=SOL | 200 | 3 ms | Pass |
Checked 2026-11-13 03:28:03 UTC
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 60s
- Edge micro-cache
- 10s
- Update frequency
- every 5 min
- Window
- range param: 12h | 24h | 3d | 7d | 1M (default 24h); latest model snapshot
- Data sources
- Model estimate computed in-house from CoinBoss's own hourly futures klines (binance, okx fallback) and aggregated open-interest history.
- Exchange coverage
- BTC, ETH, SOL plus the top 30 coins by 24 h futures notional (hourly kline volume x close); model output, not exchange-reported data
- Units
- estimated liquidation notional in USD per time x price cell; timestamps in Unix ms
- Method
- each 1 h candle opens notional = volume x close (optionally boosted by OI delta) spread over leverage tiers 5/10/25/50/100 (weights 0.30/0.30/0.20/0.12/0.08); long liq level ~ P x (1 - 1/L + 0.004), short ~ P x (1 + 1/L - 0.004); 250 price bins with 3-bin kernel; swept bins are zeroed; hourly decay 0.999
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
Availability, last 30 days
100% of 409 checks passed
Errors
Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →
| Code | HTTP | Meaning | What to do |
|---|---|---|---|
| INVALID_PARAM | 400 | A 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. |
| UNAUTHORIZED | 401 | The `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. |
| FORBIDDEN | 403 | The route is not part of the public API (internal or account-only). | Do not retry. |
| NOT_FOUND | 404 | Unknown route, or the requested coin / exchange / fund does not exist. | Do not retry; check the path and identifiers against the catalog. |
| RATE_LIMITED | 429 | More requests than the per-minute limit. `Retry-After` gives the seconds to wait. | Wait for `Retry-After`, then retry with backoff. |
| INTERNAL | 500 | Unexpected 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_FAILED | 503 | The 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. |
| UNAVAILABLE | 501 / 503 | The 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_FAILED | 200 | Some 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
/api/heatmapAvailablestring · default BTC — Coin symbol.
string · default 24h — Time window.
https://www.coinboss.com/api/heatmap?symbol=BTC&range=24hMore in this category
- Liquidation heatmap (model 1) /api/heatmap
- Symbols supported by the liquidation heatmap /api/heatmap/symbols
- Liquidation heatmap (model 2 / 3) /api/liq-heatmap
- Symbols supported by the liquidation-heatmap model /api/liq-heatmap/symbols
- Liquidation cluster levels /api/liq-levels
- Liquidation map /api/liq-map
- Symbols supported by the liquidation map /api/liq-map/symbols
- Liquidation max-pain levels /api/liq-maxpain