Audience: application and coding agent.
Coverage and source scope
Use this route when the statement type belongs in the URL rather than a query string. Setstatement_key to a supported normalized statement, then select annual or quarterly cadence and fiscal years as needed. The result preserves reported units, periods, and filing provenance and may contain missing or incomparable normalized line items. See API conventions and freshness and source evidence.
Required inputs
statement_key selects the normalized statement type; supply one issuer identifier and use period, fy / year, or a fiscal-year range when the workflow needs a particular reporting slice. Inspect the returned periods and provenance rather than inferring a fiscal period from the request alone.
Related guides
Financial statements API guide
Understand normalized statement coverage and filing context.
Freshness and trust
Carry source and freshness metadata into downstream reports.
Canonical metadata
requestIdtraceparentprovenancefreshnessmaterialization
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 a supported
statement_keyand one issuer identifier - use the returned periods and provenance rather than inferring the reporting slice from a requested fiscal year alone
- preserve completeness, freshness, materialization,
requestId, andtraceparentwhen handling a partial or transient result

