Create an inhibit rule to suppress lower-priority alerts when higher-priority ones are firing.
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.
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Channels Manage (on-call) |
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.
Parameters for creating an inhibit rule.
Channel the rule belongs to.
Rule name, 1 to 39 characters.
1 - 39Label keys used to pair source and target alerts.
Evaluation priority. Lower runs first.
Rule description, up to 500 characters.
500Or-of-and filter tree. Each outer element is an AND group; within each group, all conditions must match.
Or-of-and filter tree. Each outer element is an AND group; within each group, all conditions must match.
When true, suppressed target alerts are dropped instead of merged.
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.