Create New Applicant

Authorizations

ds-api-token

string

header

required

Body

application/json

Create Applicant Request

Option 1
Option 2

Create Applicant Request

external_id

string

This is a unique identifier originating from your system, which will be associated and linked to the corresponding Applicant ID in our system.

Example:

"external_user_id_123"

string | null

applicant email

Example:

"[email protected]"

phone

string | null

applicant phone number

Example:

"+1234567890"

info

object

This object allows you to include any supplementary information about the applicant, such as their first, last name or citizenship.

Show child attributes

info.full_name

string

Full Person name, if not specified will fallback to first_name and last name

Example:

"John Doe"

info.first_name

string

First name

Example:

"John"

info.last_name

string

Last name

Example:

"Doe"

info.dob

string<ISO-8601>

Date of birth in ISO-8601 format

Example:

"1987-12-24T00:00:00.000Z"

info.gender

enum<string>

gender that is used in official documents

Available options:

M,

F

Example:

"M"

info.citizenship

string<ISO 3166-1 ALPHA-2 code>

Two-letter ISO 3166-1 ALPHA-2 code, reference https://www.iban.com/country-codes. Currently can be set via manual fields feature via API when creating applicants. (Available in provided_info in applicant)

Example:

"DE"

info.country

string<ISO 3166-1 ALPHA-2 code>

Two-letter ISO 3166-1 ALPHA-2 code, reference https://www.iban.com/country-codes. Country extracted from POI document. (Available in system_info in applicant)

Example:

"DE"

info.address

string

Applicant address, could be used for any type of applicants

Example:

"Paris, France"

info.addresses

object

List of applicant addresses, only residence for now.

Show child attributes

info.addresses.residence

object

Detailed address

Show child attributes

info.addresses.residence.country

string

required

ISO 3166-1 ALPHA-2 code

Example:

"DE"

info.addresses.residence.city

string

required

City name

Example:

"Berlin"

info.addresses.residence.postal_code

string

required

postal code (or zip) for the address.

Example:

"10999"

info.addresses.residence.street

string

required

Street adress line

Example:

"Wiener Straße 17"

info.custom_fields

object

Key - value object, values can be only strings

aml_screening_enabled

boolean | null

default:false

Enables the option to activate or deactivate daily AML monitoring for applicants. When an applicant is identified in any Sanction List during the monitoring process, a notification will be triggered through the configured Webhooks.

applicant_type

enum<string>

default:Person

Possible types

Available options:

Person,

Organization,

Country,

Vessel,

Aircraft,

CryptoWallet

search_options

object

The Search Options functionality is intended for the customization of applicant AML monitoring

Show child attributes

search_options.risk_scores

enum<string>[] | null

Assigned Risk Score

Available options:

Low,

Medium,

High

search_options.tags

enum<string>[] | null

Possible Entity Tags

Available options:

Finance,

Legal,

Terrorism,

Criminal,

PEP,

Media,

Social,

Sanctions,

UnofficialSource,

Leaks,

CompanyRegistry,

Associate,

Debarred

search_options.sources

string[] | null

Possible Source IDs, contains all publicly available sources, constantly updated, for the most up to date list please check https://dash.dataspike.io/pep-sanctions/data-sources

search_options.fuzziness

boolean | null

default:true

A boolean flag (True/False). When set to True (default), broad matches are allowed. If set to False, only exact matches are permitted.

search_options.fuzziness_level

number<double> | null

default:1

Controls the strictness of name matching. 0 means exact match, 1 means broad match. Recommended value is 1. Intermediate values (e.g., 0.5) can be used to fine-tune the balance between precision and scope.

Required range: 0 <= x <= 1

search_options.phonetics

boolean | null

default:true

This setting enables phonetic similarity during AML searches, which is helpful for finding similar names across different languages. We generally recommend keeping this set to True.

search_options.mode

enum<integer> | null

default:0

0 - AUTO(Recommended), Automatically optimize query - full_name serves as the primary search term, unless both the first and last names are provided. In such a scenario, the combination of the first and last names becomes the primary term, and the full_name is employed to enhance the relevance of results.

1 - FULL_NAME_ONLY, ignores first_name and last_name fields, and only use full_name in search requests

2 - FIRST_AND_LAST_NAMES_ONLY, ignores full_name field and uses only combination of first_name and last_name in search requests

Available options:

0,

1,

2

Response

200 - application/json

Create Applicant Response

string<uuid>

Id of created applicant

Example:

"01827ed4-c928-7a3c-9a30-7ab7cc169d11"

API documentation

Authorizations

Body

Response