Get Bitcoin ETF Detail
Get comprehensive details for a specific Bitcoin ETF by ticker symbol. Returns fund info, current session data, last quote/trade, and 52-week performance metrics. Ideal for: ETF due diligence, real-time price monitoring, performance comparison, trading decisions.
Catalog action Blockchain Data
Get comprehensive details for a specific Bitcoin ETF by ticker symbol. Returns fund info, current session data, last quote/trade, and 52-week performance metrics. Ideal for: ETF due diligence, real-time price monitoring, performance comparison, trading decisions.
At a Glance
| Field | Value |
|---|---|
| Action ID | coinglass-etf-get-bitcoin-detail |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | coinglass, etf, bitcoin, btc, detail, 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 |
name | string | Yes | Full fund name |
marketStatus | string | Yes | Market status (open/closed) |
type | string | Yes | Security type |
tickerInfo | object | Yes | Detailed ticker information |
session | object | Yes | Current trading session data |
lastQuote | object | No | Latest quote data |
lastTrade | object | No | Latest trade data |
performance | object | No | Performance metrics |
Examples
json{ "type": "coinglass-etf-get-bitcoin-detail", "payload": { "ticker": "example-ticker" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/coinglass-etf-get-bitcoin-detail/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "ticker": "example-ticker" }}'
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.