---
title: "Single Live Submission"
method: POST
path: "/submission/single/live"
tags: ["Submission API"]
---

# Single Live Submission

`POST /submission/single/live`

Allows an authorized filer to transmit a SINGLE LIVE submission file. When an authorized filer transmits a filing to this resource it will transmit the file to EDGAR and return an accession number. EDGAR will then begin processing the submission.

## Headers

- `X-EDGAR-CIK` string
- `X-EDGAR-LOGIN-CIK` string

## Response `202`

Accepted. The filing has been transmitted to the SINGLE LIVE resource and the EDGAR system has generated an accession number. The submission has begun processing.

- SingleSubmissionResponse — A submission response is a response to transmitting a submission.
  - `tracking` string — A universal tracking identifier that can be used by applications to keep track of individual requests sent to the EDGAR API. The tracking identifier correlates all actions taken in the course of a single request. If seeking support from the EDGAR Help Desk this will be a useful piece of information to provide.
  - `locator` string — A short identifier that can be used by the EDGAR Help Desk to locate the tracking identifier within the EDGAR system.
  - `accessionNumber` string, nullable — The unique number associated with an transmitted submission.
  - `messages` Message[] — A list of messages providing details associated with the submission response. This could range from a notification about the filing to errors related to the state of the filing. This should include things like submission error codes as well as other EDGAR output.
    - `type` 'INFO' | 'NOTICE' | 'WARNING' | 'ERROR' — The type of the message being returned regarding how severe it is or what type of message it contains.
    - `content` string — The content of the message intended to be interpreted by a human consumer of the API output.
  - `mode` 'LIVE' | 'TEST' — The submission mode of a filing: * `TEST` - A submission mode that allows a filing to be tested for correctness * `LIVE` - A submission mode that allows a filing to be evaluated as an official filing For more information see the EDGAR Filing Manual
  - `status` 'RECEIVED' | 'REJECTED' | 'FAILED' — A short string that indicates the status of filing that was transmitted to EDGAR. * `RECEIVED` - The transmission has been received by EDGAR and an accession number has been generated * `REJECTED` - The transmission was rejected by EDGAR and will not be processed * `FAILED` - The transmission failed to be transmitted to EDGAR and will not be processed`
  - `transmissionStatus` 'RECEIVED' | 'REJECTED' | 'FAILED' — A short string that indicates the status of filing that was transmitted to EDGAR. * `RECEIVED` - The transmission has been received by EDGAR and an accession number has been generated * `REJECTED` - The transmission was rejected by EDGAR and will not be processed * `FAILED` - The transmission failed to be transmitted to EDGAR and will not be processed`

## Other responses

- `400` — Bad request
- `401` — Unauthorized. This resource is being accessed with invalid or inactive tokens. Please check that the tokens in use are active in Filer Management or are assigned to active individuals.
- `403` — Forbidden. A valid Filer API Token and User Access Token must be provided with this request. Please ensure that the User identified by the User Access Token is authorized to file (1) for the CIK associated with the Filer API Token and (2) for any CIKs for which filings are being submitted.
- `500` — Server error. An unexpected server-side error has occurred.
- `503` — A request was made to this resource outside of operational hours.

---

[API](https://skmtc.net/sec/apis/edgar-api.md) · [All operations](https://skmtc.net/sec/apis/edgar-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sec/edgar-api/revisions/8bbcd8648315/schema)