Free, no card required

US Compliance Data API

SEC filings and economic data, the way a compliance team can actually use them

What it does

Pulls SEC EDGAR filings and Federal Reserve FRED economic data through a single API, with every response carrying the filing date, retrieval timestamp, and EDGAR accession number, so the data can be cited precisely rather than reconstructed from a manual download later.

Which plan you need

Free. No card required. Included from the free tier through every paid tier above it, this isn't an add on.

Use cases

Data sources

SEC EDGAR, company filings including 10-K, 10-Q, 8-K, DEF 14A, S-1, and company facts extracted from XBRL tags
Federal Reserve FRED, macroeconomic series including interest rates, CPI, GDP, unemployment, and yield curves

What you get back

Structured filing data by ticker or CIK, financial statement figures pulled from XBRL rather than parsed from raw filings by hand, FRED series by series ID, and a full lineage record on every response, source, filing date, retrieval timestamp, EDGAR accession number. Schema changes are versioned, not silent.

Further reading

Frequently asked questions

How do I get SEC EDGAR filing data via API without building a scraper?
The API retrieves filings directly by ticker or CIK and returns structured data, not raw HTML, so there's no scraper to build or maintain.
What SEC filing types are available through an API?
10-K, 10-Q, 8-K, DEF 14A, S-1, and other standard filing types, retrieved as structured records rather than raw documents.
How do I track when a public company files a new disclosure?
Filings are retrievable by ticker or CIK with filing date included in every response, so a new filing can be checked against the last known date.
Can I get FRED macroeconomic data and SEC filings in one API call?
They're separate endpoints on the same API and same authentication, not a single combined call, but both are available without a second integration.
How do I prove to my compliance team what data was used in a financial analysis?
Every response includes the source, filing date, retrieval timestamp, and EDGAR accession number, which together form the record of exactly what was used and when.
What are SEC EDGAR's rate limits and how do they affect production use?
Raw EDGAR access carries request limits that can interrupt a production workflow without warning. The API absorbs that constraint so an integration doesn't hit it directly.
How do I build an automated due diligence workflow using public SEC filings?
Filing retrieval, financial statement extraction, and audit logging are all part of the same API, so a due diligence workflow can be built without separately sourcing and reconciling each piece.
What is data lineage and why does it matter for compliance teams using SEC data?
Lineage is the record of exactly where a data point came from and when it was retrieved. For a compliance team, it's what turns a data point into something that can be defended later, not just something that was true in the moment.
How do fintechs use EDGAR data in AML and KYC workflows?
Public filings help confirm a counterparty's regulatory status and disclosure history as part of a broader entity verification process, alongside other checks rather than in place of them.
When does the free EDGAR API stop being enough for production use?
Once a compliance workflow needs an audit trail, a stable schema, and a vendor accountable for uptime, none of which the raw EDGAR API provides on its own.
Get started free View API docs