ETF / Fund HoldingsComing soon

Query fund holdings and weights.

This data domain is coming soon. Documentation is available now for reading and integration planning. REST and MCP try-it are disabled until this domain launches — paths and parameters will not change at GA.
GET/api/v1/funds/holdings
Domain
Flows & Wallets
Level
ETF or fund
MCP tool
ownership_flows_query (task=fund_holdings)

Available data

Returns
Fund holdings and weights
Market coverage
US-listed ETFs and funds
Query granularity
One fund per query; current constituents only

Authentication

Send Authorization: Bearer YOUR_API_KEY or X-API-KEY on every request.

Query Parameters

asset_idstringqueryExampleasset_btcrequired

Catalog asset ID (e.g. asset_btc) or symbol (e.g. BTC).

limitintegerqueryExample20optional

Max rows to return (up to 1000).

Response

metadataobject

Response status and resolution information

data_statusDataStatusExamplenot_ready

ready / ok / partial / no_data / not_ready (surface-specific)

limitations[]string[]Exampledata_not_ready

Known data limitations

object_refs[]object[]

Unified object references

Errors & fallback

200
assets_resolve name multi-match; confirm from data[] candidates.
200
The object resolved but no data is available; empty_reason may be not_covered_by_source, unsupported_metric, or limited_depth.
400
Invalid parameters or an ambiguous market listing; ambiguity responses include required_params + candidates.
401
The API key is missing or invalid.
403
The current key scope or plan cannot access this data domain.
404
The requested resource does not exist; source coverage gaps are not 404 responses.
402
Credits or monthly quota exhausted.
429
Request rate exceeded; retry_after is returned in the body and Retry-After in the response headers.