ETF data API for UCITS ETFs: TER, risk, holdings, returns by ISIN

The fields an ETF data API should return

There is no domicile or ticker field: the ISIN's prefix (IE, LU, DE) usually tells the domicile, and GET /search resolves a ticker. Every key is in the field reference.

One request, one dated payload

bash
curl -s https://fundfactsapi.com/api/v1/funds/IE00B4L5Y983 \
  -H "Authorization: Bearer $FUNDFACTS_API_KEY"

json
{
  "isin": "IE00B4L5Y983",
  "name": "iShares Core MSCI World UCITS ETF",
  "cached": true,
  "generatedAt": "2026-09-02T20:32:58.872Z",
  "expiresAt": "2026-09-03T20:32:58.872Z",
  "data": {
    "keyFacts": {
      "currency": "USD",
      "aum": "USD 151.7bn",
      "inception": "2009-09-25",
      "distribution": "Accumulating",
      "holdings": 1253
    },
    "riskRating": 6,
    "benchmarkName": "MSCI World Index (Net)",
    "headlineMetrics": {
      "ter": "0.20%",
      "volatility3y": "11.8%",
      "sharpe3y": "1.68"
    },
    "metrics": {
      "maxDrawdown": "-16.5%"
    },
    "calendarReturns": {
      "years": ["2023", "2024", "2025"],
      "fund": [23.9, 18.7, 21.2],
      "benchmark": [23.8, 18.7, 21.1]
    },
    "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 }
    ],
    "dataAsOf": "2026-09-01"
  }
}

This is the real payload for iShares Core MSCI World UCITS ETF, trimmed. Money and percentages arrive as printed ("0.20%", "USD 151.7bn"); weights and returns are numbers in percent.

Identifiers: ISIN first

GET /funds/{isin} takes a 12-character ISIN, case-insensitive. Each share class has its own: an accumulating and a distributing class of the same ETF return different key facts, fees and returns. GET /search?q= finds ISINs by exchange ticker (VWCE, EUNL), name, issuer or ISIN prefix among funds already loaded, and is not counted.

Freshness

Each payload is stored for 24 hours: within that window a fund returns in well under a second with cached: true. A cold one is read from the fund house's documents in 15 seconds to 3 minutes, so allow 300 seconds. expiresAt says when the payload goes stale, and data.dataAsOf dates the figures: show that one to your users.

Batch, SDKs and MCP

• Batch: POST /funds with { "isins": [...] } takes up to the plan's batch size (1 on Free, 10 on Starter, 50 on Pro, 200 on Scale, 1,000 on Enterprise). Each fund found counts one request.
• SDKs: npm install @fundfactsapi/sdk, a Python client from GitHub, and React widgets that render the payload.
• MCP: the MCP server puts the same data inside Claude, ChatGPT, Cursor and Claude Code, on every plan, Free included.

What you get vs a stock-market data API

What it is not for

Prices, quotes, intraday NAV (iNAV), volume and corporate actions belong to a market-data API keyed on the ticker. Use one alongside: it says what the ETF trades at, FundFacts API says what the ETF is. Stocks, bonds and indices are not funds and return 404 fund_not_found, free up to as many misses a month as the plan's allowance.

Price

Free is $0: 15 lookups a month, no card, personal use. Starter is $9.99 a month for 500 requests, Pro $49 for 9,000, Scale $249 for 60,000 (VAT included). Commercial use of the data comes with Pro, Scale and Enterprise. One request is counted per fund found. See pricing.

Get started in three steps

1. Check the shape without a key. curl -s https://fundfactsapi.com/api/v1/demo/funds/IE00B4L5Y983 returns the full payload of any fund already loaded.
2. Create a free key. Sign up with an e-mail address or Google. The Free plan gives 15 lookups a month without a card, and the key is in the dashboard.
3. Call it from your code or your assistant. Send GET /api/v1/funds/{isin} with Authorization: Bearer <key>, batch from Starter with POST /funds, or connect the MCP server. The quickstart has curl, TypeScript and Python.