Create or update routing rules for an integration to direct alerts to specific channels. At least one of cases or default must be provided.
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 | Integrations 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 or updating the routing rule of an integration. The handler creates a rule when none exists for the integration, otherwise it overwrites the existing one. At least one of cases or default must be provided.
Integration the rule belongs to.
Ordered list of case branches. Cases are evaluated top to bottom.
Optional sections that group consecutive cases for display.
Default branch used when no case matches (or all matched cases yield no valid channels).
Expected current version for optimistic concurrency control. Pass the value returned by the latest read.
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.