Submit an AML screening
Screens a person or company (detected from the payload) against sanctions, PEP and adverse-media lists via the compliance service. This is list screening only — identity verification with documents and liveness lives under /v1/kyc and /v1/kyb. All identity fields are optional and forwarded whole to the screening engine; the more identity data you send (date of birth, countries, strong identifiers, aliases), the more precise the analysis. If a compliance fee is configured, it is debited before the call and refunded if the screening fails. The result is stored locally for audit history (GET /v1/aml/screenings). idempotency_key is required — replaying with the same key returns the original screening with idempotency_hit true and never charges twice.
Authorizations
Session JWT (from register/login) or API key (pk_...).
X-API-Key: <token> is accepted as an alternative header.
Body
Required (the screening charges a fee). Also accepted as the Idempotency-Key header.
Identity data. Provide person or company; when omitted
it is filled from the account profile. Additional fields are accepted
and forwarded to the screening engine.
Enable continuous monitoring from the start.
Response
Screening submitted and stored locally.
Local mirror of the screening plus billing fields. The full result is in result.
screening compliance_person, compliance_company person, company Provider-neutral screening outcome from the compliance service.