SEC EDGAR Submission API API

Submission of filings to EDGAR by API can be made through the Submission API. The Submission API requires the presentation of a Filer API Token in combination with a User API Token. Optionally, filers could also specify a login CIK if there is a delegation from the EDGAR account correspondingto the login CIK to the filer API token EDGAR account/CIK. Delegations can be established on the Filer Management dashboard under “Manage Delegations and User Groups.” For more informationon establishing delegations, see [How Do I “Understand and Manage Delegation.](https://www.sec.gov/submit-filings/filer-support-resources/how-do-i-guides/understand-manage-delegation)” Filings transmitted through the Submission API are expected to conform to the filing standard(s)[provided by the SEC](https://www.sec.gov/submit-filings). Information is provided on the required format and contents of filings by the [Technical Specifications](https://www.sec.gov/submit-filings/technical-specifications). Information and guidance on filing can be found in the [EDGAR Filing Manual](https://www.sec.gov/submit-filings/edgar-filer-manual). Information on specific forms can be found in the [SEC Forms Index](https://www.sec.gov/submit-filings/forms-index). The Submission API will return accession numbers for the submitted filings. A 202 HTTP statuscode indicates only that processing will begin in EDGAR and an accession number or accession numbers have been generated. Filings with errors will be processedand suspended by EDGAR. The results of processing (status and errors) are not provided by this endpoint and are instead available to clients using the API through theSubmission Status API. When using Submission API endpoints, the client can optionally specify the "Expect: 100-continue"HTTP request header to allow a response from these API resources to be returned before uploading the entire filing in the event that the EDGAR API determines thatthe request will not be allowed. This header should only be used for requests that have a body more than 1MiB in size. Filings may be transmitted via either SINGLE or BULK transmission. A SINGLE transmission providesa single filling and will result in a response containing an accession number if the filing is transmitted successfully or an error if there is an issue while transmitting the filing. Even if a filing is successfully transmitted through the submission API, the filing may still be suspended by EDGAR if the contents of the filing do not satisfy EDGAR filing requirements. The accession number may be provided to the Submission Status API in order to check whether the filing was accepted by EDGAR. A BULK filing, in contrast, is a single document that contains multiple filings to be submitted.If one or more filings are successfully transmitted then one or more accession numbers will be created and returned in the same order filings are included in the BULK filing document. However, if a filing is not successfully transmitted then an accession number may not be created, which means that the filer may have difficulty determining which accession number corresponds to which filing in the BULK filing document. Even if a filing is successfully transmitted through the Submission API, the filing may still be suspended by EDGAR if the contents of the filing do not satisfy EDGAR filing requirements. The relevant accession number may be provided to the Submission Status API in order to check whether the filing was accepted by EDGAR.