---
title: "Get alert"
method: GET
path: "/api/{cloudId}/v1/alerts/{id}"
tags: ["Alerts"]
---

# Get alert

`GET /api/{cloudId}/v1/alerts/{id}`

This endpoint provides users the ability to retrieve comprehensive details of a specific alert using its unique id.

## Path parameters

- `id` string, required

## Response `200`

Returned if the request is successful.

- AlertResponse
  - `id` string — Identifier of alert.
  - `tinyId` string — Unique, system-generated identification code assigned to each alert. This ID is shorter and simpler than the primary alert ID, making it easier to reference in communications and operations. It serves as a quick reference point to uniquely identify each alert.
  - `createdAt` string, date-time — Exact date and time when the alert was generated. It helps in tracking the timeline of the alerts and understanding the chronology of events.
  - `updatedAt` string, date-time — Exact date and time when the alert was updated.
  - `message` string — Brief summary of the alert that provides enough information to understand the nature of the issue at a glance.
  - `entity` string — Entity that the alert is related to. It could be a server, service, application or another source that's being monitored. The 'entity' helps in identifying and categorizing the origin of the alert, enabling quicker diagnostics and resolution of the issue.
  - `source` string — Origin of the alert, i.e., the system or application where the alert was generated. This field is useful for tracking and sorting alerts according to their originating sources, which can help in troubleshooting and determining the cause of the alerts.
  - `status` 'open' | 'acked' | 'resolved' | 'snoozed' | 'closed' — Current state of the alert represents whether the alert is new, has been acknowledged by a team member, has been resolved etc.
  - `alias` string — Client-defined identifier of the alert, that is also the key element of <a target="_self" href="https://support.atlassian.com/atlassian/docs/what-is-alert-de-duplication/">Alert De-Duplication</a>.
  - `tags` string[] — Additional categorizing information. These tags can then be used for searching or grouping alerts, making it easier to manage and prioritize them.
  - `extraProperties` ExtraProperties — Map of key-value pairs to use as custom properties of the alert. This can include context-specific data, diagnostic information, or other metadata that can assist in understanding and resolving the alert.
  - `description` string — Detailed information contains more comprehensive information than the 'message' field, including the implications of the alert, steps to reproduce the issue, or suggestions for resolving the problem. It serves as a guide for the person or team responding to the alert to better understand the situation and take appropriate actions.
  - `acknowledged` boolean — Indicating whether the alert has been acknowledged by a team member or not. If the alert has been acknowledged, it means that someone is actively looking into the issue.
  - `ackTime` string, date-time — Exact date and time when the alert was acknowledged.
  - `closeTime` string, date-time — Exact date and time when the alert was closed.
  - `count` integer — Represents the number of times the alert has been triggered. Each time the same alert is triggered, instead of creating a new alert, the count of the existing alert increases. This helps in reducing noise and focusing on the recurring issue.
  - `owner` string — Display name of the alert owner.
  - `snoozed` boolean — Reflects whether the alert has been temporarily silenced or not. If set to 'true', it means the alert notifications have been paused for a specified duration and will not disturb the users during this period.
  - `snoozedUntil` string, date-time — Represents the time until which the alert is snoozed.
  - `lastOccuredAt` string, date-time — Represents the most recent time the alert was triggered.
  - `integrationType` string — Denotes the type of integration used to create the alert.
  - `integrationName` string — Denotes the name of integration used to create the alert.
  - `priority` 'P1' | 'P2' | 'P3' | 'P4' | 'P5' — Urgency level of the alert. The priority can be set as 'P1', 'P2', 'P3', 'P4', or 'P5', with 'P1' being the highest and 'P5' the lowest. The 'priority' attribute aids in effective alert management by allowing alerts to be categorized and handled according to their importance.
  - `responders` Responder[] — Teams, users, escalations and schedules that the alert will be routed to send notifications.
    - `id` string — Identifier of the responder.
    - `type` 'team' | 'user' | 'escalation' | 'schedule' — Type of the responder.
  - `actions` string[] — A list of actions that can be executed on the alert. These actions are custom to your organization and can be used to automate responses to specific alerts.
  - `seen` boolean — Represents whether the alert has been viewed by a user or not.

## Other responses

- `401` — Returned if the authentication credentials are incorrect.
- `403` — Returned if the alert is not visirequest user does not have read-only permission for alerts.
- `404` — Returned if the alert is not found.

---

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