Create a new channel for incident management.
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 a channel.
Owning team ID.
Channel name. 1 to 59 characters.
1 - 59Additional teams that can manage the channel. Up to 3 entries.
3Free-form description. Up to 500 characters.
500Default escalation rule applied to the channel. Omit to skip default escalation.
Alert grouping configuration.
Flapping detection configuration.
Auto-resolve timeout in seconds. 0 disables auto-resolve. Max 30 days.
0 <= x <= 2592000Auto-resolve timer reset mode.
trigger, update IDs of plugins (integrations) subscribed to this channel.
When true, the channel is visible only to its managing teams.
Disable outlier incident detection.
Disable automatic incident closing.
Allow external reporters to file incidents into this channel.
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.