---
title: "List alerts"
method: GET
path: "/data-observability/v1/alerts"
tags: ["Alerts"]
---

# List alerts

`GET /data-observability/v1/alerts`

## Request

- Base URL: `https://your-environment.ataccama.one/api`
- URL: `https://your-environment.ataccama.one/api/data-observability/v1/alerts`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/ataccama/apis/ataccama-one-agentic-data-trust-platform-public-api/docs/data-observability/v1/alerts/get.ts> (a function with typed inputs; its response is checked against the schema)

List the alerts in your environment.

To restrict the result by status, severity, or resolution, use the corresponding query parameters.
Each parameter accepts a single value. For multi-value or negated conditions, or to filter by finding type,
affected asset, or creation date, use [Filter alerts](#tag/alerts/POST/data-observability/v1/alerts/filter) instead.

Paging is forward-only.

## Query parameters

- `after` string
- `size` integer
- `sort` string
- `status` string
- `severity` string
- `resolution` string

## Response `200`

Paginated list of alerts.

- object
  - `meta` PaginationMetadata
    - `next` string: Encoded string representing the next page. Omitted if there are no more pages.
    - `total` integer: Total number of items available across all pages.
  - `data` AlertResponse[]
    - `urn` string, uri, required: URN of a Data Observability alert. Format: urn:ata:{tenant}:data-observability:alert:{uuid} Example: urn:ata:acme-corp:data-observability:alert:0197f3a0-1111-7c0c-8f9d-3a2b4c5d6e7f.
    - `status` string, required: @ExtensibleEnum The alert lifecycle status, taken from the findings: - `ACTIVE`: One or more of the alert's findings are still active. - `STALE`: None of the alert's findings are active, but one or more are stale. - `INACTIVE`: All of the alert's findings are inactive, and the alert has ended.
    - `severity` string, required: @ExtensibleEnum The highest severity among the alert's findings: `LOW`, `MEDIUM`, `HIGH`, or `CRITICAL`.
    - `resolution` string, required: @ExtensibleEnum How your team triaged the alert, as set in the web application: - `NOT_SET`: The resolution has not been decided yet. - `OPEN`: The alert requires attention. - `EXPECTED`: The behavior is acceptable and aligns with expectations. - `FALSE_POSITIVE`: The alert was triggered incorrectly and does not reflect a real problem. - `RESOLVED`: The underlying cause has been addressed. - `ESCALATED`: The alert has been escalated to Jira or ServiceNow. The resolution can change at any time, even after the alert has ended.
    - `createdAt` string, date-time, required: When the alert was created.
    - `updatedAt` string, date-time: When the alert's findings were last updated. The timestamp tracks updates to the findings only, not changes to the alert's resolution. The field cannot be filtered on. To detect resolution changes, re-fetch the alerts and compare fields.
    - `resolvedAt` string, date-time, nullable: When the alert was last resolved. Omitted while the alert is unresolved. The type still admits null so a future implementation may send it explicitly.

## Other responses

- `400`: Bad request. The request parameters or body are invalid.
- `403`: Forbidden. You do not have permission to access the requested resource.

---

[API](https://skmtc.dev/ataccama/apis/ataccama-one-agentic-data-trust-platform-public-api.md) - [All operations](https://skmtc.dev/ataccama/apis/ataccama-one-agentic-data-trust-platform-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/ataccama/apis/ataccama-one-agentic-data-trust-platform-public-api/revisions/46f16e0487f8?raw)