POST
/api/v1/verification/aml-screening/sanction/

Screens an individual against global sanctions lists only.

Identical to /aml-screening with check_type: ["sanction"], kept as its own route so callers who never run PEP checks do not have to send the check type on every request. PEP matches are not returned.

Billed per screening and debited from the organisation wallet. A 402 means the balance is below the screening price.

Authorization

ApiKeyAuth
X-API-Key<token>

In: header

Request Body

TypeScript Definitions

Use the request body type in TypeScript.

Serializer for AML Screening request. Handles both sanction and PEP screening.

Response Body

application/json

curl -X POST "https://example.com/api/v1/verification/aml-screening/sanction/" \  -H "Content-Type: application/json" \  -d '{    "first_name": "John",    "last_name": "Doe",    "dob": "1985-04-12"  }'
{  "data": {},  "status": true,  "response_code": "00",  "message": "string",  "billing_info": {    "was_charged": true,    "amount": "string",    "currency": "string"  }}
Response Codes & Statuses: Prembly API responses include custom response_code values (e.g., 00 Success, 01 Not Found, 02 Unavailable).
View Response Codes Guide
Prembly Slack Community

Join our developer Slack channel for real-time integration support, engineering updates, and direct Q&A with the Prembly team.

Join Slack Channel