What is included in sec edgar api guide?

CIK and security identity, accession number, form and amendment status, filing and accepted timestamps, primary document and exhibits, filing period, source URL and retrieval run. Company submissions are collected incrementally and reconciled with SEC bulk archives. Coverage records distinguish an issuer with no matching filing from an ingestion failure.

Can I use this for historical backtesting?

Yes, where coverage and serving rights permit it. Save the query, source, known-at cutoff, schema version, and coverage result with the experiment.

Filings dataset

SEC EDGAR API guide

Q: Where does DataCedar get filings data?

SEC EDGAR. EDGAR is the open primary source. DataCedar preserves SEC attribution and follows the SEC fair-access policy and user-agent requirements.

Use the SEC’s open submissions and XBRL APIs through a normalized, accession-aware research layer.

Start with the API Read the API docs

Primary source

SEC EDGAR

API route

/v3/stocks/{symbol}/filings

Coverage

Explicit by stream

Serving

Rights-aware

What this dataset means

An SEC filing is a document submitted to EDGAR under a specific form type and accession number. Reliable research keeps the accession, accepted timestamp, filer CIK, document list, amendments, and original source URL so every extracted statement can be traced back to what the company filed.

The buyer’s objective is straightforward: Integrate public SEC data without maintaining every EDGAR parsing edge case. DataCedar keeps the research contract visible so the output can be inspected before it is trusted.

Fields delivered

CIK and security identity

accession number

form and amendment status

filing and accepted timestamps

primary document and exhibits

filing period

source URL and retrieval run

The endpoint is /v3/stocks/{symbol}/filings. Responses retain deterministic pagination and the metadata needed to connect normalized records to their source run.

How to evaluate a provider

The open SEC API is the benchmark. Pay for normalization, joins, history, and operational reliability—not for repackaged access alone.

A filing date is not always the first tradable time. Event research must use the accepted timestamp, market session, amendments, and the simulated decision cutoff. DataCedar deliberately exposes that boundary in the product rather than leaving customers to infer it from a missing endpoint or a legal footnote.

Failure modes to test before purchase

SEC fair-access violations.
CORS assumptions.
Recent submissions mistaken for full history.
Acquisition access is treated as proof of redistribution rights.
An empty array cannot distinguish no event from incomplete collection.

Source, freshness, and reproducibility

Source. SEC EDGAR. DataCedar stores source identifiers and retrieval runs before normalization, then serves its own stable downstream schema.

Freshness. The SEC updates submissions throughout the day and republishes bulk archives nightly. DataCedar records both the filing time and when its collector observed the filing.

Rights. EDGAR is the open primary source. DataCedar preserves SEC attribution and follows the SEC fair-access policy and user-agent requirements.

Questions, answered.

The research schema includes CIK and security identity, accession number, form and amendment status, filing and accepted timestamps, primary document and exhibits, filing period, source URL and retrieval run. Fields remain connected to source, retrieval, coverage, and rights metadata.