---
title: "Get a Incident by ID"
method: GET
path: "/rest/operations/1.0/incidents/{incidentId}"
tags: ["Operations"]
---

# Get a Incident by ID

`GET /rest/operations/1.0/incidents/{incidentId}`

Retrieve the currently stored Incident data for the given ID.

The result will be what is currently stored, ignoring any pending updates or deletes.

Only Connect apps that define the `jiraOperationsInfoProvider` module can access this resource.
This resource requires the 'READ' scope for Connect apps.

## Path parameters

- `incidentId` string, required

## Response `200`

The Incident data currently stored for the given ID.

- object — Data related to a specific incident in a specific container that the incident is present in. Must specify at least one association to a component.
  - `schemaVersion` '1.0', required — The IncidentData schema version used for this incident data. Placeholder to support potential schema changes in the future.
  - `id` string, required — The identifier for the Incident. Must be unique for a given Provider.
  - `updateSequenceNumber` integer, required — An ID used to apply an ordering to updates for this Incident in the case of out-of-order receipt of update requests. This can be any monotonically increasing number. A suggested implementation is to use epoch millis from the Provider system, but other alternatives are valid (e.g. a Provider could store a counter against each Incident and increment that on each update to Jira). Updates for a Incident that are received with an updateSqeuenceId lower than what is currently stored will be ignored.
  - `affectedComponents` string[], required — The IDs of the Components impacted by this Incident. Must be unique for a given Provider.
  - `summary` string, required — The human-readable summary for the Incident. Will be shown in the UI. If not provided, will use the ID for display.
  - `description` string, required — A description of the issue in Markdown format. Will be shown in the UI and used when creating Jira Issues.
  - `url` string, uri, required — A URL users can use to link to a summary view of this incident, if appropriate. This could be any location that makes sense in the Provider system (e.g. if the summary information comes from a specific project, it might make sense to link the user to the incident in that project).
  - `createdDate` string, date-time, required — The timestamp to present to the user that shows when the Incident was raised. Expected format is an RFC3339 formatted string.
  - `lastUpdated` string, date-time, required — The last-updated timestamp to present to the user the last time the Incident was updated. Expected format is an RFC3339 formatted string.
  - `severity` object — Severity information for a single Incident. This is the severity information that will be presented to the user on e.g. the Jira Incidents screen.
    - `level` 'P1' | 'P2' | 'P3' | 'P4' | 'P5' | 'unknown', required — The severity level of the Incident with P1 being the highest and P5 being the lowest
  - `status` 'open' | 'resolved' | 'unknown', required — The current status of the Incident.
  - `associations` object[] — The IDs of the Jira issues related to this Incident. Must be unique for a given Provider.
    - `associationType` 'issueIdOrKeys' | 'serviceIdOrKeys' | 'ati:cloud:compass:event-source' — the type of the association being made
    - `values` string[]

## Other responses

- `401` — Missing a JWT token, or token is invalid.
- `403` — The JWT token used does not correspond to an app that defines the Operations Information module, or the app does not define the 'READ' scope.
- `404` — No data found for the given Incident ID.
- `429` — API rate limit has been exceeded.
- `503` — Service is unavailable due to maintenance or other reasons.
- `default` — An unknown error has occurred.

---

[API](https://skmtc.net/atlassian/apis/jira-software-cloud-api.md) · [All operations](https://skmtc.net/atlassian/apis/jira-software-cloud-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/jira-software-cloud-api/versions/4e108d54b990/schema)