AML screening
POST https://api-verify.secuveri.com/v1/aml/screen checks one person against the SECO, EU, UN, OFAC and UK sanctions lists and, unless include_peps is false, politically exposed persons. It uses the same lists, scoring and price as the AML workflow step. Send Idempotency-Key so retries reuse one screening result and charge. Raw subject input is not stored; saved responses, including your reference, are encrypted.
curl -X POST https://api-verify.secuveri.com/v1/aml/screen \
-H "x-api-key: $SECUVERI_API_KEY" \
-H "Idempotency-Key: $AML_REQUEST_ID" \
-H "content-type: application/json" \
-d '{"name":"Hans Müller","date_of_birth":"1970-05-04","nationality":"CHE","reference":"customer-42"}'name (or names, up to 5 spellings) is required; date of birth, nationality and document number make matches sharper. The answer has state (CLEAR or POSSIBLE_MATCH), each hit with its score breakdown, the list versions used, and signed_result, the same answer as a JWS you verify like a signed result.
Generate and save a unique AML_REQUEST_ID before the first attempt (8–200 printable non-space ASCII characters). Reuse it with the same details on retries, including after a timeout. Keys are scoped to your organization and environment. Replays return the original list versions and signed result for 24 hours from the first attempt. After expiry the key returns 410 and cannot charge again. Use a new key only for a new intended screening. Without the header, requests are independent and retries can charge again.
| Status | Meaning |
|---|---|
| 400 | Invalid input |
| 401 | Missing or unknown API key |
| 402 | The balance does not cover the screening |
| 409 | Same key in progress (retry after 1 second), different details, or a refunded reservation |
| 410 | Saved response expired; this key cannot charge again |
| 429 | More than 120 screenings in a minute |
| 503 | Source lists or matching capacity temporarily unavailable; retry with the same key. Capacity errors include Retry-After: 1 and start no charge |
To keep screening verified customers, turn on monitoring in the workflow's AML step. New hits put the verification back into review and send verification.review_required.