Free Mutual Fund Data API
Sources, Coverage & Examples免费共同基金数据 API
数据源、覆盖范围与示例
Compare free mutual fund APIs by NAV, history, holdings, region, authentication, and limits—then test a real JSON request.
按净值、历史数据、持仓、地区、鉴权与限额比较免费基金 API，
并用真实 JSON 请求验证接口。
TL;DR摘要
A callable mutual fund REST API with clear coverage, stable identifiers, documented limits, and JSON responses.
Some sources need no key; others offer a free tier. Always verify quotas, licensing, attribution, and commercial-use terms.
India-focused APIs commonly expose daily NAV history. U.S. sources may emphasize SEC filings, identifiers, and holdings.
Request one known fund, inspect dates and identifiers, then confirm pagination, errors, freshness, and rate limits.
可直接调用的基金 REST API，以及清晰的覆盖范围、稳定标识符、限额说明和 JSON 返回。
有些接口无需密钥，有些仅提供免费额度；必须核对配额、许可、署名和商业使用条款。
印度接口常见每日净值历史；美国数据源更常围绕 SEC 申报、基金标识符与持仓。
先请求一只已知基金，核对日期和标识符，再验证分页、错误、数据新鲜度与限流。
What a free mutual fund data API should cover免费基金数据 API 应覆盖哪些内容
The exact keyword hides several distinct data needs. Define the minimum dataset before choosing a provider: current NAV, historical NAV, fund metadata, portfolio holdings, fees, risk metrics, or regulatory filings. No single free source is guaranteed to cover every region and field.
“基金数据 API”背后包含多种需求。选择接口前，应先确定最低数据集：最新净值、历史净值、基金元数据、组合持仓、费用、风险指标或监管申报。没有一个免费数据源能保证覆盖所有地区和字段。
Mutual fund records should be centered on the legal fund and share class, not a display name alone. Retail, institutional, accumulating, distributing, hedged, and currency-denominated classes can follow the same portfolio while having different NAV, expenses, minimums, sales loads, eligibility, and investor cash flows.
共同基金数据应以法律基金和份额类别为中心，不能只依赖展示名称。零售、机构、累积、分红、汇率对冲和不同币种份额可能跟踪同一组合，却拥有不同净值、费用、最低投资额、销售负担、投资者资格和现金流。
Latest and historical mutual fund NAV API
Check valuation date, update schedule, currency, adjusted values, missing-day behavior, and whether inactive schemes remain queryable.
Mutual fund holdings API free coverage
Holdings are usually less frequent than NAV. Verify reporting period, point-in-time availability, security identifiers, weights, and filing source.
Fund identity and regional scope
Scheme codes, tickers, CUSIPs, ISINs, share classes, and fund-family identifiers are not interchangeable. Match the API to the market your application serves.
Fees, loads, minimums, and eligibility
Separate expense ratio, management fee, front- or back-end load, redemption fee, platform fee, minimum initial and subsequent investment, investor type, and waiver period. A single “fee” field cannot represent the full cost contract.
Distributions and total-return history
Preserve income and capital-gains distribution types, ex and payment dates, currency, and reinvestment method. Price or NAV change alone can understate investor return when distributions are paid.
Fund status and predecessor history
Capture launch, closure to new investors, merger, liquidation, renamed classes, and predecessor or successor IDs. Historical research needs inactive funds and the date each status became knowable.
最新与历史基金净值 API
检查估值日期、更新计划、币种、复权口径、缺失交易日处理方式，以及已终止基金是否仍可查询。
免费基金持仓 API 的覆盖范围
持仓数据的更新频率通常低于净值数据，应核对报告期、时点数据、证券标识符、权重和申报来源。
基金身份与地区范围
基金代码、Ticker、CUSIP、ISIN、份额类别和基金家族标识符不能混用，应让接口与目标市场匹配。
费用、销售负担、最低投资额与资格
区分费率、管理费、前端或后端销售费、赎回费、平台费、首次与追加最低投资额、投资者类型和费用减免期。单一“费用”字段无法表达完整成本契约。
分派与总回报历史
保存收益与资本利得分派类型、除权日、支付日、币种和再投资方式。基金发生分派时，只看价格或净值变化会低估投资者回报。
基金状态与前身历史
记录成立、暂停新投资者申购、合并、清盘、份额改名和前身或后继 ID。历史研究还需要已终止基金，以及每个状态首次可知的日期。
Free mutual fund data API sources to evaluate值得评估的免费基金数据 API 来源
Treat this as a regional shortlist, not a universal ranking. Test one active class, one inactive or merged scheme, one distribution date, one class with a load or minimum, and one holdings report. Compare identifier resolution, NAV and publication dates, currency, status, pagination, corrections, and whether the source is reporting the legal class you requested.
下表是按地区核验的候选清单，不是全球统一排名。可测试一只存续份额、一只终止或合并基金、一个分派日、一只有销售费或最低投资额的份额，以及一份持仓报告，比较标识解析、净值与发布日期、币种、状态、分页、更正，以及来源是否真的对应所请求法律份额。
| Source数据源 | Coverage覆盖内容 | Access访问方式 | Verify first优先核对 |
|---|---|---|---|
| MFapi.in | Indian schemes, search, latest NAV, and NAV history.印度基金、搜索、最新净值与净值历史。 | REST/JSON; documentation says no API key.REST/JSON；文档说明无需 API 密钥。 | Rate limits, caching, AMFI scheme codes.限流、缓存与 AMFI 基金代码。 |
| MFData.in | Indian NAV, holdings, sectors, ratios, and analytics.印度基金净值、持仓、行业、比率与分析。 | Open REST API with published per-IP limits.开放 REST API，并公开 IP 限额。 | Endpoint-specific quotas and field provenance.不同端点配额与字段来源。 |
| SEC EDGAR APIs | U.S. filings and structured submission data; not a ready-made daily NAV feed.美国基金申报与结构化提交数据；不是现成的每日净值源。 | Official JSON APIs without authentication keys.官方 JSON API，无需鉴权密钥。 | Form coverage, identifiers, parsing, fair-access policy.表单范围、标识符、解析与公平访问政策。 |
| Commercial free tiers | May add U.S./global profiles, holdings, prices, or normalized identifiers.可能补充美国/全球档案、持仓、价格或标准化标识符。 | Usually signup, API key, and monthly quota.通常需要注册、API 密钥与月度配额。 | Licensing, redistribution, historical depth, overage price.许可、再分发、历史深度与超额价格。 |
Choose the dataset by mutual fund use case按基金数据使用场景选择接口
A source can be excellent for daily NAV and still be unsuitable for portfolio research. Define the decision the application must support, then require the fields and dates that make that decision reproducible.
一个数据源可能非常适合每日净值展示，却不适合组合研究。先明确应用需要支持的判断，再要求接口提供能够复现该判断的字段和日期。
Require the exact share class, valuation date, publication time, currency, fund status, and a documented rule for weekends and holidays. Do not label a daily NAV as a live market price.
Require the reporting period, publication date, security identifiers, portfolio weights, cash treatment, derivatives coverage, and an explicit “unknown” state for undisclosed positions.
Keep official NAV, income distributions, capital-gains distributions, fees, and reinvestment assumptions separate. A return series is only comparable when its adjustment method is stated.
Return evidence with every answer: fund and class IDs, source date, retrieval time, currency, revision status, and the endpoint used. The agent should abstain when the requested class cannot be resolved.
必须包含准确的份额类别、估值日期、发布时间、币种和基金状态，并说明周末及节假日如何处理。每日净值不能标成实时市场价格。
必须包含报告期、发布日期、证券标识符、组合权重、现金处理方式和衍生品覆盖范围；未披露的持仓应明确标记为“未知”，不能当作零持仓。
官方净值、收益分派、资本利得分派、费用与再投资假设需要分别保存。只有调整方法清楚的回报序列才适合横向比较。
每次回答都应附带基金与份额 ID、源数据日期、抓取时间、币种、修订状态和调用端点。无法解析目标份额时，Agent 应停止推断并提示用户确认。
Suppose a distributing share class closes at a NAV of $20.00, pays a $0.50 distribution, and reports $19.60 on the next valuation date. The raw NAV change is −2.0%, but an investor who received or reinvested the distribution has an approximate one-period return of ($19.60 + $0.50) / $20.00 − 1 = +0.5%. A second accumulating class of the same portfolio may retain the income and show a different NAV path. The API therefore needs a class identifier and distribution record; fund name plus NAV is not enough.
假设某分红型份额前一估值日净值为 20.00 美元，随后每份分派 0.50 美元，下一估值日净值为 19.60 美元。单看净值，变化率为 −2.0%；但投资者若收到或再投资这笔分派，该期间的近似回报为（19.60 + 0.50）÷ 20.00 − 1 = +0.5%。跟踪同一组合的累积型份额可能保留收益，从而呈现不同的净值路径。因此，接口必须同时提供份额标识与分派记录，只有基金名称和净值远远不够。
Mutual fund API Python example and validation steps基金数据接口 Python 示例与验证步骤
1. Test a documented fund identifier
Start with one scheme code from the provider’s own documentation. A minimal Python request is requests.get("https://api.mfapi.in/mf/125497/latest", timeout=20); call raise_for_status() before reading JSON.
2. Validate the response, not just HTTP 200
Check the fund name, identifier, NAV date, numeric types, timezone assumptions, empty histories, pagination, and error shape. Treat a successful transport as different from valid financial data.
3. Cache daily data and record provenance
Mutual fund NAV is normally periodic rather than tick-level. Store retrieval time, provider, endpoint, source date, and raw response so later calculations remain explainable.
4. Re-check terms before production
Free access can change. Confirm current limits, permitted use, attribution, redistribution, service status, and whether your workload needs a paid fallback.
5. Normalize the share-class contract
Store legal fund ID, class ID, scheme code, currency, distribution policy, hedging, fee schedule, minimums, investor eligibility, status, and effective dates separately. Do not inherit attributes from a sibling class without source evidence.
6. Reconcile NAV, distributions, and total return
Check NAV continuity around distributions, mergers, and class events. Build a separate total-return series with documented reinvestment assumptions and keep it distinct from the official NAV history.
7. Preserve first-known and revised records
Keep valuation, publication, processed, and retrieval times plus revision IDs. If a NAV or holding is corrected, store both versions so historical analysis cannot use the correction before it was available.
1. 用文档中的基金标识符测试
从供应商文档给出的基金代码开始。最小 Python 请求可使用 requests.get("https://api.mfapi.in/mf/125497/latest", timeout=20)，读取 JSON 前先调用 raise_for_status()。
2. 验证返回内容，而不只看 HTTP 200
核对基金名称、标识符、净值日期、数值类型、时区假设、空历史、分页和错误结构。传输成功不等于金融数据有效。
3. 缓存每日数据并记录来源
基金净值通常按日或定期更新，而非 Tick 级。保存抓取时间、提供商、端点、源数据日期和原始响应，便于解释后续计算。
4. 上线前重新核对条款
免费访问可能变化。确认最新限额、允许用途、署名、再分发、服务状态，以及业务是否需要付费备用源。
5. 规范份额类别契约
分别保存法律基金 ID、份额 ID、基金代码、币种、分派政策、汇率对冲、费用表、最低投资额、投资者资格、状态和有效日期；没有来源证据时，不能从同一基金的其他份额继承属性。
6. 核对净值、分派与总回报
检查分派、合并和份额事件附近的净值连续性，另行建立再投资假设清晰的总回报序列，并与官方净值历史分开保存。
7. 保留首次可得与修订记录
保存估值、发布、处理和抓取时间及修订 ID。净值或持仓更正时保留两个版本，使历史分析无法在更正实际可得前提前使用。
How QVeris helps connect mutual fund data capabilitiesQVeris 如何帮助连接基金数据能力
QVeris does not manufacture mutual fund records or replace the provider’s license. It helps developers and agents discover available capabilities, inspect their interfaces, and connect the selected external tool through a consistent workflow.
QVeris 不生产基金记录，也不会替代数据提供商的许可。它帮助开发者和 Agent 发现可用能力、检查接口，并通过一致的工作流连接选定的外部工具。
- Open QVeris provider details to inspect relevant financial-data capabilities.
- Inspect fund and class identifiers, regional coverage, dataset types, effective and publication dates, revisions, authentication, and provider documentation before connecting a tool.
- Require the exact share class, currency, dataset, date range, fee or distribution definition, history policy, and evidence fields in each request.
- Keep source names, raw identifiers, timestamps, and validation results with every output; QVeris connectivity does not validate investment suitability.
- 打开 QVeris 服务商详情，查看相关金融数据能力。
- 连接前检查基金与份额标识、地区覆盖、数据集类型、有效与发布日期、修订、鉴权方式和提供商文档。
- 每次请求都应明确份额类别、币种、数据集、日期范围、费用或分派定义、历史规则和证据字段。
- 为每条输出保留数据源、原始标识、时间戳和验证结果；QVeris 的连接能力不代表投资适当性验证。
FAQ常见问题
Yes. Current examples include India-focused no-key APIs and official SEC filing APIs. Coverage, limits, licensing, and readiness for daily NAV or holdings differ.
MFapi.in documents no-key access for Indian scheme search and NAV history. SEC data APIs also require no key, but serve regulatory submissions rather than a normalized daily NAV feed.
Choose a region-appropriate provider, find its scheme identifier, call the documented history endpoint, then validate dates, currency, gaps, pagination, and update frequency.
Sometimes. MFData.in publishes Indian holdings endpoints, while U.S. holdings can originate in SEC filings or commercial free tiers. Reporting periods and licenses vary.
Use an HTTP client such as Requests, set a timeout, raise on non-success status, parse JSON, validate the schema, and cache results according to the provider’s update schedule.
Different share classes can have different currencies, fees, loads, distribution policies, hedging, and eligibility. Resolve the legal class ID and valuation date before treating values as duplicates.
No. NAV is normally an official periodic valuation, often daily, and its publication may follow the valuation time. Preserve valuation and publication dates rather than presenting request time as market freshness.
Keep official NAV and distribution records separate, then calculate total return with an explicit reinvestment convention. Comparing NAV changes alone can omit income and capital-gains payments.
有。当前可见来源包括面向印度市场的免密钥 API，以及美国 SEC 官方申报 API；覆盖范围、限额、许可和是否适合净值/持仓各不相同。
不一定。MFapi.in 文档说明印度基金搜索与净值历史无需密钥；SEC 数据 API 也无需密钥，但主要提供监管申报，而非标准化每日净值。
先选适合目标地区的数据源，找到基金标识符，调用文档中的历史端点，再核对日期、币种、缺口、分页和更新频率。
部分可以。MFData.in 提供印度基金持仓端点；美国持仓可能来自 SEC 申报或商业服务的免费层，报告期和许可需要单独检查。
使用 Requests 等 HTTP 客户端，设置超时，处理非成功状态，解析 JSON，验证字段，并按提供商的更新周期缓存结果。
不同份额类别可能拥有不同币种、费用、销售负担、分派政策、汇率对冲和资格要求。判定重复前，应先解析法律份额 ID 与估值日期。
不是。净值通常是按固定周期、常见为每日计算的官方估值，发布时间还可能晚于估值时点。应保留估值与发布日期，不能把请求时间当成市场时效。
官方净值与分派记录应分开保存，再用明确的再投资规则计算总回报。只比较净值变化，可能遗漏收益和资本利得分派。