How do I get the sector exposure of a fund or ETF by ISIN?
Sector weights (Information Technology, Financials, Health Care…) for any fund or ETF from its ISIN as a JSON array: data.sector, with a rule-based sector tilt label.Updated 12 September 2026 · by FundFacts APIShort answer
Call GET https://fundfactsapi.com/api/v1/funds/{isin} with a bearer API key and read data.sector in the JSON response (related fields: data.profile.sectorTilt). Sector weights come from the monthly factsheet or the product page, using the fund house's own classification (most equity funds use GICS sectors; some use ICB or an in-house scheme). The Free plan gives 15 lookups a month with no card, and the keyless demo endpoint shows the shape for an already-loaded fund.
Where it is in the response
| Path | Type | Meaning |
|---|---|---|
data.sector | Array<{ label, weight }> | Sector weights in percent, in the order the fund house lists them. |
data.profile.sectorTilt | string or null | "Broad" or the dominant sector when one is clearly overweight. |
Sample for iShares Core MSCI World UCITS ETF (IE00B4L5Y983):
json"sector": [{ "label": "Information Technology", "weight": 29.8 },{ "label": "Financials", "weight": 16.46 },{ "label": "Industrials", "weight": 11.03 }],"profile": { "sectorTilt": "Broad" }
Where the figure comes from
Sector weights come from the monthly factsheet or the product page, using the fund house's own classification (most equity funds use GICS sectors; some use ICB or an in-house scheme). Bond funds expose instrument, creditQuality and maturity instead; mixed funds carry assetAllocation too.
The request
bashcurl -s --max-time 300 https://fundfactsapi.com/api/v1/funds/IE00B4L5Y983 \-H "Authorization: Bearer $FUNDFACTS_API_KEY" | jq '.data.sector'
pythonimport os, requestsr = requests.get("https://fundfactsapi.com/api/v1/funds/IE00B4L5Y983",headers={"Authorization": f"Bearer {os.environ['FUNDFACTS_API_KEY']}"}, timeout=300)fund = r.json()print(fund["name"], fund['data']['sector'])
javascriptconst res = await fetch("https://fundfactsapi.com/api/v1/funds/IE00B4L5Y983", {headers: { Authorization: `Bearer ${process.env.FUNDFACTS_API_KEY}` },signal: AbortSignal.timeout(300_000),});const fund = await res.json();console.log(fund.name, fund.data.sector);
Sign up at fundfactsapi.com/signup for a key; the Free plan is 15 lookups a month with no card. Without a key, GET https://fundfactsapi.com/api/v1/demo/funds/IE00B4L5Y983 returns the same payload for funds already in the store (30 calls a minute per IP; it never loads a new fund).
Caveats
- Labels are not forced into one taxonomy, so "Information Technology" (GICS) and "Technology" (ICB) can both appear across funds. Normalise labels in your code if you aggregate across issuers, or let
POST /portfoliodo it. - Weights may not sum to exactly 100 because of cash, derivatives or rounding on the document.
Several funds at once
POST /funds with { "isins": ["…", "…"], "wait": true } returns the same payload for up to 10 ISINs per call on Starter, 50 on Pro and 200 on Scale. One request is counted per ISIN answered. X-RateLimit-Remaining on every response tells you how many are left this month; a 429 rate_limited response carries Retry-After. Search and /me are free.
A fund nobody has requested in the last 24 hours is loaded on demand from the documents the fund house publishes. That first call takes 15 seconds to about 3 minutes; set your client timeout to 300 seconds and do not fire a second request for the same ISIN while the first is running. Every later call within 24 hours returns from the store in well under a second with cached: true.
Everything else in the payload is listed in the field reference.
Verify it yourself
The demo endpoint returns the live payload for a fund that is already in the store, without a key. Everything on this page can be checked against it.bashcurl -s https://fundfactsapi.com/api/v1/demo/funds/IE00B4L5Y983 | jq '{name, asOf: .data.dataAsOf, ter: .data.headlineMetrics.ter, risk: .data.riskRating, top: .data.topHoldings[:3]}'