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

Balance changes among BTC rich-list addresses

Balance changes among BTC rich-list addresses

GET/api/btc/rich-flow
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 6148491 s old (expected within 259200 s)

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
limitintegerOptional50≥ 1 · ≤ 200Number of rows to return. Example: 50

Example request

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

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 }`.
summaryobject—Summary block.
summary.in_usd_24hnumberUSDUSD value of recorded inflows to the tracked large BTC addresses in the last 24 hours; 0 also when no record exists in the window.
summary.out_usd_24hnumberUSDUSD value of recorded outflows from the tracked large BTC addresses in the last 24 hours; 0 also when no record exists in the window.
summary.net_usd_24hnumberUSD`in_usd_24h` − `out_usd_24h`.
summary.count_24hnumber—Count over 24 hours.
dataarray—Payload.
data[]object—Payload.
data[].addressstring—On-chain address.
data[].amount_btcnumberBTCBalance change of the address in this record; negative for an outflow.
data[].usd_valuenumberUSDUSD value of the balance change (positive); null when the source did not publish it.
data[].directionstring—`in` when the address balance increased, `out` when it decreased.
data[].tx_hashstring—Hash of the transaction; null when the source did not provide one.
data[].labelnull—Label.
data[].tsnumbermsTimestamp.

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

Example response

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

  • {
    • "success": true,
    • "summary": {
      • "in_usd_24h": 0,
      • "out_usd_24h": 0,
      • "net_usd_24h": 0,
      • "count_24h": 0
      },
    • "data": [
      • { … 7 },
      • { … 7 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
60s
Edge micro-cache
10s
Update frequency
scheduled every 15 min, but every run has failed since about 2026-09-03
Window
most recent stored balance changes (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
Large balance increases/decreases among top Bitcoin addresses. Stale.
Pagination
`limit` default 50, max 200; no offset.
Sorting
time descending
Units
BTC and USD
Method
summary = total inflow, outflow and net change in USD over the last 24 hours of stored rows.
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 2003 msSchema matchesNewest data point 71.2d old

The newest data point is 6148491 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-flowDegraded
Parameters

integer · default 50 · min 1 · max 200 — Number of rows to return.

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