Choose the archive that matches your dataset
The SEC documents nightly rebuilds at approximately 03:00 Eastern Time. Record when you downloaded the archive; the filename alone does not tell you which snapshot your analysis used. The archives are data snapshots, not a promise to include every filing document as HTML.
| submissions.zip | Public filing-history JSON for filers | A company and filing-metadata baseline. |
| companyfacts.zip | Aggregated company XBRL JSON | A baseline of standard financial observations. |
No matching records. Try a broader search.
Build a resumable ingestion process
Download once, verify that you received a valid ZIP and inspect entries before extraction. Record the archive size, a cryptographic hash, retrieval time and your parser version. Extract into a staging location, validate a representative set and only then swap the active dataset.
Do not load a partially extracted archive into production. Store failures separately, keep the previous valid snapshot and make the refresh atomic from the reader’s point of view. These are recommended operating checks; this publication did not download or ingest the full bulk archives.
Plan the incremental boundary
A nightly baseline does not automatically cover the interval after it was built. For a small watchlist, refresh the relevant submissions JSON at a conservative cadence. For a large filing-monitoring workflow, consider an event feed plus a reconciliation job against official records.
Persist a high-water mark with overlap, then deduplicate using filing identifiers. Keep the original event receipt time and the official filing time separately. Before claiming complete coverage, compare the resulting filing set with the appropriate official index for the same interval.
Distinguish bulk metadata from raw filings
If your task requires the original reports and attachments, use the archive/index access described in SEC Developer Resources. A companyfacts snapshot does not replace original footnotes, exhibits or all custom XBRL data.
Use the access comparison to decide whether document extraction, event transport or a full-text index is the actual missing piece. That decision prevents paying for a service whose output does not match your dataset.
Source notes
- SEC EDGAR API documentation ↗
Official submissions, XBRL, bulk data, update schedule and access requirements.
- SEC Developer Resources ↗
Official archive, index and RSS options; fair-access request limit.
The Synoptic workflow
Explore the SEC event stream
For new-filing monitoring, verify the stream and your account access.
Explore the SEC event stream