How do I get 1-, 3-, 5- and 10-year annualised returns of a fund by ISIN?
Annualised returns over 1, 3, 5 and 10 years and since inception for any fund or ETF versus its benchmark, from its ISIN as JSON: data.annualisedReturns.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.annualisedReturns in the JSON response. The table is read from the factsheet's annualised (or "average annual") performance block, benchmark column included. 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.annualisedReturns | Array<{ label, fund, index }> | One row per period as printed: "1 Year", "3 Years p.a.", "5 Years p.a.", "10 Years p.a.", "Since Inception". |
Sample for iShares Core MSCI World UCITS ETF (IE00B4L5Y983):
json"annualisedReturns": [{ "label": "1 Year", "fund": 19.57, "index": 19.55 },{ "label": "3 Years p.a.", "fund": 19.82, "index": 19.78 },{ "label": "5 Years p.a.", "fund": 11.05, "index": 10.98 },{ "label": "10 Years p.a.", "fund": 12.97, "index": 12.9 },{ "label": "Since Inception", "fund": 11.12, "index": null }]
Where the figure comes from
The table is read from the factsheet's annualised (or "average annual") performance block, benchmark column included. Labels are kept as printed because fund houses differ ("3 Years p.a.", "3Y annualised", "3 years (ann.)"); match on the leading number when you need a fixed key.
The request
bashcurl -s --max-time 300 https://fundfactsapi.com/api/v1/funds/IE00B4L5Y983 \-H "Authorization: Bearer $FUNDFACTS_API_KEY" | jq '.data.annualisedReturns'
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']['annualisedReturns'])
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.annualisedReturns);
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
- The 1-year row is a plain return, the longer rows are annualised; that is how the documents present them.
- Where the factsheet prints cumulative rather than annualised figures, the cumulative block lands in
cumulativePerformanceand this array may be shorter.
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]}'