Multi-chain rich-list balance changes
Multi-chain rich-list balance changes
/api/rich-list/:chain/flowRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| chain path | string | Required | — | eth, tron, bsc, polygon, arbitrum, doge, ltc, dash, aptos, bch, avalanche, optimism, base, ton | Chain id; 400 if unsupported. Example: eth |
| self | string | Optional | — | 1 | =1 includes transfers between listed addresses. |
| limit | integer | Optional | 50 | ≥ 1 · ≤ 200 | Number of rows to return. Example: 50 |
Parameters marked “path” are part of the URL.
Example request
curl -s "https://www.coinboss.com/api/rich-list/eth/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.
| Field | Type | Unit | Description |
|---|---|---|---|
| success | boolean | — | true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`. |
| chain | string | — | Chain id. |
| available | boolean | — | Whether data is available. |
| src | string | — | Source. |
| unit | string | — | Unit of the values in this object. |
| summary | object | — | Summary block. |
| summary.in_usd_24h | number | USD | USD value of recorded inflows to the tracked large addresses of the chain in the last 24 hours; 0 also when no record exists in the window. |
| summary.out_usd_24h | number | USD | USD value of recorded outflows from the tracked large addresses of the chain in the last 24 hours; 0 also when no record exists in the window. |
| summary.net_usd_24h | number | USD | `in_usd_24h` − `out_usd_24h`. |
| summary.count_24h | number | — | Count over 24 hours. |
| data | array | — | Payload. |
| data[] | object | — | Payload. |
| data[].address | string | — | On-chain address. |
| data[].amount | number | — | Amount. |
| data[].usd_value | number | USD | USD value of the balance change (positive); null when the source did not publish it. |
| data[].direction | string | — | `in` when the address balance increased, `out` when it decreased. |
| data[].tx_hash | string | — | Hash of the transaction; null when the source did not provide one. |
| data[].ts | number | ms | Timestamp. |
Generated 2026-11-11 23:01 UTC from 1 real responses.
Example response
/api/rich-list/eth/flow?limit=50 · Real response captured 2026-11-13 03:53:41 UTC. Long arrays and maps are shortened for display: data had 50 items.
- "success"true
- "chain""eth"
- "available"true
- "src""oklink"
- "unit""ETH"
- "summary"
- "in_usd_24h"0
- "out_usd_24h"0
- "net_usd_24h"0
- "count_24h"0
- "data"
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 60s
- Edge micro-cache
- 10s
- Update frequency
- scheduled every 20 min, but the default source has failed since about 2026-09-03
- Window
- most recent stored rows (default source frozen at about 2026-09-03)
- Data sources
- Large holder balance changes per chain; default rows come from a discontinued scraped source and are stale.
- Exchange coverage
- Chains: eth, tron, bsc, polygon, arbitrum, doge, ltc, dash, aptos, bch, avalanche, optimism, base, ton; `available: false` when a chain has no rows.
- Pagination
- `limit` default 50, max 200; no offset.
- Sorting
- time descending
- Units
- native coin units and USD
- Method
- With `self=1`, flows are derived by diffing consecutive top-holder snapshots.
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
The newest data point is 6148422 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 →
| Code | HTTP | Meaning | What to do |
|---|---|---|---|
| INVALID_PARAM | 400 | A 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. |
| UNAUTHORIZED | 401 | The `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. |
| FORBIDDEN | 403 | The route is not part of the public API (internal or account-only). | Do not retry. |
| NOT_FOUND | 404 | Unknown route, or the requested coin / exchange / fund does not exist. | Do not retry; check the path and identifiers against the catalog. |
| RATE_LIMITED | 429 | More requests than the per-minute limit. `Retry-After` gives the seconds to wait. | Wait for `Retry-After`, then retry with backoff. |
| INTERNAL | 500 | Unexpected 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_FAILED | 503 | The 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. |
| UNAVAILABLE | 501 / 503 | The 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_FAILED | 200 | Some 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
/api/rich-list/:chain/flowDegradedstring — Chain id; 400 if unsupported.
string — =1 includes transfers between listed addresses.
integer · default 50 · min 1 · max 200 — Number of rows to return.
https://www.coinboss.com/api/rich-list/eth/flow?limit=50More in this category
- Multi-chain address lookup /api/browser/:chain/address/:addr
- Multi-chain block lookup /api/browser/:chain/block/:hashOrHeight
- Multi-chain transaction lookup /api/browser/:chain/tx/:txid
- Detects which EVM chains an address is active on /api/browser/detect
- Balance changes among BTC rich-list addresses /api/btc/rich-flow
- BTC rich list /api/btc/rich-list
- BTC rich-list statistics /api/btc/rich-stat
- BTC rich-list holdings trend /api/btc/rich-trend
- Bitcoin address summary /api/explorer/address/:addr
- Bitcoin address transactions /api/explorer/address/:addr/txs
- Bitcoin block detail /api/explorer/block/:hashOrHeight
- Bitcoin chain tip /api/explorer/tip
- Bitcoin transaction detail /api/explorer/tx/:txid
- Count of BTC addresses holding more than a threshold /api/indicators/addr-above/:tier
- BTC on-chain valuation indicator series /api/indicators/bdc/:name
- Bitcoin reachable-node count and distribution /api/indicators/bitnodes
- BTC holder comparison series /api/indicators/btccmp/:pair
- BTC on-chain chart series /api/indicators/chain
- Exchange BTC inflow / outflow history /api/indicators/cm/exchange-flows
- BTC supply held on exchanges /api/indicators/cm/exchange-supply
- BTC non-zero address count history /api/indicators/cm/nonzero-addresses
- Government BTC holdings /api/indicators/gov-treasuries
- Bitcoin halving countdown and history /api/indicators/halving
- Share of BTC supply dormant for more than N years /api/indicators/hodl-wave-above/:years
- Bitcoin mining-pool block share /api/indicators/mempool/pools
- Strategy BTC cost basis and holdings history /api/indicators/mstr-cost
- Share of BTC supply in profit /api/indicators/supply-profit-pct
- WBTC reserve balance history /api/indicators/wbtc-balance
- Multi-chain rich list /api/rich-list/:chain
- Multi-chain rich-list balance changes /api/rich-list/:chain/flow
- Multi-chain rich-list statistics /api/rich-list/:chain/stat
- Multi-chain rich-list holdings trend /api/rich-list/:chain/trend
- Public-company / institutional coin treasuries /api/treasuries/:coin