In this section, you will find the specifics of creating a process that has Liveness + Identity Verification + Behavior Alert as a capabilities
In this section, you will find detailed documentation on the operation of the endpoints related to the capabilities Liveness + Identity Verification + Fraudster Profile Detection, used together.
These are two synchronous capabilities (Liveness + Identity Verification) integrated with one asynchronous capability (Fraudster Profile Detection). In other words, to retrieve all responses, it will be necessary to Get the Process Result.
For this integration, it will be necessary to consume two endpoints described in this documentation, which can also be combined with the use of Webhooks.
The capabilities of the Unico IDCloud platform via Client are managed through API Keys—used as a parameter in the request headers—that define the access scope. As a prerequisite, you must have an API Key configured with the capabilities Liveness + Identity Verification + Behavior Alert, ensuring dedicated and secure access to the resource.
Talk to your project manager to obtain the API Key with this configuration.
Your API requests are authenticated using an access token. Any request that does not include a valid access token will return an error.
You can learn more about generating an access token here.
Endpoints:
Production: https://api.id.unico.app/processes/v1.
Important:
If the response for the Identity Verification capability returns unicoId = yes, this result already includes Liveness (i.e., the liveness parameter will not be included in the response);
At the time of process creation, the response will not return the parameter identityFraudsters.result. This parameter will only be provided when Getting the Process Result, once the process is completed (status = 3);
To use the Liveness capability, it is mandatory to use our SDKs;
It is possible to use the Identity Verification capability without Liveness. For this use case, the liveness value will always return as liveness = 1. In this scenario, no Liveness validation is performed, not even passive validation.
If an error occurs during biometric processing, the request will return a status code = 200, and the process will return a status = 5, as shown in the example below:
Tips:
When implementing your business rules, always validate the final statuses of the processes (3, 4, 5). To validate the response of IDCloud capabilities, only consider status = 3 for your decision-making process.
In the v2 endpoint (/processes/v2/{id}), we also return additional user information, as shown in the example below:
Attention:
When making a GET request for a process with status = 5 (error), the return status code will be 410 (Gone) instead of 200 (Success);
The Identity Verification and Fraudster Profile Detection capabilities are entirely independent. To implement your business rules, make sure to analyze the meaning of each response.
Tips:
When implementing your business rules, always validate the final statuses of the processes (3, 4, 5). To validate the response of IDCloud capabilities, only consider status = 3 for your decision-making process;
To improve the performance of your operation, you can use our Webhooks and only get the results of processes that have a finalized status;
For more details on the scenarios you might receive in the response, refer to the Response Scenarios section;
For more information about possible errors for this endpoint, refer to the Errors section.
Still need help?
Didn't find something or still need help? If you're already a client or partner, you can reach out through our Help Center.
Endpoint to create a new process for Liveness + Identity Verification + Behavior Alert in by Client.
Valid access token.
Valid APIKEY with Liveness + Identity Verification + Behavior Alert capabilities enabled.
User information.
User's CPF. Must contain 11 characters and be sent without dots or dashes.
"12345678909"User's name.
"Luke Skywalker"User's email.
"luke@unico.io"User's phone number. Must contain 13 characters and be sent without dots or dashes, in the format DDI + DDD + Phone Number.
"551972557070"Use case for the operation.
"Onboarding"The ID of the branch where the process will be created. If there is only one branch associated with the service account, this parameter is not required. If there is a separation of processes by branch, you will receive the branch IDs from the Unico team.
"60837cd3-ed3c-4038-ad7c-0a85ad64b03a"Encrypted file generated by the SDK or Base64 (if not using Liveness).
"/9j/4AAQSkZJR..."Process successfully created.
Process ID.
"80371b2a-3ac7-432e-866d-57fe37896ac6"Process status. Possible values: '1' - In processing; '4' - Canceled (e.g., timeout); '5' - Error.
1Information about identity verification.
Identity verification result. Possible values: 'yes' - CPF holder's face; 'no' - Not the CPF holder's face; 'inconclusive' - Unable to confirm if it is the CPF holder's face.
"inconclusive"Liveness result. Possible values: '1' - Liveness approved; '2' - Liveness rejected.
1Endpoint to get the result of a process for Liveness + Identity Verification + Behavior Alert in by Client.
Process ID.
Valid access token.
Valid APIKEY with Liveness + Identity Verification + Behavior Alert capabilities enabled.
Process information successfully retrieved.
Process ID.
"2b034568-dfaf-463f-94fb-18ed93c312e8"Process status. Possible values: '1' - In processing; '3' - Completed; '4' - Canceled (e.g., timeout); '5' - Error.
3Information about identity verification.
Identity verification result. Possible values: 'yes' - CPF holder's face; 'no' - Not the CPF holder's face; 'inconclusive' - Unable to confirm if it is the CPF holder's face.
"inconclusive"Liveness result. Possible values: '1' - Liveness approved; '2' - Liveness rejected.
1Information about Behavior Alert.
Behavior Alert result. Possible values: 'yes' - The face has been involved in a fraudulent identity transaction; 'inconclusive' - No indication that the face has been involved in a fraudulent identity transaction.
"inconclusive"