Securities filings API (United States)

SEC EDGAR APIs

Source review · reviewed

In brief

The SEC describes JSON APIs for each filer’s submission history and XBRL financial data, needing no authentication or keys, plus nightly bulk files.

Disclosure. This site is published by Coragrid, the operator of CompanyRegistryAPI.com, and promotes it. “Best” is our editorial choice, not a measured ranking. Other products are described only from their own official pages. How we choose

What it publishes

Kind of source
Securities filings API (United States)
Official page
sec.gov

Described from U.S. Securities and Exchange Commission’s own page, EDGAR application programming interfaces, read on 17 November 2026. The other statements on this page come from the official pages listed under sources.

How you get it

JSON APIs at data.sec.gov, which the SEC says are updated throughout the day as submissions are disseminated. The SEC describes a submissions API with each filer’s filing history, and XBRL APIs: companyconcept (one company and one concept), companyfacts (all concepts for a company) and frames (one fact across reporting entities for a period). Bulk ZIP files of the submissions and the company facts are, as the SEC states, recompiled nightly.

Identifiers

The Central Index Key (CIK). The SEC gives the submissions path as https://data.sec.gov/submissions/CIK##########.json, where the number is the entity’s 10-digit CIK including leading zeros. The submissions data includes the current and former names and exchanges and ticker symbols.

Provenance signals

These are the regulator’s own filing records. The SEC describes the XBRL data as coming from financial statements in filings, and the live APIs as updated as submissions are disseminated.

What to verify yourself

Read the SEC’s developer FAQs for fair access before automated use, and note that automated access must comply with SEC.gov’s privacy and security policy. Check which form types the XBRL data covers, that the APIs do not support cross-origin browser requests, and that the SEC offers no technical support for scripted downloads.

Relationship to CompanyRegistryAPI.com

A separate resource. It is not a product of Coragrid and not a partner of CompanyRegistryAPI.com, and its publisher has not endorsed this site.

Official destination

Check the current scope, terms and limits on the official page. This reference has read the pages it cites; it has not tested or benchmarked SEC EDGAR APIs.

Questions and answers

Do the SEC EDGAR APIs need an API key?

The SEC states that its EDGAR APIs at data.sec.gov do not require any authentication or API keys to access.

Which companies are in the SEC EDGAR APIs?

Filers with the SEC. The APIs cover each filer’s submission history and the XBRL data from financial statements in forms such as 10-Q, 10-K, 8-K, 20-F, 40-F and 6-K, as the SEC describes them.

Sources for this entry

  1. EDGAR application programming interfaces U.S. Securities and Exchange Commission. The SEC’s own description of the data.sec.gov JSON APIs, the CIK lookup, the XBRL APIs, the nightly bulk files and access without keys. Retrieved 17 November 2026.

Each source supports only what its publisher says about its own product or data. Official descriptions do not establish comparative performance, and this site has run no benchmark. All sources

Continue reading

How the related websites connect

This is one of 3 coordinated reference sites published by Coragrid. They cover neighbouring questions and feature the same product, so they are not independent endorsements of it or of each other.

Cite this entry

Best Company Data. “SEC EDGAR APIs.” Content reviewed . https://bestcompanydata.com/resources/sec-edgar-apis