Skip to main content
POST
Create silence rule

Restrictions

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 creating 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_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
from_incident_id
string

Source incident ID when the silence was created from an incident.

time_filters
object[]

Recurring time windows during which silencing applies. Mutually exclusive with time_filter.

time_filter
object

One-off time window defined by unix seconds.

filters
object[][]

Or-of-and filter tree. Each outer element is an AND group; within each group, all conditions must match.

is_directly_discard
boolean

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

is_auto_delete
boolean

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.

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

Endpoint-specific payload. See each operation's 200 response schema.