Per-fund daily spot-ETF net flows
Per-fund daily spot-ETF net flows
/api/etf/detailRequest
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| asset | string | Optional | BTC | BTC, ETH, SOL, HYPE | Underlying asset. Any other value returns 400 `INVALID_PARAM`. Example: BTC |
| days | integer | Optional | 30 | ≥ 1 · ≤ 120 | Look-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.
| Field | Type | Unit | Description |
|---|---|---|---|
| success | boolean | — | true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`. |
| asset | string | — | Asset symbol. |
| days | number | — | Daily values or number of days. |
| unit | string | — | Unit of the values in this object. |
| tickers | array | — | 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[].ticker | string | — | Fund ticker. |
| tickers[].issuer | string|null | — | Fund issuer. |
| dates | array | — | Calendar dates (UTC). |
| dates[] | string | — | Calendar dates (UTC). |
| data | object | — | 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.{*}.TOTAL | number | million USD | Net 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"
- "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"
- "2026-10-05"
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
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 →
| 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
/api/etf/detailAvailablestring · default BTC — Underlying asset. Any other value returns 400 `INVALID_PARAM`.
integer · default 30 · min 1 · max 120 — Look-back window in days.
https://www.coinboss.com/api/etf/detail?asset=BTC&days=30More in this category
- Spot ETF funds /api/sd/etf/funds
- Spot ETF history /api/sd/etf/history
- Spot ETF overview (issuer disclosures) /api/sd/etf/overview
- Per-fund daily spot-ETF net flows /api/etf/detail
- Daily spot-ETF net-flow history /api/etf/flows
- Single ETF detail /api/etf/fund/:ticker
- ETF fund list /api/etf/funds
- ETF coin holdings per fund /api/etf/holdings
- ETF / trust products of one issuer /api/etf/issuer
- ETF overview /api/etf/overview
- Grayscale trust premium / discount /api/grayscale/premium
- Futures-based ETF volumes /api/indicators/futures-etf-volumes