GET
/api/v1/etf/summaryHobbyist tier+ · 30 req/minCross-asset ETF rollup — BTC + ETH + combined in a single call.
Dashboard-friendly single-call summary. Returns the latest day's flow, rolling 7-day flow, cumulative AUM, and all-time extremes for both BTC and ETH, plus the combined totals. Windows are fixed here — custom time ranges belong on the per-asset routes.
Query parameters
This endpoint takes no query parameters.
Response shape
Always wrapped in the standard envelope. Nullable fields are explicitly marked — treat missing numeric data as a real data-source gap, not as an error.
data payloadtypescript
// Wrapped in the standard envelope:
// {
// data: /* shape below */,
// meta?: { total?: number; limit?: number; offset?: number; ... }
// }
{
assets: {
BTC: {
latestDate: string | null;
latestFlowUsdM: number;
rolling7dUsdM: number;
cumulativeUsdM: number;
biggestInflow: { date: string; totalUsdM: number } | null;
biggestOutflow: { date: string; totalUsdM: number } | null;
};
ETH: { /* same shape as BTC */ };
};
combined: {
latestFlowUsdM: number;
rolling7dUsdM: number;
cumulativeUsdM: number;
};
}Example
Copy the curl, replace YOUR_KEY with a real key from your dashboard, and run.
Requestbash
curl -sS "http://localhost:3000/api/v1/etf/summary" \
-H "Authorization: Bearer cg_live_YOUR_KEY"Responsejson
{
"data": {
"assets": {
"BTC": {
"latestDate": "2026-04-17",
"latestFlowUsdM": 195.1,
"rolling7dUsdM": 920.12,
"cumulativeUsdM": 43210.55,
"biggestInflow": { "date": "2026-03-05", "totalUsdM": 1045.3 },
"biggestOutflow": { "date": "2026-02-19", "totalUsdM": -385.7 }
},
"ETH": {
"latestDate": "2026-04-17",
"latestFlowUsdM": 45.7,
"rolling7dUsdM": 88.12,
"cumulativeUsdM": 2810.33,
"biggestInflow": { "date": "2026-03-21", "totalUsdM": 215.8 },
"biggestOutflow": { "date": "2026-02-11", "totalUsdM": -120.0 }
}
},
"combined": {
"latestFlowUsdM": 240.8,
"rolling7dUsdM": 1008.24,
"cumulativeUsdM": 46020.88
}
},
"meta": { "total": 2 }
}Notes
- Combined totals are naive sums of BTC and ETH $M — the two assets have different price scales, so interpret accordingly.
Next
Check the error code reference, or get an API key to try the request against your own account.