24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/btc/rich-trend
GETDegraded

BTC rich-list holdings trend

BTC rich-list holdings trend

GET/api/btc/rich-trend
Partial coverage. The address-ranking source stopped updating; the last snapshot is returned with its original timestamp. Treat the data as historical until the timestamp moves again.
Degraded. The newest data point is 6292751 s old (expected within 259200 s)

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
daysintegerOptional365≥ 7 · ≤ 2000Look-back window in days. Example: 365

Example request

curl -s "https://www.coinboss.com/api/btc/rich-trend?days=365"

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 }`.
dataarray—Payload.
data[]object—Payload.
data[].tsnumbermsTimestamp.
data[].top10number—Top ten entries.
data[].top20numberfractionShare of BTC supply held by the 20 largest addresses on that day, as a fraction.
data[].top50numberfractionShare of BTC supply held by the 50 largest addresses on that day, as a fraction.
data[].top100numberfractionShare of BTC supply held by the 100 largest addresses on that day, as a fraction.

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

Example response

/api/btc/rich-trend?days=365 · Real response captured 2026-11-13 03:59:10 UTC. Long arrays and maps are shortened for display: data had 293 items.

  • {
    • "success": true,
    • "data": [
      • { … 5 },
      • { … 5 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
10m
Edge micro-cache
10s
Update frequency
scheduled every 15 min, but every run has failed since about 2026-09-03
Window
last 365 days by default (`days` 7-2000); ends at about 2026-09-01
Data sources
Scraped from a third-party block explorer's internal web API (not an official public API); no longer updating.
Exchange coverage
Bitcoin top-holder concentration. Stale.
Sorting
time ascending
Units
percent of supply held by top-N addresses
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

DegradedChecked 2026-11-13 03:59:10 UTCHTTP 2001 msSchema matchesNewest data point 72.8d old

The newest data point is 6292751 s old (expected within 259200 s)

Availability, last 30 days

100% of 408 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/btc/rich-trendDegraded
Parameters

integer · default 365 · min 7 · max 2000 — Look-back window in days.

Request URLhttps://www.coinboss.com/api/btc/rich-trend?days=365
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.