Re-screen a Beneficiary
Queue a fresh compliance screen (sanctions / PEP / adverse media) of
an active beneficiary. Asynchronous: responds 202 immediately and
the screening worker runs the check. A non-clear outcome blocks the
beneficiary pending review and dispatches screening.hit and
beneficiary.blocked webhook events; a clear outcome changes
nothing. Both the request and the screening outcome are audited.
Not the same as POST /v1/beneficiaries/{id}/rescore, which
recomputes the engine risk score.
Requires an Idempotency-Key header.
Authorizations
Per-request DPoP proof JWT (RFC 9449). MUST accompany the Authorization: DPoP <access_token> header on every protected operation. The proof is signed by the merchant's private DPoP key and carries htm, htu, iat, jti, and ath claims.
Headers
Unique key identifying this operation. Sending the same key twice returns the original response instead of creating a duplicate. Keys are retained for 24 hours.
255Path Parameters
^ben_[a-zA-Z0-9]+$Response
Screening queued.