Request watchlist verification
On this page, you will learn how to initiate a new watchlists verification using the API.
To initiate the watchlists verification process, send the first_name
, last_name
and born_on
informations using the following endpoint:
POST /verifications/watchlists
{
"workspace_id": null,
"natural_person": {
"first_name": "John",
"last_name": "Doe Smith",
"born_on": "1990-12-21"
}
}
In the response, you'll find the id
. This value is required to retrieve the verification results.
Query param rules
Strict matching recommended
We recommend using a strict match for any verifications:
first_name
,last_name
, andborn_on
must exactly be the verified person identity information.For example, if the name is “John Doe Smith”, do not send only “John Doe” or “John Smith”.
To help you perform accurate verifications and avoid false positives, here's some details about the query params:
Query Param | Description | Examples |
---|---|---|
natural_person [first_name] | The first name of the natural person to verify | John |
natural_person [last_name] | The last name of the natural person to verify | Doe |
natural_person [born_on] | The birth date of the natural person to verify (format: (YYYY-MM-DD) | 1980-01-01 |
workspace_id | Scopes the verification to a specific workspace. Defaults to the main workspace if not specified. | 090b4f7e-25e8-423d-9387-741f6188ba7a |
ℹ️ Formatting Tolerance
- Case-insensitive: Uppercase and lowercase differences do not impact verification.
For example: john is treated the same as John. - Accents tolerated: Minor variations such as "é" vs "e", or "è" vs "e", will not changed the match.
- Special characters: Hyphens (e.g., Anne-Marie) and apostrophes (e.g., O'Connor) must be included if they are present in the official identity. Their omission may lead to mismatches.
Updated 2 days ago