/api/etf/holdings
GETDegraded

ETF coin holdings per fund

ETF coin holdings per fund

GET/api/etf/holdings
Partial coverage. The holdings source has not published a new snapshot recently; the last one is returned with its original date. Check `latest.date` before using the numbers.
Degraded. The newest data point is 3124699 s old (expected within 345600 s)

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
assetstringOptionalBTCBTC, ETH, SOL, HYPEUnderlying asset. Any other value returns 400 `INVALID_PARAM`. Example: BTC

Example request

curl -s "https://www.coinboss.com/api/etf/holdings?asset=BTC"

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 }`.
assetstring—Asset symbol.
unitstring—Unit of the values in this object.
countnumber—Number of items.
latestobject—Most recent record.
latest.datestring—Calendar date (UTC).
latest.holdingsnumber—Coins held by the fund.
latest.aum_pct_of_mcapnumber%Combined AUM of the asset's spot ETFs as a percentage of the coin's market cap, on the most recent date in `data`.
dataarray—Payload.
data[]object—Payload.
data[].datestring—Calendar date (UTC).
data[].holdingsnumber—Coins held by the fund.
data[].aum_pct_of_mcapnumber%Combined AUM of the asset's spot ETFs as a percentage of the coin's market cap on that date, from a third-party source.

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

Example response

/api/etf/holdings?asset=BTC · Real response captured 2026-11-13 03:58:19 UTC. Long arrays and maps are shortened for display: data had 64 items.

  • {
    • "success": true,
    • "asset": "BTC",
    • "unit": "token_count",
    • "count": 64,
    • "latest": {
      • "date": "2026-10-08",
      • "holdings": 1282351.4417,
      • "aum_pct_of_mcap": 6.3813
      },
    • "data": [
      • { … 3 },
      • { … 3 }
      ]
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
5m
Edge micro-cache
10s
Update frequency
hourly collector run, but the upstream source has been disabled since 2026-10-08
Window
full stored daily history (ends 2026-10-08)
Data sources
Total coins held by all US spot ETFs of an asset, from a third-party ETF data site.
Exchange coverage
BTC, ETH, SOL (as stored); no data after 2026-10-08.
Sorting
date ascending
Units
holdings in coins (token count); aum_pct_of_mcap in percent
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

DegradedChecked 2026-11-13 03:58:19 UTCHTTP 2002 msSchema matchesNewest data point 36.2d old

The newest data point is 3124699 s old (expected within 345600 s)

Availability, last 30 days

100% of 410 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/etf/holdingsDegraded
Parameters

string · default BTC — Underlying asset. Any other value returns 400 `INVALID_PARAM`.

Request URLhttps://www.coinboss.com/api/etf/holdings?asset=BTC
Choose an endpoint and press “Send request”. The response, headers and timing will appear here.