> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Bitcoin ETF History

Get historical data for a specific Bitcoin ETF by ticker symbol. Returns daily BTC holdings, market price, NAV, premium/discount, and shares outstanding over time. Ideal for: tracking ETF flows, analyzing premium/discount trends, monitoring institutional accumulation.

![Get Bitcoin ETF History logo](https://ai-icon.b3.fun/logo/coinglass)
Catalog action Blockchain Data

Get historical data for a specific Bitcoin ETF by ticker symbol. Returns daily BTC holdings, market price, NAV, premium/discount, and shares outstanding over time. Ideal for: tracking ETF flows, analyzing premium/discount trends, monitoring institutional accumulation.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `coinglass-etf-get-bitcoin-history` |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `coinglass`, `etf`, `bitcoin`, `btc`, `history`, `institutional`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ticker` | `string` | Yes | ETF ticker symbol \(e.g., 'GBTC', 'IBIT', 'FBTC'\). Use the Bitcoin ETF List action to get valid tickers. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ticker` | `string` | Yes | ETF ticker symbol |
| `dataPoints` | `array` | Yes | Array of historical data points |

## Examples

**Workflow node**

```json
{
  "type": "coinglass-etf-get-bitcoin-history",
  "payload": {
    "ticker": "example-ticker"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/coinglass-etf-get-bitcoin-history/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "ticker": "example-ticker"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.