Why the Newest Farside Row Is Usually Wrong
If you have gone looking for a Bitcoin ETF flows API, you have found that there is no official one. The figure everyone quotes comes from Farside Investors, a web page with a table: one row per US trading day, one column per fund (IBIT, FBTC, GBTC and the rest) and a Total. No API, no CSV endpoint, no stated update schedule. So every "ETF flows API" is a scraper of that table, and most of them share the same bug.
The bug is in how the table fills. Farside does not publish a day's row all at once. It appears early with most cells blank and fills in fund by fund as each issuer reports, with the two largest, IBIT and FBTC, typically last. The Total column is the sum of whatever has reported so far. A scraper that reads the newest row and stamps it with the fetch time is publishing a partial sum as if it were the day's flow.
We had that bug. On 23 September 2026 the BTC endpoint served +$32.4M, which was a single fund's figure. The settled Total for that trade date was +$346.9M. Checked across 56 BTC trading days, 43 were wrong. Only Friday figures, read on the Saturday after every fund had reported, were right. This post explains the fix, the fields that make the correction visible, and how to read the series without reintroducing the error.
What Counts as a Settled ETF Flow Day
The obvious rule, "a row is final when it has no blank cells", is wrong for this table. Farside writes a - for a fund with no flow that day as well as for a fund that has not reported yet, and most settled rows contain at least one. The rule that actually holds is about ordering:
- A row is final once a newer trade-date row exists below it, or once every fund that reported the previous day has reported this one.
- Anything else is partial, and a partial row is only ever served as the day in progress, never as a flow.
- A
-cell means no value, not zero. The series does not invent a 0.0 for a fund or a day that has not reported.
The endpoint is keyed by US trade date, not by the time we happened to scrape. Each row's time is 00:00 UTC of its trade_date. That matters for joining flows to price: a Tuesday flow belongs to Tuesday's US session, even though it is not fully reported until Wednesday morning in most time zones.
Since 2026-09-25, flows holds settled days only. The day still being reported is returned separately, labelled, so you can watch it fill without ever adding it to a total by accident.
How Do I Get Settled Bitcoin ETF Flows by Trade Date?
curl "https://cryptodataapi.com/api/v1/market-intelligence/etf/btc/flows?days=5" \
-H "X-API-Key: cdk_live_your_key"
The response shape, with illustrative values:
{
"asset": "BTC",
"units": "USD",
"latest": {"trade_date": "2026-11-05", "time": 1793836800, "flow_usd": 212400000.0,
"total_value": 212400000.0, "status": "final", "source": "farside"},
"in_progress": {"trade_date": "2026-11-06", "net_flow_usd": 41200000.0,
"status": "partial", "funds_reported": 5, "funds_total": 11,
"source": "farside", "updated_at": "2026-11-07T06:10:00Z"},
"count": 5,
"flows": [
{"trade_date": "2026-10-30", "flow_usd": -88100000.0, "status": "final", "source": "farside"},
{"trade_date": "2026-11-03", "flow_usd": 150300000.0, "status": "final", "source": "sosovalue"},
{"trade_date": "2026-11-04", "flow_usd": 97000000.0, "status": "final", "source": "farside"},
{"trade_date": "2026-11-05", "flow_usd": 212400000.0, "status": "final", "source": "farside"}
],
"sources": {"primary": "farside.co.uk", "backup": "sosovalue.com"},
"source_health": {"farside:btc": {"last_ok": "...", "consecutive_failures": 0}}
}
Field by field:
flowsis oldest first and settled only. Every row hastrade_date,flow_usd(andtotal_value, the same number, kept for older clients),status: "final"andsource.latestis the newest settled day. With the defaultdays=1,flows[0],flows[-1]andlatestare all the same row.in_progressis the day still filling, withstatus: "partial",funds_reportedout offunds_total, ornullwhen no day is in progress (weekends, or once the newest day has settled). Do not add it to totals.sourceisfarsidefor the figure the market quotes, orsosovaluefor a day Farside had not settled or could not be fetched. SoSoValue's keyless historical chart is the independent backup, settled days only.source_healthreports each feed's last success and consecutive failures, so a stale series announces itself in the payload.
days runs from 1 to 1000 and returns the last N settled trade days: BTC back to 2024-01-11, ETH to 2024-07-23, SOL to 2025-10-28. The asset path accepts btc, eth and sol; xrp returns a 400 because no free source publishes XRP spot-ETF flows. The route answers any valid key and is also sold per call over x402 at $0.01 with no key.
Newest-Row Scrape vs Settled Series: What Changes in Practice
| Newest-row scrape (the old behaviour) | Settled-by-trade-date series (current) | |
|---|---|---|
| Weekday figure | A partial sum on most days | The full Farside Total, or absent until settled |
| Key | Fetch time | trade_date; time is 00:00 UTC of it |
| Day in progress | Indistinguishable from a settled day | Separate in_progress with funds_reported / funds_total |
| Blank cell | Read as 0.0 (SOL showed 0.0 on unreported days) | No value; a day with no reports is not emitted |
| Source failure | Silent staleness | SoSoValue fills the day, source says so, source_health shows the failure |
| Cumulative figures | Included the filling day | Settled days only |
The last row is why /api/v1/market-intelligence/etf/btc/aum changed at the same time. It reconstructs BTC spot-ETF assets under management from the full flow history since the January 2024 launch, returning aum_usd_from_flows, btc_held_from_flows, cumulative_net_flow_usd and price_appreciation_usd plus method, excludes and caveats. It now sums settled days only, where before it included the day still reporting. It is a derived estimate, and it excludes GBTC's pre-conversion holdings; the caveats field says so in the payload rather than in a footnote.
What Happened to the History Archived Before the Fix?
The daily snapshots and the coinglass_etf_flows typed snapshots under /backtesting/snapshots are point-in-time copies of what the API served at the time. For dates before 2026-09-25 that means most weekday rows hold the partial figure. They are deliberately not rewritten: an archive that is edited after the fact stops being a record of what the market could see. Snapshots from 2026-09-25 onward carry trade_date, status and source, so a consumer can tell the two eras apart by the presence of those fields.
For settled history, use the flows route with ?days=N. It is the corrected series back to launch and it is cheap:
import httpx, pandas as pd
H = {"X-API-Key": "cdk_live_your_key"}
r = httpx.get("https://cryptodataapi.com/api/v1/market-intelligence/etf/btc/flows",
params={"days": 400}, headers=H).json()
df = pd.DataFrame(r["flows"])[["trade_date", "flow_usd", "source"]]
df["trade_date"] = pd.to_datetime(df["trade_date"])
df["cum_usd"] = df["flow_usd"].cumsum()
print(df.tail(), "\nsettled days:", r["count"])
print("in progress:", r["in_progress"]) # never append this to df
Every row in df is a settled US trading day. The source column lets you drop or flag the SoSoValue-filled days if you want a single-source series for a paper. The in_progress object is printed, not appended, which is the whole discipline in one line.
The same route serves ETH and SOL with the same semantics, and the altcoin ETF flows post covers their shorter histories. For the interpretive side, what sustained inflows have and have not predicted, see Bitcoin ETF flow tracking; this post is only about getting the number right.
When to Use This (and When Not To)
Use flows for anything that sums, averages or backtests. Rolling 5-day flow, cumulative inflow since launch, flow-versus-return regressions, regime tagging in a daily strategy: all of these are only valid on settled trade dates, and that is all flows contains.
Use in_progress for a live dashboard, labelled as partial. Showing "+$41M so far, 5 of 11 funds reported" is honest and useful. Showing "+$41M" as today's flow is the exact mistake this endpoint was rebuilt to stop. If you display it, display funds_reported and funds_total next to it.
Expect the newest settled day to lag. A US trading day usually settles during the following US morning, after IBIT and FBTC report, and Friday settles on Saturday. A bot that needs Thursday's flow at Thursday's close will not get it from any Farside-derived source; the data does not exist yet. Read latest.trade_date and act on the day it names, not the calendar day you are in.
Do not back-fill from the pre-2026-09-25 snapshots. Those are partials by construction. And do not expect XRP: the route returns a 400 for it until a free source publishes XRP spot-ETF flows, and we would rather return nothing than a guess.
The flows and AUM routes are on any free key, 100 requests a day before email verification and 1,000 after, or per call over x402 for an agent without a key. The docs list both under Market Intelligence.
Frequently asked questions
Is there an official Bitcoin ETF flows API?
No. The figure the market quotes comes from Farside Investors' web table, which has no API. GET /api/v1/market-intelligence/etf/btc/flows serves that table's settled daily Totals keyed by US trade date, with SoSoValue as an independent backup, and works with any valid key or per call over x402.
Why is the newest Farside row usually wrong?
Farside fills a new trade-date row fund by fund as issuers report, with IBIT and FBTC typically last, so the Total is a partial sum until the row settles. On 23 September 2026 the newest row read +$32.4M while the settled Total was +$346.9M.
What does the in_progress field mean?
It is the trade date still being reported, with status partial, funds_reported out of funds_total and its running net flow. It is returned separately from flows and must never be added to totals. It is null when no day is in progress.
How much Bitcoin ETF flow history can I get?
The days parameter (1 to 1000) returns the last N settled trade days: BTC back to 2024-01-11, ETH to 2024-07-23 and SOL to 2025-10-28. Each row carries trade_date, flow_usd, status final and source (farside or sosovalue).
Does the endpoint cover XRP ETF flows?
No. The asset path accepts btc, eth and sol. xrp returns a 400 because no free source publishes XRP spot-ETF flows.



