curl --request POST \
--url https://{environment-subdomain}.idmetagroup.com/api/v3/verifications/watchlist-aml-passthrough \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"name": "Example Person"
}
'{
"success": true,
"message": "Watchlist AML screening processed successfully",
"data": {
"matchCount": 0,
"matches": []
},
"verificationStatus": "VERIFIED",
"verificationStatusCode": 3,
"transactionId": "79b6f81c-fc48-42ce-b907-763129b0957e",
"verificationType": "aml",
"metadata": {
"yourRef": "case-1001"
},
"createdAt": "2026-09-03 08:00:00+0000"
}Compliance
Watchlist and AML Screening
Screen an individual against AML and watchlist datasets through the passthrough endpoint.
POST
/
api
/
v3
/
verifications
/
watchlist-aml-passthrough
curl --request POST \
--url https://{environment-subdomain}.idmetagroup.com/api/v3/verifications/watchlist-aml-passthrough \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"name": "Example Person"
}
'{
"success": true,
"message": "Watchlist AML screening processed successfully",
"data": {
"matchCount": 0,
"matches": []
},
"verificationStatus": "VERIFIED",
"verificationStatusCode": 3,
"transactionId": "79b6f81c-fc48-42ce-b907-763129b0957e",
"verificationType": "aml",
"metadata": {
"yourRef": "case-1001"
},
"createdAt": "2026-09-03 08:00:00+0000"
}Authorizations
Use your API token as a Bearer token in the Authorization header.
Headers
Example:
"Bearer {your_api_token}"
Body
application/json
Full name of the individual to screen.
Maximum string length:
255Example:
"Example Person"
Optional date of birth.
Minimum array length:
1Available options:
PEP, SAN, RRE, INS, DD, POI, REL Two-character country codes used to narrow the search.
Minimum array length:
1Required string length:
2Minimum array length:
1Available options:
PEP Tier 1, PEP Tier 2, PEP Tier 3 Required range:
75 <= x <= 100Available options:
fuzzy, strict Available options:
any, male, female Status applied when matches exist but there is no exact name and date-of-birth match.
Available options:
manual, rejected Optional client-defined values echoed in completed and source-error responses.
Response
Screening completed. No match, review-needed match, and rejected match outcomes all use HTTP 200.
Example:
true
Show child attributes
Show child attributes
Available options:
VERIFIED, REVIEW_NEEDED, REJECTED 3 = Verified, 2 = Review Needed, 1 = Rejected.
Available options:
3, 2, 1 Example:
"aml"
Example:
"2026-09-03 08:00:00+0000"