---
title: "GET /status"
method: GET
path: "/status"
---

# GET /status

`GET /status`

## Request

- Base URL: `https://dev-cloud.acronis.com/api/alert_manager/v1`
- URL: `https://dev-cloud.acronis.com/api/alert_manager/v1/status`
- Auth: OAuth 2
  - Authorization code: `https://dev-cloud.acronis.com/api/2/idp/authorize`
  - Client credentials
  - Password
  - Token URL: `https://dev-cloud.acronis.com/api/2/idp/token` scopes: `urn:acronis.com::alert_manager::viewer`

Returns the last of the most critical alerts grouped by selected scope.

## Query parameters

- `scope_key` string, required: Groups the results by the context key or searchable details. See registered alert types for available context keys and searchable details.
- `scope_value` string[]: Scope values to filter alerts by. If omitted, the response will contain the last most critical status among available alerts. Client may group statuses for multiple scope values by using the `or()` operator: * Example: `scope_key=KEY&scope_value=VAL1&scope_value=VAL2` - looks for two statuses * Example: `scope_key=KEY&scope_value=or(VAL1,VAL2)` - looks for single status * Example: `scope_key=KEY&scope_value=or(VAL1,VAL2)&scope_value=VAL3` - looks for two statuses Client should explicitly url-encode values breaking URL syntax. For example, to find a status of the resource with the `stepName` key containing `step 01` or `step 02`: `scope_key=stepName&scope_value=or(step%201,step%202)`

## Response `200`

Alert list grouped by scopes.

- object
  - `items` ScopeStatus[], required
    - `scope` object, required: Value of scope. Contains values of context or searchable details.
    - `status` Status, required: Status of any scope that represents the last alert with the highest severity in the scope.
      - `id` string, required: ID of the alert.
      - `type` string, required: Type of the alert.
      - `severity` 'ok' | 'information' | 'warning' | 'error' | 'critical', required: Severity level of the alert.
      - `createdAt` string, date-time, required: A date and time when the alert was created.
      - `details` object, required: Details about the alert.

## Other responses

- `400`: Bad request.
- `401`: Request is refused because authentication parameters are invalid.
- `403`: A security error due to an issue with tenant security claim: invalid tenant in the access token, tenant resolution failed and etc.
- `414`: Too many scope values. For cloud deployment there is no practical limitation. For on-premise deployment known limits imposed by database engine are 32766 for SQLite and more than 32768 for MS SQL Server.

---

[API](https://skmtc.dev/acronis/apis/alert-manager-api.md) - [All operations](https://skmtc.dev/acronis/apis/alert-manager-api/llms.txt) - [OpenAPI document](https://skmtc.dev/acronis/apis/alert-manager-api/revisions/540eec169663?raw)