---
title: "List findings"
method: GET
path: "/data-observability/v1/findings"
tags: ["Findings"]
---

# List findings

`GET /data-observability/v1/findings`

## Request

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

List the findings in your environment.

To list the findings of one alert, use the `alertUrn` parameter. To restrict the result by finding type
or status, use the corresponding query parameters. Each parameter accepts a single value. For multi-value
or negated conditions, or to filter by affected asset, use [Filter findings](#tag/findings/POST/data-observability/v1/findings/filter) instead.

Paging is forward-only.

## Query parameters

- `after` string
- `size` integer
- `sort` string
- `alertUrn` string, uri: 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.
- `findingType` string
- `status` string

## Response `200`

Paginated list of findings.

- 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` FindingResponse[]
    - `urn` string, uri, required: URN of a Data Observability finding. Format: urn:ata:{tenant}:data-observability:finding:{uuid} Example: urn:ata:acme-corp:data-observability:finding:0197f3a0-2222-7c0c-8f9d-3a2b4c5d6e7f.
    - `alertUrn` string, uri: 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.
    - `findingType` string, required: The type of the finding as a hierarchical, dot-separated code, for example, `data.dq.threshold-breach-rule` or `job.failure`. In filters, a value matches the exact code and all its subtypes. For the full taxonomy and the meaning of each code, see the Findings group description. The set is fixed within a release but can change between releases. Handle unknown codes gracefully.
    - `severity` string, required: @ExtensibleEnum The severity of the finding: `LOW`, `MEDIUM`, `HIGH`, or `CRITICAL`.
    - `status` string, required: @ExtensibleEnum The finding lifecycle status: - `ACTIVE`: The problem is still being observed. - `STALE`: The problem has not been observed recently. - `INACTIVE`: The problem has ended (see `endedAt`).
    - `summary` string: A human-readable summary of the finding, for example, `Completeness on customer.email dropped to 71% (threshold 95%).`
    - `affectedAssetUrn` string, uri, required: A URN identifying a resource in any realm of the Public API. URNs follow RFC 8141. Format: urn:ata:{tenant}:{realm}:{resource-type}:{uuid} Components: - `urn` — fixed scheme - `ata` — Ataccama namespace - `{tenant}` — tenant identifier from the authentication context - `{realm}` — API realm, for example `catalog` or `reference-data` - `{resource-type}` — resource type within the realm, for example `catalog-item` or `table` - `{uuid}` — UUID (v4 or v7) of the resource Example: urn:ata:acme-corp:reference-data:table:123e4567-e89b-12d3-a456-426614174000.
    - `firstSeenAt` string, date-time, required: When the problem was first observed.
    - `lastSeenAt` string, date-time, required: When the problem was last observed.
    - `endedAt` string, date-time, nullable: When the problem ended. Set only once the finding is `INACTIVE`; omitted while it is `ACTIVE` or `STALE`. The type still admits null so a future implementation may send it explicitly.
    - `createdAt` string, date-time, required: When the finding was registered (the server-side ingest time). This is the default sort field; it can differ from `firstSeenAt` by ingest lag.

## 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)