---
title: "Screen a name or RF identifier against Russian regulatory watchlists"
method: POST
path: "/api/v1/entity/rf-watchlists/screen"
tags: ["Sugra Entity"]
---

# Screen a name or RF identifier against Russian regulatory watchlists

`POST /api/v1/entity/rf-watchlists/screen`

Screen a person or organization name (name_fuzzy) or a Russian registry identifier (identifier_exact: inn/ogrn/snils/reg_number/domain/url) against Russian domestic regulatory lists currently loaded in the Entity corpus (Minjust extremist organizations / 114-FZ; foreign agents / undesirable when present). Provide name OR identifier, not both. Default listing is active-only; set include_excluded=true for research mode. This is NOT a Western sanctions screen - use POST /entity/screen for OFAC/EU/UN/... Fail-CLOSED: if no RF regulatory list is loaded, returns 503. Identifier mode requires the SQL RF package (ENTITY_RF_SQL).

## Request body

- EntityScreenRequest
  - `name` string, nullable
  - `country` string, nullable
  - `dob` string, nullable
  - `nationality` string, nullable
  - `as_of` string, nullable
  - `threshold_hit` number
  - `threshold_review` number
  - `corpus` 'sanctions' | 'rf_regulatory' | 'all'
  - `include_excluded` boolean
  - `identifier` RfIdentifierRequest — RF-only exact identifier (INN/OGRN/SNILS/domain/...). Not OFAC docs.
    - `type` 'inn' | 'ogrn' | 'snils' | 'reg_number' | 'domain' | 'url', required
    - `value` string, required

## Response `200`

Successful Response

- EnvelopeEntityRfWatchlistsScreenData
  - `data` EntityRfWatchlistsScreenData, required
    - `screening` EntityRfWatchlistsScreenScreening
      - `status` string, nullable
      - `matches` unknown[], nullable
        - unknown
  - `meta` SugraMeta, required — Metadata attached to every /api/v1/* response envelope.
    - `endpoint` string, required — Requested endpoint path.
    - `data_time` string, required — ISO 8601 UTC timestamp of the source data, not of the request.
    - `response_time` string, required — ISO 8601 UTC timestamp when this response was produced.
    - `provider` string, required — API name and version.
    - `source` string, nullable — Identifier of the primary upstream source used for this response.
    - `attribution` string, nullable — Human-readable attribution mandated by an upstream source (e.g. a securities regulator or self-regulatory organization). Present only on responses whose source requires the owner and source to be clearly identified. Do not remove or alter it when using the response.
    - `fallback_used` boolean, nullable — True when the primary source failed and a fallback produced the data.
    - `fallback_chain` string[], nullable — Ordered list of sources attempted, in the order they were tried.
    - `cached` boolean, nullable — True when this response was served from the internal cache.
    - `stale` boolean, nullable — True when the cached response was returned after the upstream rate-limited or errored. Clients can use this to detect degraded data.

## Other responses

- `401` — Missing or invalid `x-api-key` header. JSON body with a stable `code` distinguishing `missing_api_key` (no header sent) from `invalid_api_key` (header sent, key not accepted); any other 401 source carries the generic `unauthorized` with its detail as `reason`. Plus `hint`. `plan` is always null on 401 - an unauthenticated request has no plan; quota exhaustion is 429, not 401.
- `422` — Validation Error
- `429` — Daily rate limit exceeded. Check `X-RateLimit-Reset` for the next window.
- `503` — Upstream source is temporarily unavailable. Retry after a short delay.

---

[API](https://skmtc.net/sugra/apis/sugra-api.md) · [All operations](https://skmtc.net/sugra/apis/sugra-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sugra/sugra-api/revisions/914af3d38c7c/schema)