Update an existing channel’s configuration and settings.
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 updating a channel. Only the fields you pass are updated.
Channel ID to update.
New owning team ID.
Additional teams that can manage the channel. Up to 3 entries.
3New channel name. 1 to 59 characters.
1 - 59New description. Up to 500 characters.
500Auto-resolve timeout in seconds. 0 disables auto-resolve. Max 30 days.
0 <= x <= 2592000Auto-resolve timer reset mode.
trigger, update When true, the channel is visible only to its managing teams.
Alert grouping configuration.
Flapping detection configuration.
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.
Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.
"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"
Response from updating a channel. Only populated when is_external_report_enabled is set to true; otherwise all fields are empty.