FundFacts API vs Bloomberg for fund and ETF data
Bloomberg is the reference for professional market data across every asset class. FundFacts API does one narrow thing: it turns a fund or ETF ISIN into the structured contents of its factsheet and KID. This page explains when the narrow tool is the right one.At a glance
| Criterion | FundFacts API | Bloomberg Terminal and Bloomberg Data License |
|---|---|---|
| Scope | Fund and ETF factsheet data only: key facts, fees, holdings, exposures, risk indicator, performance, risk metrics | All asset classes: real-time and historical prices, fundamentals, news, analytics, fund data, messaging (Terminal); bulk and API reference data (Data License) |
| Input key | Any fund or ETF ISIN, one REST call | Bloomberg identifiers (tickers, FIGI) alongside ISIN, SEDOL, CUSIP |
| Fund holdings | Full constituents where the issuer publishes them, top holdings otherwise | Fund holdings and analytics available within the Terminal and via licensed data products |
| Refresh | Reloaded from the issuer's current documents every 24 hours; response carries dataAsOf | Real-time and end-of-day feeds |
| Delivery | REST JSON, OpenAPI spec, TypeScript types | Terminal desktop application; Data License via files and APIs; B-PIPE for streaming |
| Onboarding | Self-serve: free key in a minute, no contract, card only for paid plans | Sales-led contract; per-seat Terminal subscription; Data License agreements priced by content and usage |
| Pricing | Published: Free $0 (10 requests/day), Pro $49/month, Scale $299/month, metered enterprise $0.01/request | Quoted by Bloomberg sales; not published as a self-serve price list |
| Redistribution | Display in your own product for your users under the terms of service | Governed by the licence; display and redistribution rights are contracted separately |
| AI tooling | AI companion kit (AGENTS.md, Cursor rule, Claude Code skill, OpenAPI, TypeScript types) on paid plans | Bloomberg's own AI features inside the Terminal; developer tooling through licensed APIs |
Where Bloomberg is the right answer
If your users are traders, portfolio managers or analysts who need live prices, fixed-income analytics, news, chat and a single screen for everything, nothing on this page argues against a Terminal. Likewise, if you need firm-wide reference data across equities, bonds, derivatives and funds with a service-level agreement, a Data License is built for that.
Where a narrow API wins
Most fund-facing products do not need any of that. A screener, a client report, a robo-advisor's fund universe or a chatbot that answers "what does this ETF hold?" needs a stable, structured snapshot of what the fund house itself publishes: TER, SRRI, top holdings, sector and country weights, calendar returns.
FundFacts API returns exactly that, keyed on the ISIN your users already have, and the entire onboarding is a sign-up form. A developer can have the first ISIN resolving in an afternoon, and the AI companion kit lets a coding agent scaffold the integration from one prompt.
bash
Honest limits
- No intraday or real-time prices. The NAV series is daily where the issuer publishes one.
- No ratings, analyst research or estimates.
- Coverage depends on the issuer publishing a public document set; see coverage.
- Figures are as published by the management company, which for monthly factsheets means the previous month end.
Using both
Teams that already have a Terminal often still use a lightweight API for the customer-facing product, because Terminal data cannot simply be re-displayed to end clients. Keep Bloomberg on the desk, and feed the product from documents the fund houses publish for the public.