Choose a Free Financial Statements API
You Can Trust如何选择值得信赖的
免费财务报表 API
Evaluate coverage, periods, filings, normalization, limits, and accounting quality before you integrate.
接入前应评估报表覆盖范围、报告期、原始申报文件、字段标准化、请求频率限制与会计数据质量，
判断接口能否作为稳定的数据源。
Free financial statements API: the short answer免费财务报表 API：先看结论
A dependable financial statements API should return the income statement, balance sheet, and cash-flow statement as one accounting package. The three statements need compatible company identifiers, fiscal periods, currencies, units, consolidation scope, and source filings. The real test is not whether an endpoint returns JSON, but whether the statements reconcile and retain enough accounting context for an analyst or agent to explain every total.
可靠的财务报表 API 应把利润表、资产负债表和现金流量表作为一套相互关联的会计数据提供。三张报表需要采用一致的公司标识、财务报告期、币种、计量单位、合并范围和来源文件。真正需要验证的并不是接口能否返回 JSON，而是报表之间能否完成勾稽，以及是否保留了足够的会计上下文，使分析人员或智能体能够解释每个合计数。
Expect caps on companies, history, fields, downloads, requests, or reuse. Confirm them before coding.
Income, balance sheet, and cash flow data should share company identifiers, currencies, fiscal periods, and source links.
When normalized fields disagree, the filing and its reported units remain authoritative.
Assets should equal liabilities plus equity, and cash-flow movements should explain changes in cash after scope and FX effects.
免费套餐通常会限制可查询公司数量、历史数据范围、返回字段、下载量、请求配额或数据再利用权限，接入前应逐项确认。
利润表、资产负债表和现金流量表中的公司标识、币种、财务报告期及原始文件链接应保持一致。
若标准化后的字段彼此冲突，应以原始申报文件及其披露的计量单位为准。
资产应等于负债与所有者权益之和；在考虑合并范围和汇率影响后，现金流变动应能够解释现金余额的变化。
What should a financial statements API include?财务报表 API 应该包含哪些数据？
Begin with income, balance-sheet, and cash-flow data for annual and interim periods. The response should identify the period start and end, fiscal year and quarter, filing date, currency, unit scale, form type, consolidation scope, and source document. Instant facts and duration facts must remain distinct. Without that context, a correct number may still be assigned to the wrong quarter or compared with an incompatible value.
基础数据应包括年度和中期报告期的利润表、资产负债表及现金流量表。响应还应标明报告期起止日期、财年与季度、文件提交日期、币种、计量单位及数量级、申报表类型、合并范围和原始文件链接。时点型数据与期间型数据必须分开处理；缺少这些上下文时，数值即使本身正确，也可能被放入错误季度，或与口径不兼容的数据比较。
Look for revenue, costs, gross profit, operating expenses, operating income, non-operating items, interest, taxes, net income, and basic and diluted shares. Quarterly values should represent the quarter itself, not an unlabeled year-to-date duration. Distinguish reported line items from calculated margins and subtotals.
Assets, liabilities, and equity are instant facts. Verify cash, receivables, inventory, property, goodwill, debt, leases, deferred items, retained earnings, and non-controlling interests. The provider should preserve classifications and make the accounting equation testable.
Separate operating, investing, and financing activities, then identify exchange-rate effects, discontinued operations, and the opening and closing cash definitions. Free cash flow is usually derived and should not replace reported operating cash flow and capital expenditure fields.
Companies may report the same concept under different labels or use custom taxonomy extensions. A useful API returns standardized fields while preserving the original concept, label, context, dimensions, and source value for audit.
One filing may contain current and comparative periods, while a later amendment may revise only selected facts. Keep filing identity and version on every record so a newer document does not silently rewrite historical analysis.
重点检查营业收入、成本、毛利、营业费用、营业利润、营业外项目、利息、所得税、净利润，以及基本和稀释后股数。季度数据应代表单个季度，而不是没有标注的年初至今累计数；企业原始披露科目也应与计算得出的利润率和小计分开。
资产、负债和所有者权益属于时点型数据。应核对现金、应收账款、存货、固定资产、商誉、债务、租赁负债、递延项目、留存收益和少数股东权益，并保留流动与非流动分类，使会计恒等关系能够直接验证。
分别处理经营、投资和融资活动现金流，并识别汇率影响、终止经营以及期初和期末现金的定义。自由现金流通常是计算指标，不能替代企业披露的经营现金流和资本性支出。
不同公司可能使用不同名称披露同一概念，也可能采用自定义会计分类扩展。可靠的 API 应提供标准化字段，同时保留原始概念、标签、上下文、维度和来源数值，以便审计。
一份申报文件可能同时包含本期和比较期数据，后续修订也可能只调整部分科目。每条记录都应保留文件身份和版本，避免新文件悄然改写此前的历史分析。
How to reconcile the three financial statements如何完成三张财务报表的勾稽
Reconciliation should be performed on one issuer, one consolidation scope, one currency and unit scale, and one compatible filing version. A failed equation does not immediately prove that the source is wrong: the API may have dropped a line item, reversed a sign, mixed parent-only and consolidated facts, selected the wrong comparative period, or mapped cash definitions inconsistently.
三表勾稽必须限定在同一发行人、同一合并范围、同一币种和数量级，以及相互兼容的申报版本内。恒等关系不成立时，不能立即认定原始文件错误；接口可能漏掉了科目、颠倒了正负号、混用了母公司与合并口径、选择了错误比较期，或采用了不一致的现金定义。
Worked balance-sheet example资产负债表勾稽实例
Suppose reported assets are 1,000, liabilities are 600, and equity attributable to all owners is 400. The equation assets = liabilities + equity balances: 1,000 = 600 + 400. If a normalized API returns liabilities of 560 because it omitted 40 of lease liabilities, the apparent residual is 40. Do not plug that gap into “other liabilities” automatically. Trace the missing source concept, classification, context, and calculation role first.
假设公司披露资产 1,000、负债 600、归属于全部所有者的权益 400，则会计恒等式成立：1,000 = 600 + 400。如果标准化接口因为漏掉 40 的租赁负债，只返回负债 560，就会出现 40 的表面差额。不能为了让报表平衡而自动把差额塞入“其他负债”，应先追查缺失科目的原始概念、分类、会计上下文和计算关系。
Equity also needs the correct perimeter. Parent-shareholder equity may exclude non-controlling interest while total equity includes it. The equation can fail when an API compares consolidated assets and liabilities with parent-only equity. Store both fields when reported and identify which one participates in the filing's calculation tree.
所有者权益还需要使用正确范围。归属于母公司股东的权益可能不含少数股东权益，而所有者权益合计通常包含。若接口用合并资产和负债去匹配仅归属母公司的权益，恒等式就会失败。企业同时披露两项数值时应分别保存，并标明哪一项参与原申报文件的计算关系。
Worked cash roll-forward example现金余额衔接实例
Assume beginning cash is 120, operating cash flow is +80, investing cash flow is −50, financing cash flow is +10, and exchange-rate effects are −2. Ending cash under that statement definition is 120 + 80 − 50 + 10 − 2 = 158. The API should expose all five components and a reconciliation status, not merely return operating cash flow and ending cash.
假设期初现金为 120，经营活动现金流为 +80，投资活动现金流为 −50，融资活动现金流为 +10，汇率变动影响为 −2，则按照现金流量表口径计算的期末现金为 120 + 80 − 50 + 10 − 2 = 158。接口应返回全部五个组成项和勾稽状态，而不是只提供经营现金流与期末现金。
The balance-sheet cash line might still be 160 if the cash-flow statement includes or excludes restricted cash differently. That two-unit difference can be legitimate when the filing provides a reconciliation table. Preserve the balance-sheet cash, cash-flow cash definition, restricted cash, and source note separately; forcing both statements to the same field would destroy useful accounting information.
如果现金流量表与资产负债表对受限现金的纳入方式不同，资产负债表现金仍可能是 160。只要原文件提供相应勾稽表，这 2 个单位的差异就可能合理。应分别保存资产负债表现金、现金流量表的现金定义、受限现金和来源附注；强行把两张报表映射到同一个字段，反而会丢失有价值的会计信息。
Net income links require scope and presentation checks净利润衔接需要核对范围与列报
Net income can appear on the income statement and as the starting point of the indirect cash-flow statement, but the values may differ when one is attributable to the parent, one includes non-controlling interests, or discontinued operations and presentation labels differ. Reconcile by source concept and scope before treating a mismatch as an error.
净利润既可能出现在利润表，也可能作为间接法现金流量表的起点。但如果一项仅归属于母公司、另一项包含少数股东权益，或终止经营与列报标签不同，数值就可能不一致。应先依据来源概念和合并范围完成核对，再判断差异是否属于错误。
Choose the right source layer选择适合的财务报表来源层
| Route路线 | Strength优势 | What still needs validation仍需验证 |
|---|---|---|
| SEC filing and XBRL factsSEC 申报与 XBRL 数据项 | Primary US filing evidence, original concepts, contexts, dimensions, units, calculation relationships, and accessions.美国公司一手申报证据、原始概念、上下文、维度、单位、计算关系和申报编号。 | Statement presentation, extensions, duplicates, versions, period selection, and mapping into application fields.报表列报、自定义扩展、重复项、版本、报告期选择与应用字段映射。 |
| Normalized statements API标准化财务报表 API | Consistent JSON, common line items, multi-company or multi-market queries, pagination, and faster product integration.一致的 JSON、通用报表科目、跨公司或多市场查询、分页与更快的产品接入。 | Source links, mapping policy, unmapped facts, sign conventions, statement equations, restatements, free limits, and licensing.来源链接、映射规则、未映射数据、正负号、报表恒等式、重述、免费限制与许可。 |
| Issuer report and notes发行人报表与附注 | Official presentation, accounting policies, non-GAAP reconciliation, segment detail, and explanations for unusual balances.官方列报、会计政策、非 GAAP 勾稽、分部细节与异常余额说明。 | Document version, publication time, machine extraction, table structure, and how presentation values map to regulatory facts.文档版本、发布时间、机器提取、表格结构，以及展示值如何映射到监管数据项。 |
Show the source period, currency, unit, filing, reported versus normalized label, and reconciliation status.
Use compatible periods and versions, preserve derivation formulas, and block ratios when required inputs fail reconciliation.
Retain original concepts, contexts, dimensions, source documents, mapping decisions, exceptions, and every later correction.
Return the value with statement, period, scope, source, confidence, and any unresolved imbalance instead of presenting one bare number.
展示来源报告期、币种、单位、申报文件、原始或标准化标签，以及勾稽状态。
使用兼容的报告期和版本，保留派生公式；必要输入未通过勾稽时，应阻止继续计算比率。
保留原始概念、上下文、维度、来源文件、映射决策、例外与后续所有更正。
数值应同时附带所属报表、期间、范围、来源、置信度和未解决差异，不能只返回一个裸数字。
Validate accounting meaning, not just JSON shape不仅要核验 JSON 结构，还要核验会计含义
| Criterion评估项 | What to verify核验内容 | Common free-tier trade-off免费套餐的常见限制 | Test验证方法 |
|---|---|---|---|
| Periods报告期 | Fiscal dates, duration, annual versus quarterly scope.财务报告期的起止日期、期间长度，以及年度与季度数据的覆盖范围。 | Calendar dates presented as fiscal dates.将日历日期误作财务报告期日期。 | Compare several issuers with source filings.选取多家发行人，将接口数据与原始申报文件逐一核对。 |
| Units计量单位 | Currency, thousands or millions, shares, and per-share values.币种、以千或百万为数量级的金额、股数及每股数值。 | Silent scaling or mixed currencies.未披露数量级换算，或混用不同币种。 | Recalculate totals from raw reported values.使用原始披露值重新计算各合计项。 |
| Statement linkage报表勾稽 | Accounting equation, net income links, cash roll-forward, and share-count consistency.会计恒等关系、净利润衔接、现金余额变动与股数一致性。 | Each statement is normalized independently.三张报表被分别标准化，彼此无法勾稽。 | Run cross-statement equations for sampled filings.对抽样财报运行跨报表勾稽与恒等关系检查。 |
| Taxonomy mapping科目映射 | Original concept, standardized field, dimensions, sign, and calculation role.原始概念、标准化字段、维度、正负号和计算关系。 | Custom concepts dropped or forced into the wrong field.自定义科目被丢弃，或被强行映射到错误字段。 | Trace unusual issuer-specific line items through normalization.选择企业特有科目，检查其完整的标准化映射过程。 |
| Restatements财报重述 | Original facts, later amendments, and point-in-time history.初始披露的数据项、后续修订，以及各历史时点可获得的数据版本。 | Latest value overwrites prior knowledge.最新数值覆盖历史时点当时可获得的数据。 | Query an amended filing and retain both versions.查询一份经过修订的申报文件，并保留修订前后的两个版本。 |
| Completeness完整性 | Required totals, null reasons, filing coverage, and reconciliation status.必要合计项、空值原因、文件覆盖情况和勾稽状态。 | Missing facts converted to zero.缺失科目被直接转换为零。 | Compare field availability by form, sector, and year.按申报表类型、行业和年份统计字段可用率。 |
| Limits请求限制 | Minute, daily, pagination, bulk, and concurrency quotas.每分钟和每日请求配额，以及分页、批量请求和并发限制。 | Slow backfills or incomplete universes.历史数据回填缓慢，或目标公司范围无法完整覆盖。 | Plan a full refresh and exercise 429 retries.估算一次全量刷新所需的请求量，并验证 HTTP 429 重试机制。 |
A safer integration pattern for statement data更稳健的财务报表数据接入方案
Start from filing identity, form type, acceptance time, reporting entity, and fiscal-period metadata. Attach facts to that immutable filing context before selecting which version belongs in a current company view.
Store the payload, source URL, retrieval time, original concept, context, dimensions, filing identity, and normalized fields separately so mappings and corrections remain auditable.
Tickers change, so prefer a legal entity identifier. Include period dates, instant or duration type, form, filing version, currency, unit, and dimensions. Do not collapse distinct segment or class-of-stock facts into one value.
Select a consistent filing version, map line items, retain unmapped facts, and run statement and cross-statement checks. Publish a reconciliation status instead of silently accepting an unexplained imbalance.
Store amendments and restatements as new versions. Monitor field coverage, mapping changes, balance failures, stale filings, and provider schema changes so a technically successful pipeline does not deliver degraded statements.
从文件身份、申报表类型、监管系统接收时间、财务报告主体和报告期元数据入手。先把数据项关联到不可变的文件上下文，再判断公司当前视图应采用哪个版本。
将供应商返回的原始数据、来源网址、获取时间、原始会计概念、上下文、维度、申报文件标识和标准化字段分别存储，确保字段映射和后续更正可追溯、可审计。
股票代码可能变化，因此应优先采用法定实体标识。数据键还应包含报告期起止日期、时点或期间类型、申报表、文件版本、币种、单位和维度，不能把不同业务分部或不同股权类别的数据折叠为一个值。
选择口径一致的文件版本，映射报表科目，同时保留尚未映射的原始数据，并运行报表内部及跨报表检查。出现无法解释的不平衡时，应返回勾稽状态，而不是静默接受。
修订文件与财报重述应保存为新版本。同时监控字段覆盖率、映射变化、报表不平、长期未更新的文件和供应商数据结构变化，避免接口请求虽然成功，报表质量却持续下降。
Use QVeris to discover statement data capabilities用 QVeris 查找财务报表数据服务能力
Provider directories go stale, and APIs name accounting concepts differently. QVeris helps developers and agents discover income-statement, balance-sheet, cash-flow, filing, and company-fact capabilities, then inspect their inputs and constraints before calling them. It can simplify access across tools, but the application still owns filing selection, taxonomy mapping, reconciliation, version history, and the accounting explanation presented to users.
服务商目录中的信息可能已经过时，同一财务报表项目在不同 API 中也可能使用不同名称。QVeris 可帮助开发者和智能体发现利润表、资产负债表、现金流量表、监管文件和公司数据项能力，并在调用前检查输入与限制。它能够简化跨工具的数据访问，但文件版本选择、会计科目映射、报表勾稽、版本历史以及最终向用户作出的会计解释，仍由应用方负责。
- Search for income statements, balance sheets, cash flow statements, filings, or company facts rather than relying on a vendor name.
- Inspect identifiers, periods, fields, authentication, pagination, and limits before integration.
- Keep your provider adapter, raw source, and provenance trail even when capability discovery and calling are streamlined.
- 按利润表、资产负债表、现金流量表、申报文件或公司基本面数据等具体需求进行搜索，不要只按服务商名称查找。
- 接入前应检查标识符、报告期、字段、鉴权方式、分页机制和请求频率限制。
- 即使数据服务的查找和调用流程已经简化，也应保留服务商适配器、原始数据来源和数据溯源链路。
FAQ常见问题
Yes. Public filing sources and commercial free tiers can provide statements, but normalization, international coverage, history, limits, and usage rights vary.
Sometimes. Confirm licensing, attribution, storage, redistribution, service reliability, request capacity, and a fallback plan before launch.
Some filings report year-to-date duration facts. A provider must derive the standalone quarter carefully or label the value as cumulative; otherwise quarter-over-quarter analysis will be wrong.
Yes. Retain the original concept, context, dimensions, unit, and source filing beside the normalized field. They are necessary when a mapping is disputed or an issuer uses a custom extension.
Run the accounting equation, compare net income across statements, reconcile opening and closing cash, and check share-count and foreign-exchange effects. Document legitimate differences rather than forcing equality.
Keep the original and amended filing as separate versions with acceptance timestamps. A current view can prefer the latest version, while historical queries retrieve what was available then.
有。通过公共申报数据源和商业数据服务的免费套餐都可以获取财务报表，但各项服务在字段标准化、国际市场覆盖范围、历史数据跨度、请求配额和使用权限方面差异很大。
视情况而定。上线前应确认许可条款、来源标注要求、数据存储与再分发权限、服务可靠性和请求容量，并准备备用方案。
部分申报文件披露的是年初至今累计期间数据。供应商需要谨慎计算单季数值，或明确标注其为累计值；否则环比分析会得出错误结论。
需要。原始概念、会计上下文、维度、单位和来源文件应与标准化字段一并保存。当映射存在争议或企业使用自定义扩展时，这些信息是核验依据。
可以验证会计恒等关系、比较不同报表中的净利润、勾稽期初与期末现金，并检查股本和汇率影响。对于合理存在的差异，应保留解释，而不是强行调平。
原始文件与修订文件应作为独立版本保存，并记录监管系统接收时间。当前视图可以优先展示最新版本，但历史查询应返回当时已经公开的数据。