Skip to main content
POST
/
channel
/
silence
/
rule
/
update
Update silence rule
curl --request POST \
  --url 'https://api.flashcat.cloud/channel/silence/rule/update?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "channel_id": 1001,
  "rule_id": "6621b23f4a2c5e0012ab34cd",
  "rule_name": "Mute during maintenance",
  "time_filter": {
    "start_time": 1710000000,
    "end_time": 1710086400
  },
  "filters": [
    [
      {
        "key": "labels.service",
        "oper": "IN",
        "vals": [
          "billing"
        ]
      }
    ]
  ]
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsChannels Manage (on-call)

Authorizations

​
app_key
string
query
required

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

application/json

Parameters for updating a silence rule. Exactly one of time_filter or time_filters must be provided, and filters must be non-empty.

​
channel_id
integer<int64>
required

Channel the rule belongs to.

​
rule_id
string
required

Silence rule ID (MongoDB ObjectID).

Pattern: ^[0-9a-fA-F]{24}$
​
rule_name
string
required

Rule name, 1 to 39 characters.

Required string length: 1 - 39
​
priority
integer

Evaluation priority. Lower runs first.

​
description
string

Rule description, up to 500 characters.

Maximum string length: 500
​
time_filters
object[]

Recurring time windows. Mutually exclusive with time_filter.

​
time_filter
object

One-off time window defined by unix seconds.

​
filters
object[][]

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.

​
is_directly_discard
boolean

When true, silenced alerts are dropped instead of suppressed into incidents.

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.

​
request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

​
data
object
required

Empty response body. The server returns data: null on success.