Free SEC Filings API: Official & Free-Tier Guide

Choose the right free SEC filings API path

A free SEC filings API search usually begins with price, but the decision is really about the answer shape and engineering responsibility. Official SEC sources provide authoritative submission metadata, filing documents, XBRL facts, and downloadable datasets. A third-party free tier may add ticker lookup, full-text or section search, normalized form-specific records, webhooks, bulk exports, or SDKs while imposing account, quota, retention, and licensing rules.

Define the job before choosing the endpoint. “Latest filings for a company” needs a submissions index; “revenue by quarter” needs XBRL facts plus taxonomy and period logic; “risk-factor text” needs document retrieval and section extraction; “insider purchase” or “institutional holding” needs ownership-form parsing; “new material event” needs form and item classification. One generic filings endpoint rarely solves all five correctly.

What the official free SEC EDGAR API provides

The SEC EDGAR API documentation describes public JSON endpoints on data.sec.gov for submissions history and extracted XBRL data. These endpoints do not require an API key, but automated clients must identify themselves and follow current SEC access and security policies. Filing archives and primary documents live under SEC archive paths and should be linked by CIK, accession, and document name rather than treated as anonymous HTML pages.

Submissions JSON is a filing index, not the filing body

The company submissions response contains recent form types, filing and report dates, accession numbers, primary documents, and references to older submissions files. A complete backfill must follow those older-file references, handle amendments as separate filings, and preserve the sequence in which filings became public. The index tells you what exists; it does not contain every document, exhibit, inline XBRL fact, or narrative section.

XBRL endpoints answer fact-level questions

Companyfacts, companyconcept, and frames expose machine-readable facts. They help with standardized metrics, but each fact still has taxonomy, unit, period, form, filed date, accession, and sometimes segment or dimensional context. Selecting “the latest value” without duration-versus-instant logic or amendment handling can mix incompatible facts. XBRL also does not replace narrative sections, exhibits, signatures, or ownership-form fields.

Model a source-linked SEC filing request

1. Resolve ticker to CIK

CIK is the stable SEC entity identifier. Normalize it to the format required by the endpoint and store it alongside the ticker instead of treating ticker symbols as permanent identifiers.

2. Filter by form and date

Separate filing date from report period, include amendments deliberately, and decide whether the application needs metadata, the primary HTML document, exhibits, or XBRL facts.

3. Preserve accession number and source URL

Store the raw response next to normalized fields. The accession number, form, filing date, CIK, retrieval time, and official SEC URL form the minimum useful provenance record.

4. Treat documents, exhibits, facts, and extracted sections as separate layers

Store the filing index, raw primary document, exhibit inventory, structured facts, and derived section text independently. Each derived artifact should point to source accession, document, parser version, and extraction range. This prevents a parser update from silently changing the authoritative filing record.

5. Build point-in-time versions, not one mutable “latest” row

Keep original filings and amendments in filing-time order, then derive a current view and an as-known-at-time view. Research backtests should see only filings public by the analysis timestamp; production applications can separately expose the latest corrected state.

SEC filing clocks, processing states, and amendment history

A filing record needs more than one date. The report period describes the business period covered; the filing date is a calendar-level filing field; the SEC acceptance timestamp records when the submission entered EDGAR; retrieval time records when your system obtained it. A parsed fact can become available later than the raw document. Keep these clocks separate so an alert, backtest, and current dashboard can each use the correct one.

Compare free SEC filing data API limits

Build a resilient SEC filings API Python client

Create one request layer that sets a descriptive User-Agent, timeout, and accepted response type. Add conservative pacing, conditional or immutable caching where appropriate, honor Retry-After, and retry temporary failures with jittered exponential backoff. Treat 403, 404, 429, and 5xx responses as different operational states rather than returning an empty dataset.

• Resolve and store CIK as a string, with effective-dated ticker mappings rather than a permanent ticker assumption.
• Ingest recent submissions and referenced older files, then reconcile accessions, forms, filing dates, report dates, and primary documents.
• Fetch and hash raw filing artifacts before parsing; keep parser and taxonomy versions with every derived record.
• Use bounded queues and global pacing across workers so parallel backfills still respect current access policy.
• Reconcile daily additions and amendments, and alert on unexplained accession disappearance, document changes, or parser row loss.
• Publish source URL, accession, form, filed date, report period, retrieval time, and derivation status with downstream answers.

FAQ