How do I get the calendar-year returns of a fund by ISIN?
Year-by-year returns of any fund or ETF versus its benchmark from its ISIN, as JSON arrays: data.calendarReturns.years, .fund and .benchmark.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.calendarReturns.years in the JSON response (related fields: data.calendarReturns.fund, data.calendarReturns.benchmark). The three arrays mirror the discrete-performance table that KIDs and factsheets must print, in the same order. 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.calendarReturns.years | string[] | Calendar years, oldest first. |
data.calendarReturns.fund | number[] | Fund return per year in percent. |
data.calendarReturns.benchmark | (number or null)[] | Benchmark return per year, null where not published. |
Sample for iShares Core MSCI World UCITS ETF (IE00B4L5Y983):
json"calendarReturns": {"years": ["2020", "2021", "2022", "2023", "2024", "2025"],"fund": [15.9, 21.9, -18.0, 23.9, 18.7, 21.2],"benchmark": [15.9, 21.8, -18.1, 23.8, 18.7, 21.1]}
Where the figure comes from
The three arrays mirror the discrete-performance table that KIDs and factsheets must print, in the same order. Where the fund house also publishes the NAV history, the years are checked against it. The ongoing year is not included until it closes.
The request
bashcurl -s --max-time 300 https://fundfactsapi.com/api/v1/funds/IE00B4L5Y983 \-H "Authorization: Bearer $FUNDFACTS_API_KEY" | jq '.data.calendarReturns'
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']['calendarReturns']['years'])
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.calendarReturns.years);
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
- Returns are in the share-class currency, as the document states them.
- A young fund has fewer years; a fund launched mid-year has no partial first year unless the document prints one.
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]}'