24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/indices/bottom-radar/case-0819
GETAvailableBeta

Bottom-radar historical case study

Frozen case study of the 2026-08-19 market bottom as seen by the bottom radar.

GET/api/indices/bottom-radar/case-0819

Request

This endpoint takes no parameters.

Example request

curl -s "https://www.coinboss.com/api/indices/bottom-radar/case-0819"

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 }`.
idstring—Identifier.
titlestring—Chinese title of the case study.
savedAtstring—Date-time string.
moveobject—The BTC price move under study: low, high, size in percent and the main rally days.
move.lowobject—Low of the period.
move.low.dstring—Calendar date (UTC).
move.low.pricenumber—Last price in the quote currency (USD or USDT unless stated).
move.highobject—High of the period.
move.high.dstring—Calendar date (UTC).
move.high.pricenumber—Last price in the quote currency (USD or USDT unless stated).
move.pctnumber%Percentage.
move.mainDaysarray—Main rally days of the move.
move.mainDays[]array—One day as `[date, daily change in %]`.
move.mainDays[][]number|string—Element 0 is the date string, element 1 that day's price change in percent.
findingsarray—Findings of the study, one per signal examined.
findings[]object—One finding: `grade`, `zh` (Chinese text) and `lead`.
findings[].gradestring—Strength of the finding: `strong`, `mid` or `anomaly`.
findings[].zhstring—Text in Chinese.
findings[].leadstring—Chinese text stating how far ahead of the move the signal appeared.
modelReviewstring—Chinese text reviewing how the older six-dimension signal model behaved in this case.
columnsarray—Chinese column labels for the fields of `rows`, in display order.
columns[]string—One column label.
rowsarray—Result rows.
rows[]object—Result rows.
rows[].dstring—Calendar date (UTC).
rows[].pricenumber—Last price in the quote currency (USD or USDT unless stated).
rows[].liqScorenumber—Liquidation imbalance score of the day: (short − long liquidations) ÷ total × 100, −100 to 100.
rows[].fundingnumber—Funding rate block or value.
rows[].oiBnnumberUSD billionBTC open interest on that day, in billions of USD.
rows[].lsLongPctnumber%Long-account percentage of BTC retail traders on that day.
rows[].etfFlowMnumber|nullUSD millionNet flow of BTC spot ETFs on that day in millions of USD; null on non-trading days.
rows[].fearGreednumber—Fear & Greed index value on that day (0–100).
rows[].iv30number%BTC 30-day at-the-money implied volatility on that day, in volatility points.
rows[].realVolnumber%BTC realized volatility on that day.
rows[].basisnumber—Futures price minus spot price, or the basis block.
rows[].perpSpotnumberratioPerpetual volume ÷ spot volume on that day.
rows[].richTop100number%Share of BTC supply held by the top 100 addresses on that day.
rows[].exBalKnumberthousand BTCBTC held on exchanges on that day, in thousands of BTC.
rows[].mvrvZnumber—MVRV Z-score of BTC on that day.
rows[].nuplnumber—Net unrealized profit/loss (NUPL) of BTC on that day.

Generated 2026-11-11 23:01 UTC from 1 real responses.

Example response

/api/indices/bottom-radar/case-0819 · Real response captured 2026-11-13 01:38:36 UTC. Long arrays and maps are shortened for display: rows had 32 items; columns had 16 items; findings had 10 items; move.mainDays had 3 items.

  • {
    • "success": true,
    • "id": "case-0819",
    • "title": "2026-08-19 大涨前全维度复盘",
    • "savedAt": "2026-08-30",
    • "move": {
      • "low": { … 2 },
      • "high": { … 2 },
      • "pct": 24.5,
      • "mainDays": [ … 2 ]
      },
    • "findings": [
      • { … 3 },
      • { … 3 }
      ],
    • "modelReview": "原六维模型爆仓维 8-17 翻多后扣住整个主升段(88~95),但是同步不领先;总命中率 47.9%≈掷硬币。真正领先的四个维度(ETF流/富豪斜率/波动压缩/散户反向)当时都不在模型里——六灯雷达补的就是这个。",
    • "columns": [
      • "日期",
      • "价格",
      • "爆仓分",
      • "费率%",
      • "OI(bn)",
      • "散户多%",
      • "ETF流(M)",
      • "恐贪"
      ],
    • "rows": [
      • { … 16 },
      • { … 16 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
60m
Edge micro-cache
10s
Window
fixed historical window around 2026-08-19
Data sources
Static, frozen case study of the 2026-08-19 market bottom; not a live dataset.
Exchange coverage
BTC, one historical case only.
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Beta

Live status

AvailableChecked 2026-11-13 01:38:36 UTCHTTP 2001 msSchema matchesNewest data point 80.1d old

Availability, last 30 days

100% of 380 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/indices/bottom-radar/case-0819Available
Parameters

No parameters.

Request URLhttps://www.coinboss.com/api/indices/bottom-radar/case-0819
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.