> For the complete documentation index, see [llms.txt](https://sosovalue-1.gitbook.io/sosovalue-api-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sosovalue-1.gitbook.io/sosovalue-api-doc/2.-etf/summary-history.md).

# 2.1 ETF Summary History

```
GET /etfs/summary-history
```

**Request Parameters**

| Parameter     | Type    | Required | Description                                                                                                                                                                                           |
| ------------- | ------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| symbol        | string  | Yes      | Crypto asset the ETF tracks. One of `BTC`, `ETH`, `SOL`, `LTC`, `HBAR`, `XRP`, `DOGE`, `LINK`, `AVAX`, `DOT` — **case-insensitive**. Not every asset is listed in every country, see the matrix below |
| country\_code | string  | Yes      | Listing country. `US` or `HK` — **case-insensitive**                                                                                                                                                  |
| start\_date   | string  | No       | Start date. Only the most recent 1 month is supported                                                                                                                                                 |
| end\_date     | string  | No       | End date. Only the most recent 1 month is supported                                                                                                                                                   |
| limit         | integer | No       | Number of records, default 50, max 300                                                                                                                                                                |

**Which `symbol` + `country_code` combinations exist**

All ten assets are available for `US`. Hong Kong only lists the three majors:

| country\_code | Available `symbol`                                              |
| ------------- | --------------------------------------------------------------- |
| `US`          | `BTC` `ETH` `SOL` `LTC` `HBAR` `XRP` `DOGE` `LINK` `AVAX` `DOT` |
| `HK`          | `BTC` `ETH` `SOL`                                               |

The two failure modes return **different codes** — worth distinguishing in a client:

| Request                                                    | Response                                                                                 |
| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| `symbol=FOO` (not in the enum)                             | `400003` `Invalid parameter: symbol`, with the full allowed list in `details.constraint` |
| `symbol=LTC&country_code=HK` (valid enum, no such listing) | `400001` `Unsupported ETF category: symbol=LTC, country_code=HK`                         |

**Response Example**

```json
[
    {
        "date": "2024-04-12",
        "total_net_inflow": -55066297.0000000000000000,
        "total_value_traded": 4706120449.0000000000000000,
        "total_net_assets": 56216535367.0000000000000000,
        "cum_net_inflow": 13534833596.0950000000000000
    },
    {
        "date": "2024-04-11",
        "total_net_inflow": 91269283.0000000000000000,
        "total_value_traded": 2498627928.0000000000000000,
        "total_net_assets": 59225065270.0000000000000000,
        "cum_net_inflow": 12581438056.0950000000000000
    }
]
```

**Response Fields**

| Field                | Type       | Description                                                                   |
| -------------------- | ---------- | ----------------------------------------------------------------------------- |
| date                 | String     | Trading date, format yyyy-MM-dd                                               |
| total\_net\_inflow   | BigDecimal | Total net inflow of all ETFs on the day (USD); negative indicates net outflow |
| total\_value\_traded | BigDecimal | Total trading volume of all ETFs (USD)                                        |
| total\_net\_assets   | BigDecimal | Total net assets of all ETFs (USD)                                            |
| cum\_net\_inflow     | BigDecimal | Cumulative net inflow since ETF launch (USD)                                  |

**Notes**

* Data is sorted in reverse chronological order (latest date first).
* Non-trading days (weekends, holidays) are excluded from results.
* You can use `start_date` / `end_date` together to perform range queries and reduce the amount of data returned.
* The query range is limited to the most recent 1 month.

**symbol Enum**

| Value | Description |
| ----- | ----------- |
| BTC   | Bitcoin     |
| ETH   | Ethereum    |
| SOL   | Solana      |
| LTC   | Litecoin    |
| HBAR  | Hedera      |
| XRP   | XRP         |
| DOGE  | Dogecoin    |
| LINK  | Chainlink   |
| AVAX  | Avalanche   |
| DOT   | Polkadot    |

**country\_code Enum**

| Value | Description   |
| ----- | ------------- |
| US    | United States |
| HK    | Hong Kong     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://sosovalue-1.gitbook.io/sosovalue-api-doc/2.-etf/summary-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.