FundFacts API vs LSEG (Refinitiv / Lipper) for fund data

At a glance

The enterprise database

Lipper's value is breadth and history: tens of thousands of share classes across every domicile, consistent classification, decades of performance, and integration with the rest of LSEG's market data. If you need to rank a fund against its global peer group over twenty years, that is the class of product to license.

The narrow API

FundFacts API answers a different question: "what does this fund's management company currently say about it?" One ISIN returns the document set as JSON, with the KID risk indicator, the ongoing charges, holdings, exposures and returns as printed. The trade-offs are deliberate:

• Coverage follows the issuers whose documents are public and readable; see coverage.
• History is what the document set carries, plus a daily NAV series where the issuer publishes one.
• No peer groups; profile.category is a composed label, not a ranking universe.

Building on it

ts
const res = await fetch("https://fundfactsapi.com/api/v1/funds/LU0106235293", {
  headers: { Authorization: `Bearer ${process.env.FUNDFACTS_API_KEY}` },
});
const { data } = await res.json();
console.log(data.riskRating, data.headlineMetrics.ter, data.topHoldings.length);

The use-case pages show how screeners, look-through tools and client reports are assembled from these fields.