Deletes a system-scoped Alertmanager silence after validating that the silence belongs
to the target system through the authoritative system_key matcher.
Requires manage:systems permission.
DELETE
/systems/{id}/alerts/silences/{silence_id}
curl \
--request DELETE 'https://api.your-domain.com/api/systems/sys_123456789/alerts/silences/4e6f0c30-c383-4e22-9443-0d7b6a8bd40b' \
--header "Authorization: Bearer $ACCESS_TOKEN"
Response examples (200)
The silence is expired (not hard-deleted) so it disappears
from `GET /silences` but stays referenced in the alert's
activity timeline as an `unsilenced` event. On the wire
the response also carries `"data": null`; the example
omits it to match the declared schema which only includes
`code` and `message`.
{
"code": 200,
"message": "silence disabled successfully"
}
Response examples (400)
{
"code": 400,
"message": "validation failed",
"data": {
"type": "validation_error",
"errors": [
{
"key": "username",
"message": "required",
"value": "string"
}
]
}
}
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"
}
]
}
}