Open API
Introduction
Initiate a new applicant registration process in the KYC system by providing the necessary details. Returns a comprehensive applicant profile upon successful creation.
A unique applicant identifies on the client side
A flow name
An applicant phone number.
An applicant email address.
The language, in which the verification results should be displayed to applicants.
Used to compare the data that you provide to us with that we extract from the applicant documents.
Retrieve comprehensive applicant details using either the internal ID or an external user identifier.
Internal ID or an external user identifier.
Internal ID or an external user identifier.
Transition the applicant to a new verification flow stage by updating their workflow based on the provided flow details.
Internal ID or an external user identifier.
A flow id
Mark an applicant for deletion, scheduling their record for removal in accordance with system retention policies.
Internal ID or an external user identifier.
Restore a previously marked applicant, reactivating their record and enabling them to continue with the verification process.
Internal ID or an external user identifier.
Generate a new verification token to client-side identity validation during the verification process.
Internal ID or an external user identifier.
Optional locale specifying the language for the verification token. Must be a valid locale string (e.g., "en-US").
Optional time-to-live (TTL) for the verification token in seconds.
Optional name of the verification flow to be applied
Blockchain network to perform the AML search. Accepted values are defined in the BlockchainEnum.
Optional transaction hash for the AML search. Must be a 64-character hexadecimal string, optionally prefixed with "0x". This field is mutually exclusive with "address".
^(0x)?[a-fA-F0-9]{64}$Optional blockchain address for the AML search. Must be a valid blockchain address and is mutually exclusive with "txHash".
Last updated