Create or update incident trigger subscription
Create or update an incident trigger subscription for AI SRE automation.
Restrictions
Usage
- Use this when an AI SRE automation rule needs to receive new-incident trigger events from selected On-call channels.
source,consumer, andconsumer_refidentify the subscription. Omittingsubscription_idupserts the row for that tuple.- Only
Critical,Warning, andInfoseverities are valid;enableddefaults to true. - Every call is recorded in the account audit log. Don’t put secrets in request fields.
Authorizations
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.
Body
Create or update an incident trigger subscription.
Subscription source. Use ai_sre_automation for AI SRE automation rules.
Consumer system. Use fc_safari for AI SRE automation rules.
Consumer-owned reference, such as an Automation rule ID.
On-call channel IDs whose new incidents should trigger the consumer.
1Incident severities to subscribe to. Ok is not valid.
1Critical, Warning, Info Existing subscription ID. Omit to create or upsert by source, consumer, and consumer_ref.
Whether the subscription is enabled. Defaults to true when omitted.
Response
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.