SEC EDGAR Submission Status API
The Submission Status API provides information from the EDGAR system. It requires a Filer API Token and accession number(s). To obtain information about a submission through the Submission Status API, you must use a Filer API Token that belongs to the CIK that submitted the filing or the CIK that was the filer for the submission. The Submission Status API will only return the detailed information about the filling (like error codes or the filer notification text) once the filing has reached the end of processing signified by the field 'final' being set to true. The statuses of filings are retained for limited amounts of time. The statuses of Accepted TEST filings are retained for two (2) days, Accepted LIVE filings are retained for sixty (60) days, and Suspended filings, regardless of type, are retained for six (6) days.
SEC EDGAR Submission Status API is one of 12 APIs that SEC EDGAR publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Submission Status API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.
This API exposes 2 operations across 2 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.11.0.
Requests are made against a single base URL, https://api.edgarfiling.sec.gov.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
SEC EDGAR Submission Status API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (Filer_API_Token_and_User_API_Token).
It accepts HTTP bearer tokens (JWT) (Filer_API_Token).
Filer_API_Token_and_User_API_Token— A Filer API Token would be required to be presented to use any of the EDGAR APIs—the EDGAR Submission API, EDGAR Submission Status API, and EDGAR Operational S…Filer_API_Token— A Filer API Token would be required to be presented to use any of the EDGAR APIs—the EDGAR Submission API, EDGAR Submission Status API, and EDGAR Operational S…
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
The Submission Status API provides information from the EDGAR system.
Schemas 13
The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are SingleSubmissionStatusResponse (24 properties), SubmissionStatusResponseItem (22 properties), SEFMessage (8 properties), SubmissionStatusClassItem (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from SEC EDGAR 11
Other APIs SEC EDGAR publishes across the network.
This is an independent, third-party profile of SEC EDGAR Submission Status API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.