White Papers

49 REST API Guide  OpenManage Essentials | Revision A02
2.9.4 AlertSubscription PUT command
An update of the subscription information can be accomplished with a PUT operation.
Note: The payload for the PUT operation is identical to the payload of the POST operation.
Note: The subscription corresponding to the device identifier will be updated (if it exists). If the subscription
with the corresponding device identifier does not exist, then the operation will return an error in the response
header
2.10 Alert subscription notification
The alert subscription notification enables the mobile user to see the latest status of a notification that is
associated with a subscription. This enables the administrator to sync his status with the status that is perceived
by the Alert Subscription Manager in OpenManage Essentials.
The following resource URI supports alert subscription notifications:
Alert subscriptions: <BASE_URI>/AlertSubscriptionNotifications
Operations supported: GET and PUT
Attributes (filtering): Id, SubscriptionId, and AlertFilterId
The attributes associated with the alert subscription notification are described in the following table.
Attribute Name
Description
Id
The unique identifier for the subscription notification.
SubscriptionId
The subscription identifier.
AlertFilterId
The filter identifier associated with the subscription.
NewAlertCount
The number of new alerts associated with this subscription notification.
LastEventId
The last event identifier that is associated with the notification.
NotificationTimestamp
The timestamp associated with the last time data was pushed.
The PUT operation clears the NewAlertCount to 0 indicating to the Alert Subscription Manager in OpenManage
Essentials that the data has been read by the mobile device.