Fund Holdings (SEC N-PORT)
InfoTrie's fund holdings dataset reads the SEC's Form N-PORT data sets: what each US registered fund held at its quarter end, position by position, with the issuer's LEI, the security's ISIN, the value in US dollars and the share of the fund's net assets. Each holding is a dated edge of InfoTrie's entity graph, known from the day it was filed, so an amendment replaces the report it amends only from its filing date. On top of the positions, it answers who holds a security, what a fund holds through the funds it invests in, and what a management company's funds hold together.
Status: In rollout — available on request
Request a sampleView as Markdown
Key facts
| Universe | US registered funds filing Form N-PORT; a European UCITS files no N-PORT |
|---|---|
| Measured run | The 2026 third-quarter data set: 14,066 filings and 5.6 million holdings |
| Point in time | A report is known from its filing date; an amendment replaces it from its own |
| Look-through | A fund's exposure through the funds it holds, up to 3 levels |
| Breakdowns | By country, issuer type and asset category as filed (not GICS sectors); a management company's funds by security, issuer, country or type |
| Frequency | One edition per quarterly SEC data set |
| Delivery | REST API and MCP tools (rollout), InfoTrie console datasets; Enterprise and Bespoke plans |
Sources
- SEC EDGAR (Form N-PORT data sets)
- GLEIF (fund managers, issuers' LEIs)
Data dictionary
| Field | Type | Description |
|---|---|---|
holder / holder_lei / holder_name | string | The fund: lei:<LEI>, or sec_series:<id> for a fund with no LEI |
security / isin_basis | string | isin:<ISIN> held, and how the ISIN was found (filed, gleif, or built from the CUSIP) |
issuer_lei / issuer_name | string | The issuer of the security |
title | string | The holding's title, as filed |
period | date | The report's period end |
known_from / known_until | timestamp | When the report became known, and when an amendment replaced it |
side / option_type | string | Long or short; put or call for an option |
asset_category | string | N-PORT asset category, e.g. EC (equity), DBT (debt) |
quantity / quantity_unit | number / string | Balance held and its unit |
value_usd / pct_of_net_assets | number | Value in US dollars and share of the fund's net assets |
holder_net_assets | number | The fund's net assets |
accession | string | The SEC filing |
dataset_quarter / net_assets / holdings_rows | string / number / integer | Per filing in each edition: the SEC data set, the fund's net assets and its number of holdings |
Use cases
- Who holds a security. List the funds holding an ISIN at their latest report known on a day.
- Look-through exposure. See a fund of funds' underlying positions, and break them down by country, issuer type or asset category.
- Manager-level views. Add up what all the funds of a management company hold, by security or issuer.
Delivery
- REST API (rollout): holdings, holders, exposure, exposure breakdown and manager exposure, as of a day, JSON, with an API key
- MCP tools (rollout): entity_holdings, entity_holders, fund_exposure, fund_exposure_breakdown and manager_exposure, read-only
- InfoTrie console: one edition per quarterly SEC data set, its rows and quality status
- On the Enterprise and Bespoke plans
Frequently asked questions
Is a fund that sold a security still listed as a holder?
No. Each fund is read from its latest report known on the day asked, for a period no older than 200 days: a fund that sold the security in its last report, or stopped reporting, is not a holder.
Are CUSIPs served?
No. Securities are named by ISIN; a CUSIP is only used to find the ISIN, and the answer says how the ISIN was found.
Are GICS sectors included?
No. Breakdowns use the country, issuer type and asset category as filed with the SEC.
See also
- Filing & Regulatory — the data pillar this dataset belongs to
- Form 13F Institutional Holdings
- Legal Entity Relationships (GLEIF Level 2)
- Legal Entities (GLEIF Level 1)
- Bond Reference Data (Terms)
- API reference (entities) — API documentation