Skip to main content
Retrieve an issuer’s normalized balance sheet, income statement, and cash flow statement together, with US GAAP and IFRS foreign-private-issuer resolution.
Audience: application and coding agent.

Coverage and source scope

Use this route to obtain the three core statements for a common issuer and reporting selection. Choose annual or quarterly cadence and fiscal-year filters before comparing periods. Each statement retains its own rows, units, periods, completeness, and filing provenance, so a bundle does not guarantee that every normalized line item is available or comparable across all three statements. See API conventions and freshness and source evidence.

Bundle interpretation

Supply one issuer identifier and use period, fy / year, or a fiscal-year range to bound the bundle. The response contains the balance sheet, income statement, and cash flow statement as separate normalized surfaces; align rows by their returned reporting periods rather than assuming the same number of observations in each statement. The route resolves US GAAP 10-K / 10-Q filers and IFRS foreign private issuers through ifrs-full 20-F / 6-K coverage. Preserve per-statement provenance, completeness, freshness, and materialization metadata when storing or comparing the bundle.

Financial statements API guide

Choose normalized statement data for a filing-aware financial workflow.

XBRL API guide

Review XBRL concepts and source provenance.

Canonical metadata

  • requestId
  • traceparent
  • provenance
  • freshness
  • materialization

Example request

Example response

About this example

This response is illustrative: EXAMPLE, all IDs, amounts, and example.com URLs are synthetic. It shows the response shape only and does not identify or claim a live SEC filing.

Give this prompt to your agent

Failure posture

  • provide one issuer identifier before requesting a bundle
  • do not assume each statement has the same reporting periods or every normalized line item
  • preserve each statement’s provenance, completeness, freshness, materialization, requestId, and traceparent when handling a partial or transient result