ackOrgMultipleAlarms
Acknowledge multiple organization alarms by alarm ID and optionally attach a note to the acknowledgement.
Preferred authentication method for automation and integrations. Send the API token in the HTTP Authorization header.
Format:
Authorization: Token {apitoken}
Notes:
- An API token generated for a specific admin has the same privileges as that admin
- An API token is automatically removed if it is not used for more than 90 days
- SSO admins cannot generate admin API tokens. Use organization API tokens when scoped Org/Site privileges are needed.
In: header
Path Parameters
uuidRequest Body
application/json
Request Body
Alarm identifiers and optional note used for bulk alarm state changes
Alarm identifiers to acknowledge or unacknowledge
Some text note describing the intent
Response Body
curl -X POST "https://example.com/api/v1/orgs/000000ab-00ab-00ab-00ab-0000000000ab/alarms/ack" \ -H "Content-Type: application/json" \ -d '{ "alarm_ids": [ "ccb8c94d-ca56-4075-932f-1f2ab444ff2c", "98ff4a3d-ec9b-4138-a42e-54fc3335179d" ], "note": "maintenance window" }'ackOrgAllAlarms POST
Acknowledge all alarms in the organization and optionally attach a note. For targeted bulk updates, use [Ack Org Multiple Alarms](/api/mist/orgs/orgs-alarms/ackOrgMultipleAlarms) with up to 1000 alarm IDs per request.
countOrgAlarms GET
Count alarms across the organization, optionally grouped by the `distinct` field and filtered by time range.