24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/indicators/bdc/:name
GETAvailable

BTC on-chain valuation indicator series

BTC on-chain valuation indicator series (MVRV, SOPR, NUPL, ... 47 metrics)

GET/api/indicators/bdc/:name

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
name pathstringRequired—mvrv-zscore, sopr, nupl, mvrv, puell-multiple, realized-price, s2f-model-price, lth-mvrv, sth-mvrv, nrpl-usd, lth-sopr, sth-sopr, reserve-risk, terminal-price, … (47)Indicator key; 400 if unknown, 503 while cache is not ready. Example: mvrv-zscore

Parameters marked “path” are part of the URL.

Example request

curl -s "https://www.coinboss.com/api/indicators/bdc/mvrv-zscore"

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 }`.
updatedAtnumbermsWhen the data was last updated.
countnumber—Number of items.
seriesarray—Time series.
series[]object—Time series.
series[].namestring—Name.
series[].dataarray—Payload.
series[].data[]array—Payload.
series[].data[][]number—Payload.

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

Example response

/api/indicators/bdc/mvrv-zscore · Real response captured 2026-11-13 01:38:38 UTC. Long arrays and maps are shortened for display: series[].data had 1455 items.

  • {
    • "success": true,
    • "updatedAt": 1794452717036,
    • "count": 1455,
    • "series": [
      • { … 2 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
30m
Edge micro-cache
10s
Update frequency
daily (refresh run starts 03:00 UTC, one metric every 8 minutes because of the upstream free-tier rate limit)
Window
full history available on the upstream free tier (roughly a rolling 4-year window), daily
Data sources
Bitcoin on-chain valuation and holder-behaviour metrics from a third-party public on-chain data API.
Exchange coverage
47 whitelisted BTC metrics (e.g. mvrv, mvrv-zscore, sopr, nupl, puell-multiple, realized-price, lth/sth supply and realized price, hodl-waves-supply, cdd, reserve-risk); 400 for unknown names, 503 until the cache is first filled.
Sorting
date ascending
Units
depends on the metric (ratio, USD, BTC, percent or address count)
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 01:38:38 UTCHTTP 2001 msSchema matchesNewest data point 22.6h 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/indicators/bdc/:nameAvailable
Parameters

string — Indicator key; 400 if unknown, 503 while cache is not ready.

Request URLhttps://www.coinboss.com/api/indicators/bdc/mvrv-zscore
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.