alerts.routing.manage. The fields are those of Create a routing rule; an optional field left out returns to its default. The rule keeps its place; Reorder routing rules changes it. Incidents already open are not affected.
curl -X PUT http://localhost:5080/api/v1/alerts/routing/rules/$RULE_ID \
-H "authorization: Bearer $MS_TOKEN" \
-H "content-type: application/json" \
-d '{"name": "Payments in production", "enabled": false, "target": {"kind": "team", "team_id": "<team-id>"}}'
Alerting
Update a routing rule
Write back an alert routing rule as a whole.
curl -X PUT http://localhost:5080/api/v1/alerts/routing/rules/$RULE_ID \
-H "authorization: Bearer $MS_TOKEN" \
-H "content-type: application/json" \
-d '{"name": "Payments in production", "enabled": false, "target": {"kind": "team", "team_id": "<team-id>"}}'
Last modified on October 31, 2026