Partially updates an organization notification with an application/merge-patch+json body (RFC 7396). Omitted fields stay unchanged; nested objects are deep-merged; nested arrays (for example allocations.ids) are replaced when present. When destinations is present it replaces the whole destinations object; the nested emails, slackChannels, and teamsChannels arrays are the full lists. Send null for a settings property to unsubscribe that type. Nulling the last type is 422. A channel that a remaining type does not support is 422 customers.channel_not_supported. A Teams destination on a type that supports Teams is 422 validation_failed when the tenant has no Teams entitlement. Optional resend fields are cleared with null (for example "settings":{"costAnomalies":{"repeat":null}}). minSeverity, minExcessCost, and allocations cannot be cleared. An id whose config stores a dashboard, report, or commitment subscription or a prompt schedule returns 404. A settings property that is not on PatchCustomerNotificationSettings is 422.
Requires the settings (Manage settings) permission and the If-Match header. The Idempotency-Key header is required. The same key, the same body, and the same If-Match replay the stored success. A different body or a different If-Match is 422 idempotency_key_reused. A 5xx response may leave the key reserved, so a retry returns 409 until the original request is released or about 30 minutes pass. dryRun=true does not reserve the key. With dryRun=true the request goes through the same checks as a real update and returns the notification as it would look after the patch, without changing anything.
Reads are immediately consistent. After a completed update, a GET of that notification returns the new state.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||