# Guide: Keep individual ETF data separate from country-wide flow totals

Canonical: https://chainminute.com/news/cc4b1af3-d50d-4a90-a293-ff3d20cfc2ef
Published: 2026-10-13T21:04:57.762Z
Publisher: Chain Minute

A SoSoValue example separates one fund ticker from an asset-and-country aggregate, with matching dates and no invented market figures.

A market brief should say whether an ETF figure describes one fund or a group of funds. AirnodeHub’s SoSoValue listing exposes separate operations for those scopes, making the distinction explicit before a number reaches a headline.

### Start with the question

For a documented example concerning US spot Bitcoin ETFs, `listEtfs` takes `symbol: "BTC"` and `country_code: "US"`. Its purpose is to identify the relevant fund tickers, names and exchanges. A ticker from that response can then identify one fund in `getEtfHistory` or `getEtfMarketSnapshot`.

A country-wide series uses a different operation: `getEtfSummaryHistory`, with the asset symbol and country code. The Airnode document describes it as daily totals across the relevant spot ETFs. An individual fund’s history and that aggregate answer different questions; they should not share an ambiguous label such as “Bitcoin ETF data.”

### Preserve the time window

The documented history operations accept `start_date` and `end_date` in `yyyy-MM-dd` form. For example, a request for October 1 through October 9, 2026 would describe that interval, rather than an unspecified “recent” period. The document limits these histories to the most recent month. An unsupported older range is not evidence that the value was zero.

The market-snapshot operation describes the latest settled day. A request made today should therefore retain the date attached to the data rather than label every returned figure as today’s trading activity. This is a documented request example; no response, flow amount or investment outcome is claimed here.

### Retain the source context

The [SoSoValue listing](https://airnodehub.api3.org/explore/sosovalue) was Free when checked on October 13, 2026. Recheck its operation pricing before use. It is an API3-operated third-party relay over SoSoValue’s data. Its attestation binds the serving Airnode, request, time and response; it does not independently establish the economic accuracy of the upstream figures.

A useful briefing keeps the asset, country or fund ticker, metric name, data date and source together. These distinctions support a clear description of the dataset, without implying a price forecast or a recommendation to buy an ETF.

## Sources

- [API3 AirnodeHub listing](https://airnodehub.api3.org/explore/sosovalue) — API3 AirnodeHub listing
- [Attestation | AirnodeHub](https://airnodehub-docs.api3.org/airnode/attestation) — airnodehub-docs.api3.org
- [For API consumers | AirnodeHub](https://airnodehub-docs.api3.org/api-consumers/) — airnodehub-docs.api3.org
- [API3 Airnode static OpenAPI](https://airnode-sosovalue.fly.dev/) — API3 Airnode static OpenAPI

- [Editorial policy](https://chainminute.com/editorial-policy)
- [Request a correction](https://chainminute.com/corrections)