---
title: "Get details of specific alarm"
method: GET
path: "/v1/alarms/{alarm-id}"
tags: ["Alarms"]
---

# Get details of specific alarm

`GET /v1/alarms/{alarm-id}`

## Path parameters

- `alarm-id` integer, required

## Response `200`

Details of given alarm

- Alarm — Full alarm representation
  - `id` integer — Alarm ID
  - `parentId` integer — Parent alarm ID (0 if none)
  - `rcaScriptName` string — Root cause analysis script name
  - `ackByUser` integer — ID of the user who acknowledged the alarm
  - `resolvedByUser` integer — ID of the user who resolved the alarm
  - `terminatedByUser` integer — ID of the user who terminated the alarm
  - `ruleGUID` string, uuid — GUID of the event processing policy rule that generated the alarm
  - `ruleDescription` string — Description of the originating rule
  - `eventCode` integer — Source event code
  - `eventName` string — Source event name (present only when the event code resolves to a name)
  - `eventId` integer — Source event ID
  - `eventTags` string — Source event tags
  - `source` integer — Source object ID
  - `dci` integer — Related DCI ID (0 if none)
  - `creationTime` string, date-time — Alarm creation timestamp
  - `lastChangeTime` string, date-time — Last change timestamp
  - `key` string — Alarm key
  - `message` string — Alarm message
  - `impact` string — Business impact
  - `state` integer — Alarm state: 0=Outstanding, 1=Acknowledged, 2=Resolved, 3=Terminated
  - `isSticky` boolean — Whether the alarm is sticky
  - `severity` integer — Current severity: 0=Normal, 1=Warning, 2=Minor, 3=Major, 4=Critical
  - `originalSeverity` integer — Original severity at creation time
  - `helpDeskState` integer — Helpdesk integration state
  - `repeatCount` integer — Number of times the alarm was repeated
  - `subordinateAlarms` integer[] — IDs of subordinate alarms
  - `categories` AlarmCategoryReference[] — Alarm categories (as assigned by the event processing policy rule that raised the alarm)
    - `id` integer — Alarm category ID
    - `name` string, nullable — Alarm category name, or null if the category no longer exists

## Other responses

- `401` — Unauthorized
- `403` — User does not have read access to alarm or alarm's source object
- `404` — Alarm with given ID does not exist

## Changes

- **2026-06-24** `47b14ef7aa72` — 1 breaking, 2 info
  - the `categories/items/` response's property type changed from `integer` to `object` for status `200`
  - added the optional property `categories/items/id` to the response with the `200` status
  - added the optional property `categories/items/name` to the response with the `200` status
- **2026-06-10** `30e75dc6a94c` — 1 info
  - added the media type `application/json` for the response with the status `200`
- **2026-05-08** `c6aaf3632e48` — 1 breaking
  - removed the media type `application/json` for the response with the status `200`

[Change history](https://skmtc.dev/netxms/apis/netxms-api/changes/v1/alarms/:alarm-id/get.md)

---

[API](https://skmtc.dev/netxms/apis/netxms-api.md) · [All operations](https://skmtc.dev/netxms/apis/netxms-api/llms.txt) · [OpenAPI document](https://skmtc.dev/netxms/apis/netxms-api/revisions/a81265c49fa9?raw)