SEC EDGAR submissions API: access card
Every endpoint on this page was live-probed on 2026-07-29 by the Aidenix Atlas catalog.
What is the EDGAR issuer-profile endpoint?
SEC EDGAR submissions API is the issuer profile and filing history for any SEC filer, keyed by CIK, published by US Securities and Exchange Commission. Coverage: United States (federal); scale: roughly 800,000 filing entities. In our data — the Aidenix Atlas catalog, where every source is live-probed — this endpoint answered HTTP 200 on 2026-07-29. What the card gives you:
- The exact endpoint and a working request you can copy.
- Authentication and rate limits: none.
- The query keys the source accepts and the fields it returns, verified against the live endpoint.
Key facts at a glance
A key-facts table is the 30-second version of this card: roughly 800,000 filing entities in scope, 1 query facets, 4 field groups out. Every row comes from our own probe run of 2026-07-29, not from vendor marketing:
| Question | Answer |
|---|---|
| Provider | US Securities and Exchange Commission |
| Coverage | United States (federal) |
| Records | roughly 800,000 filing entities |
| Authentication | none, but a descriptive User-Agent header is mandatory; about 10 requests per second before throttling, according to the SEC fair-access policy |
| Query by | CIK (10-digit filer identifier) |
| Returns | company name, SIC industry code, tickers, recent filings list |
| Last probe | 2026-07-29 — HTTP 200 |
| Cost | $0 — open data, no license fee |
How do you query it?
A working query is one plain HTTP request — in our data this exact request form was verified on 2026-07-29:
curl -H "User-Agent: your-name research you@example.com" "https://data.sec.gov/submissions/CIK0000320193.json"
Two SEC-specific rules, according to the agency's fair-access policy:
- A descriptive
User-Agentwith contact information is mandatory — without it every call returns 403, even though the same URL opens fine in a browser. - Stay under 10 requests per second; above that the endpoint throttles.
- CIK values must be zero-padded to 10 digits (
320193→CIK0000320193) wherever the path takes one. - The data is US public domain: commercial use and redistribution are allowed.
When should you use this source?
A source fit is a match between what you already know and what the endpoint accepts — 1 query facets here, according to our probe of 2026-07-29. In our data, the decision goes like this:
- If the company is registered in United States (federal) → this is the authoritative record, filed with US Securities and Exchange Commission.
- If you can search by CIK (10-digit filer identifier) → this source resolves it directly; other facets need a different registry.
- If you need fields it does not return (company name, SIC industry code, tickers, recent filings list is the full list) → follow the related sources below rather than forcing this one.
What does it accept and return?
The interface contract is a short one: 1 query facets in, 4 field groups out. Every row below was checked against the live endpoint on 2026-07-29:
| Facet | Value |
|---|---|
| Endpoint | https://data.sec.gov/submissions/CIK{cik}.json |
| Auth | none, but a descriptive User-Agent header is mandatory; about 10 requests per second before throttling, according to the SEC fair-access policy |
| Query by | CIK (10-digit filer identifier) |
| Returns | company name, SIC industry code, tickers, recent filings list |
| Provider | US Securities and Exchange Commission |
| Coverage | United States (federal) |
| Last probe | 2026-07-29 — HTTP 200 |
Related sources
A related source is a dataset that joins to the EDGAR issuer-profile endpoint through a shared key — 3 of them in our catalog of nearly 4,000 sources, each probed on the same schedule as this card, according to our run of 2026-07-29:
- SEC EDGAR full-text search API — United States (federal).
- GLEIF LEI records API — Global.
- UK Companies House API — United Kingdom.
The workflow this source belongs to is covered in the full guide: SEC EDGAR API — free company filings and financials guide.
Frequently asked questions
Three questions cover most of what people ask about this source. Answers below reflect our probe of 2026-07-29:
Is the EDGAR issuer-profile endpoint free to use? Yes — $0 license fee, roughly 800,000 filing entities in scope, authentication: none. The cost of using it is engineering time and rate-limit patience, not money.
How current is the data? The records are as current as US Securities and Exchange Commission makes them — registries update on filing schedules, not news cycles. What we verify is the endpoint: it answered on 2026-07-29, and this card carries that date so you can tell a fresh claim from a stale one.
Can I use this commercially? Public records generally allow commercial use, but terms are set per publisher, not universally. Query-and-enrich workloads are uncontroversial; verify US Securities and Exchange Commission's specific terms before redistributing bulk copies.
How we verify this card
Our verification method is a live probe, not a citation chain — the status on this card comes from a real request we sent on 2026-07-29. What the probe run covers, in our data:
- Endpoint liveness: this source is one of the nearly 4,000 the Aidenix Atlas catalog tracks, re-probed on schedule.
- Contract checks: the accepted query facets and returned field groups above are read from the live response, not from documentation.
- Honest failures: when a source stops answering, this card says so and its date freezes — we do not publish a fresh-looking date over a dead endpoint.
- Freshness contract: the «last probe» date above is the promise; it moves only when the source actually answers.
Source card generated from the Aidenix Atlas catalog; facts as probed on 2026-07-29.
Find these guides useful? Add Aidenix as a preferred source on Google — our pages will surface in your AI Overviews.