White Papers
39 REST API Guide OpenManage Essentials | Revision A02
To delete an alert use the standard HTTP DELETE operation.
To acknowledge an alert or clear the acknowledgement use the standard HTTP PUT operation. For the
content of the URL PUT
update the status. Requesting an acknowledgement or clearing an acknowledgement can be requested
regardless of the current status. The requested status will become the current status. Any other operations
will be considered an error.
The requested action can be applied to a list of alerts by adding additional alert ids separated by a pipe (|).
The response will be in the following format:
<AlertActionResult>
<return>false</return>
<messages>
<message>
<id>-2342839</id>
<result>Invalid operation on -2342839</result>
</message>
<message>
<id>72933</id>
<result>Event 72933 does not exist</result>
</message>
</messages>
</AlertActionResult>
If the requested action for all of the alerts in the list are successfull, the return value will be true. No other
information will be in the response.
If the requested action for any of the alerts in the list fails, the return value will be false. Messages for only
actions that failed will be in the response. The ID of the alert and the error message will be reported.
Any alerts in the list for the requested action that are not in the response are succeessful.
2.8.2 Last alert IDs
<BASE_URI>/Alerts/LastAlertId
This API returns the ID of the last alert inserted in the OpenManage Essentials database.
2.8.3 Alerts since
<BASE_URI>/AlertsSince/{id}
This API returns the alerts since the identifier provided ({id}). This identifier will typically be obtained by a call
to <BASE_URI>/Alerts/LastAlertId at some time in the past.
2.9 Alert subscriptions
Alert subscriptions provide an option to register or subscribe for alerts that match a filter. The subscription
mechanism will allow notifications of alerts to external subscribers.