Create a new alert rule. Returns the created rule with its assigned ID.
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 | Alerting Rules Manage (monit) |
name, ds_type, cron_pattern, and rule_configs.queries are required.ds_list (supports wildcards) or ds_ids must be non-empty.cron_pattern uses standard 5-field cron syntax.channel_ids can be empty; alerts will then route through the global integration.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.
Full alert rule configuration.
Folder the rule belongs to.
Rule name.
Custom labels.
Data source type.
Data source name patterns (supports wildcards).
Specific data source IDs.
Rule evaluation configuration.
5-field cron schedule.
Time windows when the rule is active.
text, markdown Channel IDs to send alerts to.
Notification repeat interval in seconds.
Max number of repeat notifications.
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.