Updates the options and preferences for notifications.
The settings are replaced by the ones provided in the payload, therefore the complete configuration must always be sent: channels, severities, topics and locations.
Note that when allTopics or allLocations is true, the corresponding topics and locationIds lists are ignored.
Use me as userId to update the settings of the currently logged-in user.
Required permissions: WRITE_USER.
The name of the tenant (e.g. acme).
The id of the user whose notification settings must be updated. Use 'me' for the current logged in user.
The new notification settings.
User notification settings.
Delivery channels through which notifications can be sent.
Whether notifications are delivered via email.
Whether notifications are delivered via push notification.
If true, notifications apply to all locations and the locationIds list is ignored.
If true, notifications apply to all topics and the topics list is ignored.
Severity levels for which notifications are enabled.
Whether informational-severity notifications are enabled.
Whether warning-severity notifications are enabled.
Whether critical-severity notifications are enabled.
List of topics the subscription is limited to. Ignored when allTopics is true.
A topic name.
List of location identifiers the subscription is limited to. Ignored when allLocations is true.
A unique location identifier.
Successful creation.
The bean providing organization details.
The organization object identifier.
The name of the organization.
The country of the organization.
The country ISO Code of the organization.
The timezone used for date/times localization (e.g. Europe/Rome).
The parent organization identifier (required only for creation).
Request data not valid.
The error response.
User not authenticated.
The error response.
User not authorized.
The error response.
API call rate limit exceeded.
The error response.
Internal server error.
The error response.