---
title: "EDGAR System Status"
method: GET
path: "/status"
tags: ["EDGAR Operational Status API"]
---

# EDGAR System Status

`GET /status`

Uses EDGAR operating hours logic and communicates with other EDGAR components to determine the ability of the system to receive API calls and submissions.

## Response `200`

Ok. The EDGAR system was able to provide a status response.

- Response — Provides information on the current operating state of EDGAR
  - `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.
  - `condition` 'ACCEPTING' | 'ACCEPTING_WITH_TECHNICAL_DIFFICULTIES' | 'ACCEPTING_AFTER_HOURS' | 'ACCEPTING_AFTER_HOURS_WITH_TECHNICAL_DIFFICULTIES' | 'OUTSIDE_OPERATING_HOURS' | 'NO_COMMUNICATION' — The current operating state of EDGAR
  - `message` string — Optionally provides additional information if any is required

## Other responses

- `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. This resource requires a valid Filer API Token. Please ensure that the token that is being used is a Filer API Token and is active in Filer Management.
- `500` — Server error. An unexpected server-side error has occurred.

---

[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)