/api/explorer/address/:addr/txs
GETDown

Bitcoin address transactions

Bitcoin address transactions (cursor paginated)

GET/api/explorer/address/:addr/txs
Partial 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

NameTypeRequiredDefaultAllowed valuesDescription
addr pathstringRequired——Bitcoin address. Example: 34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo
afterstringOptional——Cursor (last txid of previous page).

Parameters marked “path” are part of the URL.

Example request

curl -s "https://www.coinboss.com/api/explorer/address/34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo/txs"

Response fields

The field table has not been generated for this endpoint yet. Call it in the Playground to inspect the live response.

Example response

/api/explorer/address/34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo/txs · Real response captured 2026-11-13 02:29:09 UTC. Long arrays and maps are shortened for display: data had 50 items; data[].vin had 72 items; data[].vout had 72 items.

  • {
    • "success": true,
    • "cached": false,
    • "data": [
      • { … 10 },
      • { … 10 }
      ],
    • "next_cursor": "de541b3c48cedea330d72355fdb51fa19efa4c03183c163ddf6e31f5c985a8ed",
    • "has_more": true
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
45s
Edge micro-cache
10s
Update frequency
real time (120 s in-memory cache)
Window
most recent transactions of the address
Data sources
Live Bitcoin chain data proxied at request time from public Esplora-compatible block explorer APIs.
Exchange coverage
Bitcoin mainnet only.
Pagination
Cursor pagination: pass `after=<last txid>` to fetch the next page (page size set by the upstream API).
Sorting
newest first
Units
satoshis
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 5034941 msSchema not checked

The last probe failed (HTTP 503)

Availability, last 30 days

46.21% 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 →

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/explorer/address/:addr/txsDown
Parameters

string — Bitcoin address.

string — Cursor (last txid of previous page).

Request URLhttps://www.coinboss.com/api/explorer/address/34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo/txs
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.