/api/etf/detail
GETAvailable

Per-fund daily spot-ETF net flows

Per-fund daily spot-ETF net flows

GET/api/etf/detail

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
assetstringOptionalBTCBTC, ETH, SOL, HYPEUnderlying asset. Any other value returns 400 `INVALID_PARAM`. Example: BTC
daysintegerOptional30≥ 1 · ≤ 120Look-back window in days. Example: 30

Example request

curl -s "https://www.coinboss.com/api/etf/detail?asset=BTC&days=30"

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.
daysnumber—Daily values or number of days.
unitstring—Unit of the values in this object.
tickersarray—Fund tickers that appear as columns of the `data` matrix, sorted alphabetically with `TOTAL` last.
tickers[]object—One column: `ticker` and its `issuer` (null for `TOTAL` and when the issuer is unknown).
tickers[].tickerstring—Fund ticker.
tickers[].issuerstring|null—Fund issuer.
datesarray—Calendar dates (UTC).
dates[]string—Calendar dates (UTC).
dataobject—Payload. dynamic keys: 2026-10-01,2026-10-02,2026-10-05,2026-10-06,2026-10-07,2026-10-08
data.{*}object—Payload. dynamic keys: ARKB,BITB,BRRR,BTC,BTCO,BTCW
data.{*}.{*}number—Payload.
data.{*}.TOTALnumbermillion USDNet flow of all spot ETFs of the asset combined on that trading day (the keys of `data` are dates, YYYY-MM-DD); negative = net outflow. may be absent

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

Example response

/api/etf/detail?asset=BTC&days=30 · Real response captured 2026-11-13 03:58:18 UTC. Long arrays and maps are shortened for display: data had 30 items; dates had 30 items; tickers had 13 items; data.{*} had 13 items.

  • {
    • "success": true,
    • "asset": "BTC",
    • "days": 30,
    • "unit": "million_usd",
    • "tickers": [
      • { … 2 },
      • { … 2 }
      ],
    • "dates": [
      • "2026-10-02",
      • "2026-10-05",
      • "2026-10-06",
      • "2026-10-07",
      • "2026-10-08",
      • "2026-10-09",
      • "2026-10-12",
      • "2026-10-13"
      ],
    • "data": {
      • "2026-10-02": { … 2 },
      • "2026-10-05": { … 2 }
      }
    }

Details

Authentication
None. Public endpoint.
Rate limit
1200 requests per minute per IP
Server cache
5m
Edge micro-cache
10s
Update frequency
hourly (minute 15); source publishes once per US trading day
Window
last 30 trading days by default (`days` 1-120)
Data sources
Per-fund daily net flows of US spot crypto ETFs from a public ETF flow tracker.
Exchange coverage
US spot ETFs for BTC, ETH, SOL and HYPE; matrix of date x ticker including the TOTAL column; missing values are null.
Sorting
dates ascending; tickers alphabetical with TOTAL last
Units
million USD
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:58:18 UTCHTTP 2003 msSchema matches

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/detailAvailable
Parameters

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

integer · default 30 · min 1 · max 120 — Look-back window in days.

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