---
title: "Retrieve the monitoring of a screening"
method: GET
path: "/screenings/{screening_id}/monitoring"
tags: ["Screenings"]
---

# Retrieve the monitoring of a screening

`GET /screenings/{screening_id}/monitoring`

## Request

- Base URL: `https://developers.ozav.io/v2`
- URL: `https://developers.ozav.io/v2/screenings/{screening_id}/monitoring`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Whether the screening is under monitoring, until when, and the alerts it raised (the 100 most recent).

## Path parameters

- `screening_id` string, required

## Response `200`

The monitoring of the screening.

- ScreeningMonitoring
  - `object` 'screening_monitoring', required
  - `screening_id` string, required
  - `active` boolean, required
  - `monitoring_until` string, date-time, nullable, required: When the monitoring ends (or ended). `null` = never monitored.
  - `alerts` ScreeningAlert[], required: The alerts raised, most recent first (up to 100).
    - `id` string, required: Opaque alert id, prefixed `ozav_sca_`.
    - `list_source` string, required: The list, in the vocabulary of `matches[].list_source`.
    - `matched_name` string, required
    - `strength` 'exact' | 'alias' | 'fuzzy', required
    - `list_entry_ref` string, required: The list entry, as in `matches[].list_entry_ref`.
    - `created_at` string, date-time, required

## Other responses

- `401`: Missing or invalid API key.
- `403`: The organization lacks the entitlement (code ENTITLEMENT_REQUIRED) or the key lacks the scope (code INSUFFICIENT_SCOPE). On money-moving requests (POST /transfers, POST /wallets/{wallet_id}/transfers) a compliance hold on the customer answers with code COMPLIANCE_HOLD: the hold is reviewed and lifted on OZAV's side; retrying does not clear it. When the only hold is a pause until pending onboarding documents are received, a withdrawal answers CUSTOMER_DOCUMENTS_PENDING instead: send what `requirements` on GET /customers/{id} lists; OZAV lifts the pause after reviewing it. On OZAV Services (live without the platform's KYB), any API outside decisions, screenings, lists and self-custody wallets answers with code PRODUCTION_NOT_ACTIVATED.
- `404`: The resource does not exist, is not visible to the caller, or the id was malformed for this position (see "Resource ids" under Errors). These share one status; `code` and `message` tell them apart.
- `503`: A dependency OZAV needs (storage, a resource lookup) could not be reached, so OZAV fails closed rather than guess. Safe to retry with the same `Idempotency-Key` where the operation accepts one.

---

[API](https://skmtc.dev/ozav/apis/ozav-api.md) - [All operations](https://skmtc.dev/ozav/apis/ozav-api/llms.txt) - [OpenAPI document](https://skmtc.dev/ozav/apis/ozav-api/revisions/4133dc2109d7?raw)