Build on United States filings programmatically.

The FinancialReports API delivers SEC-supervised US filings through the same single REST surface, one x-api-key header, and one shared rate-limit bucket used across all covered markets. A US-only integration is a one-parameter filter (?country=US) on the global filings endpoint — 10-K, 10-Q, 8-K, DEF 14A, Form 4, Form 13F, 20-F, and 6-K are all served through the same endpoint with a consistent JSON envelope that is structurally identical to the payload for a German BaFin ad-hoc or a French AMF filing. No separate API key, no US-specific infrastructure, and no US-only rate-limit bucket is needed.

The distinction between the FinancialReports API and the SEC's own EDGAR API (data.sec.gov) is worth stating precisely. EDGAR's API is US-only, form-driven, and requires consumers to navigate CIK identifiers, form-type codes, and filing-index structures; it exposes the raw EDGAR data model directly, without normalisation. FinancialReports provides a normalised, cross-border layer: the same API call that retrieves a US 10-K also retrieves a German annual report or a Brazilian DFP, with consistent field names, consistent filing-type taxonomy, and consistent body-format options — which is the critical advantage for any research or application that spans multiple markets simultaneously. For US-only, EDGAR-native workflows, the EDGAR API is free and comprehensive; for cross-border workflows that include the US alongside European or EM markets, the FinancialReports API eliminates the per-market integration cost.

For real-time pipelines the webhook subscription delivers full filing metadata within roughly 60 seconds of EDGAR acceptance — covering the full set of form types, not just periodic reports. Filing bodies are available as JSON metadata (issuer, form type, period, CIK, ISIN, exchange, filer category), Markdown via /api/filings/{id}/markdown/ (the same processed text rendered on the public web pages, ready for LLM and NLP ingestion without a separate EDGAR-to-text conversion step), and original PDF or Inline XBRL for audit and structured-data use cases. Inline XBRL is preserved from EDGAR for 10-K and 10-Q financial statements, retaining machine-readable line-items where the SEC mandates them.

Typical US API use cases include backfilling S&P 500 and Russell 1000 consolidated US GAAP financials for quant research, triggering on 8-K current reports for earnings releases and M&A announcements, monitoring Form 4 insider transactions across a target coverage universe, ingesting DEF 14A proxy text for governance-factor models, tracking 13F institutional-holdings changes for flow-of-funds analysis, and building cross-border analyst tools that span EDGAR-sourced US filings alongside European ESEF and EM markets in a single consistent data model. Trial keys are available on request; the web product is free and publicly indexed, so coverage is verifiable before integration.