Update silence rule
Update an existing silence rule configuration.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Channels Manage (on-call) |
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Parameters for updating a silence rule. Exactly one of time_filter or time_filters must be provided, and filters must be non-empty.
Channel the rule belongs to.
Silence rule ID (MongoDB ObjectID).
^[0-9a-fA-F]{24}$Rule name, 1 to 39 characters.
1 - 39Evaluation priority. Lower runs first.
Rule description, up to 500 characters.
500Recurring time windows. Mutually exclusive with time_filter.
One-off time window defined by unix seconds.
OR-of-AND filter tree. Outer array is a list of AND groups; the condition passes if any AND group matches. Within each AND group, all conditions must match.
AND group — all conditions in this array must match.
When true, silenced alerts are dropped instead of suppressed into incidents.
When true, the silence rule is automatically deleted after its time window expires. Defaults to false.
Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.