/systems/{id}/alerts/silences - List active silences for a system

GET /systems/{id}/alerts/silences
Bearer auth

Returns all active and pending Alertmanager silences scoped to the target system. Expired silences are excluded. Results are filtered server-side to silences that carry an exact system_key matcher matching the system's key. Requires read:systems permission.

Path parameters

  • id string Required

    System ID (database UUID)

Responses

  • 200 application/json

    Silences retrieved successfully

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object
      Hide data attribute Show data attribute object
      • silences array[object]
        Hide silences attributes Show silences 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.
  • 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 /systems/{id}/alerts/silences 
curl \
 --request GET 'https://api.your-domain.com/api/systems/sys_123456789/alerts/silences' \
 --header "Authorization: Bearer $ACCESS_TOKEN"
Response examples (200)
The silence matches on `system_key` (server-injected) plus the labels that uniquely identified the alert at silence creation time. `silencedBy` on the active alert references this same `id`. 
{
  "code": 200,
  "message": "silences retrieved successfully",
  "data": {
    "silences": [
      {
        "id": "d9f91c6e-1b33-484e-befa-bfb41020e178",
        "matchers": [
          {
            "name": "system_key",
            "value": "NETH-D417-A2C2-7810-43D2-984B-2164-34C1-B22E",
            "isRegex": false
          },
          {
            "name": "alertname",
            "value": "DiskFilling",
            "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": "R1C1 Admin <c5gpnoo2do48>",
        "comment": "silenced during maintenance window",
        "status": {
          "state": "active"
        }
      }
    ]
  }
}
{
  "code": 200,
  "message": "silences retrieved successfully",
  "data": {
    "silences": []
  }
}
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"
      }
    ]
  }
}