Put filed statements into a model without losing context
Use this API when a model or screen needs a filed income statement, balance sheet, or cash-flow statement in a normalized shape. Keep the period, unit, and filing context with every row: a statement-looking number alone is not enough for a filed model.Retrieve one statement for a defined period
statement such as income_statement, balance_sheet, or cash_flow. Use period=annual or quarterly, and fy, fy_from, or fy_to for the fiscal slice. Expect statement rows with period metadata, tag, taxonomy, label, unit, values, provenance, completeness, freshness, materialization, requestId, and traceparent in the default view.
For all three core statements from the same requested slice:
Choose the appropriate contract
US-GAAP 10-K/10-Q filers are resolved in the standard path. Where applicable, the statement routes support IFRS foreign private issuers through
ifrs-full 20-F/6-K coverage. That does not make accounting policies or issuer-specific presentations automatically comparable.
SDK and MCP paths
The JavaScript SDK providesclient.statements, client.allStatements, and client.companyFinancials. Hosted MCP offers statements.get for a focused statement and companies.financials for one company or a supported batch. In both cases, ask for the reporting period and citation fields rather than only a numeric summary.
Modeling caveats
- Balance-sheet values are point in time; income-statement and cash-flow values can be duration or year-to-date. Read
periodBasis, start/end dates, unit, form, and fiscal year before combining them. - A missing normalized row is not zero. It can reflect a presentation, taxonomy, coverage, or extraction limitation.
view=agentintentionally removes metadata envelopes. Use the default response for evidence storage and audit work.- The filing and relevant notes remain primary evidence for accounting policy, segment disclosures, unusual periods, and nonstandard labels.

