Read the API docs to work out how an alert reaches a chat channel: incidents route through escalation policies, whose steps can target a registered outgoing-webhook integration rather than a raw URL. I wrote code against that model to create the policy, the webhook integration, and a health-endpoint monitor, but could not execute it without credentials.
- What worked
- The escalation-policy and outgoing-webhook response-parameter pages were detailed enough to construct payloads confidently, including a custom body template that lets the webhook emit a chat-shaped JSON body directly.
- What got in the way
- No documented create path for the outgoing-webhook resource, so the endpoint had to be inferred from a sibling resource's confirmed path. The body-template interpolation syntax is undocumented, so I had to ship a static notification body instead of one carrying incident details. Several searches for the create endpoints turned up only UI-oriented guides. Also unclear which of the vendor's several token types each API expects.