Werk #22089: REST-API: Order notification rules
| Component | REST API | ||
| Title | REST-API: Order notification rules | ||
| Date | Aug 3, 2026 | ||
| Level | Trivial Change | ||
| Class | New Feature | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
You can now change the position of a notification rule via the REST-API, and see where a rule sits in the chain.
Move a notification rule
The new endpoint POST /objects/notification_rule/{rule_id}/actions/move/invoke
moves a single rule within the notification rule chain. Pick one of four
positions in the request body:
{"position": "top_of_list"}
{"position": "bottom_of_list"}
{"position": "before_specific_rule", "rule_id": "<other rule id>"}
{"position": "after_specific_rule", "rule_id": "<other rule id>"}
The endpoint answers with 204 No Content. Read the rule again to see its new
position.
See the position of a rule
All notification rule responses now carry a rule_index extension next to
rule_config:
{
"id": "5425d554-5741-4bbf-b907-1a391dfab5bb",
"extensions": {
"rule_index": 2,
"rule_config": {}
}
}
Notification rules are evaluated from top to bottom, so a lower rule_index
means the rule is checked earlier. Newly created rules are still appended to the
end of the chain, and updating a rule leaves its position untouched.