24h Volume—Open Interest—24h Liquidations$1.36B24h Long/Short—BTC Dominance—ETH Dominance—
App
Language ▾
$ USD ▾
/api/etf/flows
GETAvailable

Daily spot-ETF net-flow history

Daily spot-ETF net-flow history (totals)

GET/api/etf/flows
Daily flow tables as published by a third-party source, stored by CoinBoss. Flows computed by CoinBoss from issuer disclosures are in `/api/sd/etf/history`.

Request

Query parameters

NameTypeRequiredDefaultAllowed valuesDescription
assetstringOptionalBTCBTC, ETH, SOL, HYPEUnderlying asset. Any other value returns 400 `INVALID_PARAM`. Example: BTC
daysstringOptional0—Look-back days; 0 or all = full history. Example: 30

Example request

curl -s "https://www.coinboss.com/api/etf/flows?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.
countnumber—Number of items.
latestobject—Most recent record.
latest.datestring—Calendar date (UTC).
latest.flownumber—Net creation / redemption flow of the day.
latest.aumnumber—Assets under management.
latest.aum_lastnumbermillion USDMost recent non-null combined assets under management of the asset's spot ETFs; valid as of `aum_as_of`, which may be older than `date`.
latest.aum_as_ofstring—Trading day (YYYY-MM-DD) that `aum_last` refers to.
latest.cum_totalnumber—Cumulative total.
latest.sum_7dnumber—7-day sum.
dataarray—Payload.
data[]object—Payload.
data[].datestring—Calendar date (UTC).
data[].flownumber—Net creation / redemption flow of the day.
data[].cumnumber—Cumulative net flow since listing.
data[].aumnumber|null—Assets under management.

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

Example response

/api/etf/flows?asset=BTC&days=30 · Real response captured 2026-11-13 03:52:53 UTC. Long arrays and maps are shortened for display: data had 30 items.

  • {
    • "success": true,
    • "asset": "BTC",
    • "days": 30,
    • "unit": "million_usd",
    • "count": 30,
    • "latest": {
      • "date": "2026-11-12",
      • "flow": -47.7,
      • "aum": 98821.466,
      • "aum_last": 98821.466,
      • "aum_as_of": "2026-11-12",
      • "cum_total": 55106.874,
      • "sum_7d": -1411
      },
    • "data": [
      • { … 4 },
      • { … 4 }
      ]
    }

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
full history since listing by default; `days=N` returns the last N trading days (cumulative totals always start at listing)
Data sources
Daily net flows of US spot crypto ETFs from a public ETF flow tracker; AUM from a public market-data site.
Exchange coverage
US spot ETFs for BTC, ETH, SOL and HYPE (unknown asset falls back to BTC); XRP not collected. Trailing not-yet-published days are dropped.
Sorting
date ascending
Units
million USD (flow, cum, aum)
Method
Uses the source's daily TOTAL row; cum is the running sum since the first record; sum_7d is the sum of the last 7 trading days.
Timestamps
Unix epoch milliseconds (UTC) unless the field description says otherwise
Response format
json
Stability
Stable

Live status

AvailableChecked 2026-11-13 03:52:53 UTCHTTP 2004 msSchema matchesNewest data point 27.9h old

Availability, last 30 days

100% of 409 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/flowsAvailable
Parameters

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

string · default 0 — Look-back days; 0 or all = full history.

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