/alerts/silences/{silence_id} - Get a single silence

GET /alerts/silences/{silence_id}
Bearer auth

Cross-system parallel of GET /systems/{id}/alerts/silences/{silence_id}. Looks up a silence inside a single tenant (?organization_id=) and returns it enriched with organization_id and system_key. Silences without a system_key matcher are reported as 404 — they don't belong to our domain.

Requires read:systems permission.

Path parameters

  • silence_id string Required

    Alertmanager silence ID.

Query parameters

  • organization_id string Required

    Tenant that owns the silence. Mandatory for every role except Customer (where it is ignored).

Responses

  • 200 application/json

    Silence retrieved successfully

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object
      Hide data attribute Show data attribute object
      • silence object
        Hide silence attributes Show silence attributes object
        • id string

          Alertmanager silence ID

        • matchers array[object]
          Hide matchers attributes Show matchers attributes object
          • name string

            Label name

          • value string

            Label value

          • isRegex boolean

            Whether the value is a regex

        • startsAt string(date-time)
        • endsAt string(date-time)
        • updatedAt string(date-time)
        • createdBy string
        • comment string
        • status object
          Hide status attribute Show status attribute object
          • state string

            Runtime state of the silence

            Values are active, expired, or pending.

        • organization_id string
        • system_key string
  • 401 application/json

    Unauthorized - invalid or missing token

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object | null
  • 403 application/json

    Forbidden - insufficient permissions

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object | null
  • 404 application/json

    Resource not found

    Hide response attributes Show response attributes object
    • code integer

      HTTP error code

    • message string

      Error message

    • data object
      Hide data attributes Show data attributes object
      • type string

        Type of error

        Values are validation_error or external_api_error.

      • errors array[object]
        Hide errors attributes Show errors attributes object
        • key string

          Field name that failed validation

        • message string

          Error code or message

        • value string

          Value that failed validation

      • details

        Additional error details
GET /alerts/silences/{silence_id} 
curl \
 --request GET 'https://api.your-domain.com/api/alerts/silences/d9f91c6e-1b33-484e-befa-bfb41020e178?organization_id=m4m3mdjdiizs' \
 --header "Authorization: Bearer $ACCESS_TOKEN"
Response examples (200)
Same `AlertmanagerSilence` shape as the per-system endpoint, plus `organization_id` (the tenant that owns the silence) and `system_key` (extracted from the matchers). 
{
  "code": 200,
  "message": "silence retrieved successfully",
  "data": {
    "silence": {
      "id": "d9f91c6e-1b33-484e-befa-bfb41020e178",
      "organization_id": "m4m3mdjdiizs",
      "system_key": "NETH-D417-A2C2-7810-43D2-984B-2164-34C1-B22E",
      "matchers": [
        {
          "name": "system_key",
          "value": "NETH-D417-A2C2-7810-43D2-984B-2164-34C1-B22E",
          "isRegex": false
        },
        {
          "name": "alertname",
          "value": "HighCPUUsage",
          "isRegex": false
        },
        {
          "name": "severity",
          "value": "warning",
          "isRegex": false
        }
      ],
      "startsAt": "2026-05-12T08:16:36Z",
      "endsAt": "2026-05-12T09:16:36Z",
      "updatedAt": "2026-05-12T08:16:36Z",
      "createdBy": "amelia.foster",
      "comment": "silenced during maintenance window",
      "status": {
        "state": "active"
      }
    }
  }
}
Response examples (401) 
{
  "code": 401,
  "message": "invalid token",
  "data": {}
}
Response examples (403) 
{
  "code": 403,
  "message": "insufficient permissions",
  "data": {}
}
Response examples (404) 
{
  "code": 400,
  "message": "validation failed",
  "data": {
    "type": "validation_error",
    "errors": [
      {
        "key": "username",
        "message": "required",
        "value": "string"
      }
    ]
  }
}