GETDown
Bitcoin address summary
Bitcoin address summary (balance, tx count)
GET
/api/explorer/address/:addrPartial coverage. The upstream chain-data source is not reachable from our servers at the moment, so this endpoint returns 503. It stays listed so integrations do not break silently; the probe on the status page shows when it recovers.
Down. The last probe failed (HTTP 503)
Request
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| addr path | string | Required | — | — | Bitcoin address; 400 on bad format. Example: 34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo |
Parameters marked “path” are part of the URL.
Example request
curl -s "https://www.coinboss.com/api/explorer/address/34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo"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 }`. |
| cached | boolean | — | `true` when the response came from cache. |
| data | object | — | Payload. |
| data.address | string | — | On-chain address. |
| data.balance_sat | number | sat | Confirmed balance = received − spent. |
| data.funded_sat | number | sat | Total value received in confirmed transactions. |
| data.spent_sat | number | sat | Total value spent in confirmed transactions. |
| data.tx_count | number | count | Number of confirmed transactions. |
| data.chain_stats | object | — | Totals for confirmed transactions of this address. |
| data.chain_stats.funded_txo_count | number | count | Number of outputs received. |
| data.chain_stats.funded_txo_sum | number | sat | Total value received. |
| data.chain_stats.spent_txo_count | number | count | Number of outputs spent. |
| data.chain_stats.spent_txo_sum | number | sat | Total value spent. |
| data.chain_stats.tx_count | number | count | Number of transactions. |
| data.mempool_stats | object | — | Totals for unconfirmed (mempool) transactions of this address. |
| data.mempool_stats.funded_txo_count | number | count | Number of outputs received. |
| data.mempool_stats.funded_txo_sum | number | sat | Total value received. |
| data.mempool_stats.spent_txo_count | number | count | Number of outputs spent. |
| data.mempool_stats.spent_txo_sum | number | sat | Total value spent. |
| data.mempool_stats.tx_count | number | count | Number of transactions. |
Generated 2026-11-11 23:01 UTC from 1 real responses.
Example response
/api/explorer/address/34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo · Real response captured 2026-11-13 02:29:08 UTC.
- "success"true
- "cached"false
- "data"
- "address""34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo"
- "balance_sat"24859759296803
- "funded_sat"119037530223411
- "spent_sat"94177770926608
- "tx_count"5598
- "chain_stats"
- "mempool_stats"
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 60s
- Edge micro-cache
- 10s
- Update frequency
- real time (180 s in-memory cache)
- Window
- latest snapshot
- Data sources
- Live Bitcoin chain data proxied at request time from public Esplora-compatible block explorer APIs.
- Exchange coverage
- Bitcoin mainnet only.
- Units
- satoshis (balance, funded, spent); transaction count
- Method
- balance = funded outputs - spent outputs (confirmed chain stats).
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
DownChecked 2026-11-13 03:29:06 UTCHTTP 5031 msSchema not checked
The last probe failed (HTTP 503)
Availability, last 30 days
41.67% of 132 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
GET
/api/explorer/address/:addrDownParameters
string — Bitcoin address; 400 on bad format.
Request URL
https://www.coinboss.com/api/explorer/address/34xp4vRoCGJym3xR7yCVPFHoCNxv4TwseoChoose an endpoint and press “Send request”. The response, headers and timing will appear here.
More 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