/api/btc/rich-list
GETDegraded

BTC rich list

BTC rich list (largest address balances)

GET/api/btc/rich-list
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. `balance_usd` multiplies the last known balance by the current price.
Degraded. The newest data point is 6144816 s old (expected within 259200 s)

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
limitintegerOptional100≥ 1 · ≤ 300Number of rows to return. Example: 100

Example request

curl -s "https://www.coinboss.com/api/btc/rich-list?limit=100"

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 }`.
pricenumber—Last price in the quote currency (USD or USDT unless stated).
updated_atnumbermsWhen this row was last updated.
totalnumber—Total.
dataarray—Payload.
data[]object—Payload.
data[].ranknumber—Rank in this list (1 = first).
data[].addressstring—On-chain address.
data[].balance_btcnumberBTCBTC balance of the address at the snapshot.
data[].balance_usdnumberUSDBalance value.
data[].hold_ratenumberfractionShare of BTC supply held by the address, as a fraction (0.012 = 1.2 %).
data[].tx_countnumber|nullcountNumber of transactions of the address; null when the source did not publish it.
data[].labelstring|null—Label.

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

Example response

/api/btc/rich-list?limit=100 · Real response captured 2026-11-13 03:53:37 UTC. Long arrays and maps are shortened for display: data had 100 items.

  • {
    • "success": true,
    • "price": 69106.6,
    • "updated_at": 1788397202000,
    • "total": 300,
    • "data": [
      • { … 7 },
      • { … 7 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
2m
Edge micro-cache
10s
Update frequency
scheduled every 15 min, but every run has failed since about 2026-09-03
Window
latest stored snapshot (frozen at about 2026-09-03)
Data sources
Scraped from a third-party block explorer's internal web API (not an official public API); no longer updating.
Exchange coverage
Top 300 Bitcoin addresses. Stale.
Pagination
`limit` default 100, range 1-300; no offset.
Sorting
rank ascending
Units
BTC and USD; percent of supply
Method
balance_usd = balance in BTC x latest stored BTC price.
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

DegradedChecked 2026-11-13 03:53:37 UTCHTTP 2002 msSchema matchesNewest data point 71.1d old

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

Availability, last 30 days

100% of 407 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-listDegraded
Parameters

integer · default 100 · min 1 · max 300 — Number of rows to return.

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