Werk #22511: PagerDuty: REST API reads and writes the integration key in the wrong format
| Component | Notifications | ||
| Title | PagerDuty: REST API reads and writes the integration key in the wrong format | ||
| Date | Nov 19, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
The REST API endpoints for notification rules handled the integration key of the PagerDuty notification method in a format that does not match the one used by the Setup and the PagerDuty notification script:
- Rules created or changed through the REST API could not send notifications. The notification failed with "Password not found".
- Reading a rule returned
{"option": "store", "store_id": ""}for an integration key from the password store, and for an explicit key saved in the Setup. Writing such a rule back replaced the key with an empty password store reference.
The REST API now returns the integration key as configured and stores it in the same format as the Setup. Integration keys written by the REST API work again without any changes.
This does not apply to rules that were read through the REST API and written back: their integration key was replaced with an empty password store reference, so their notifications still fail with "Password not found". Enter the integration key of these rules again.