Comparison

FundFacts API vs stock market data APIs for funds and ETFs

Developer-friendly market data APIs are excellent for what they were designed for: equity prices, fundamentals and tickers. Funds are a different domain — keyed on ISIN, documented in KIDs and factsheets, with share classes and monthly disclosure. This page explains the gap and where each tool fits.

At a glance

CriterionFundFacts APIEquity market data APIs (Alpha Vantage, Financial Modeling Prep, Twelve Data, EODHD and similar)
Primary keyAny fund or ETF ISIN, one REST callExchange ticker (often US-centric); ISIN support varies by provider
UniverseUCITS funds and ETFs with public document sets, US products progressivelyListed equities and ETFs, mostly US exchanges; unlisted mutual funds partially or not at all
PricesDaily NAV series where the issuer publishes one; no intradayIntraday and end-of-day prices, the core product
Fund-specific fieldsKID risk indicator, ongoing charges, distribution policy, share class, benchmark, calendar returns vs benchmarkGenerally not available or limited to expense ratio and top holdings for US ETFs
HoldingsFull constituents where published, with sector and country tablesTop holdings for major US ETFs on some plans; European ETFs often missing
RefreshReloaded from the issuer's current documents every 24 hours; response carries dataAsOfReal-time to daily for prices
OnboardingSelf-serve: free key in a minute, no contract, card only for paid plansSelf-serve API keys with free tiers
PricingPublished: Free $0 (10 requests/day), Pro $49/month, Scale $299/month, metered enterprise $0.01/requestPublished tiers, typically priced by requests per minute or day

Why funds do not fit a ticker-first API

A ticker identifies a listing. An ETF listed on Xetra, the LSE and Borsa Italiana has three tickers and one ISIN per share class; a mutual fund has no ticker at all in most of Europe. The facts users ask about — TER, risk indicator, replication, Acc or Dist, benchmark, holdings — live in regulatory documents, not in exchange feeds. Equity APIs can add an ETF profile endpoint for large US products, but the long tail of UCITS share classes is outside their model.

Where the equity APIs are better

  • Intraday and historical prices for listed ETFs, including volume and corporate actions.
  • Equity fundamentals for the companies inside a fund, if you want to enrich look-through results.
  • Broader coverage of US-listed products and crypto.

Where FundFacts API fits

python
import os, requests
r = requests.get(
"https://fundfactsapi.com/api/v1/funds/IE00B3RBWM25",
headers={"Authorization": f"Bearer {os.environ['FUNDFACTS_API_KEY']}"},
timeout=180,
)
data = r.json()["data"]
print(data["keyFacts"]["distribution"], data["headlineMetrics"]["ter"], data["riskRating"])

The response is the fund's own disclosure as JSON. Combine it with a price API for charts and you have both halves of a fund page: what it is, and what it trades at.

Verdict

Use an equity market data API for prices and company fundamentals. Use FundFacts API when the question is about the fund itself — fees, risk indicator, share class, holdings, exposures — keyed on the ISIN your users actually have.
Descriptions of other providers are based on their public websites and documentation as of September 2026 and may be out of date; check the vendor for current features and pricing. All product names are trademarks of their respective owners. FundFacts API is not affiliated with any of them. Nothing here is investment advice.

Try it on your own ISINs

One request returns key facts, holdings, risk and performance as JSON. Free plan, no card.