URL parameters
The ID of the Slack integration you want to update.
Headers
Bearer $TOKEN
application/json
Body parameters
How incidents are posted. verbose posts every incident to the single connected channel, thread starts a thread per incident in it, and channel creates a new channel per incident. thread and channel need a paid plan.
Who to always invite into the incident channel when integration_type is channel. An array of objects with a type and an id. type is user, on_call_calendar, or slack_user_group.
Make the incident channels private. Needs at least one entry in channel_invitees.
The name shown for the connected channel in Better Stack. Send null to show the channel's own name.
Let Slack users alert every team and escalation policy. Set it to false to allow only the ones in alert_options.
The teams and escalation policies Slack users can alert. A team is {"type": "team", "id": 7} with the booleans call, sms, email, push and critical_alert, each false when left out. An escalation policy is {"type": "policy", "id": 73}. The read-only keys a GET returns, name, team_id and team_name, are ignored, so you can send the alert_options from a GET back unchanged.
Invite new Slack users into your Better Stack team as responders.
Notify the channel when the primary responder changes.
Notify when a resource is paused.
Notify when an incident is resolved.
Send a direct message to people tagged in incident comments.
Start an AI SRE conversation when Better Stack is tagged.
Allow creating incidents only by the members of the connected channel.
Post incident timeline events about e-mails, phone calls, and integrations. Applies when integration_type is thread or channel.
Post incident metadata.
Post status page updates. Turning it off clears status_page_update_resources.
Post status page updates only for these affected resources, given as objects with a type and an id, or leave it empty to post updates for every resource of the integration's team. Needs post_status_page_updates turned on, and type is one of status_page, monitor, heartbeat, monitor_group, heartbeat_group, webhook_integration, email_integration, incoming_webhook, amazon_sns_integration, manually_tracked_item, logs_chart, or catalog_reference.
Notify this integration alongside the primary responder when no escalation policy is configured.