The ZOLOZ Face Capture checkresult API is used to request a result about the face capture process results. This API is idempotent.
Required. A unique business ID for tracing purpose. For example，the sequence ID from the merchant's business-related database.
Note: The ZOLOZ server does not perform uniqueness check on the value of this field. For better tracking, it is strongly recommended to enable the merchant server to guarantee the uniqueness of the business ID.
Required. The unique transaction ID that is returned in the response of the initialize API.
Required. The API request result, which contains information about the result of the API request, such as status and error codes.
Detailed face capture information. Refer to the table below for details.
Optional. Detailed information about face capture. This field is only available when the value of the result.resultCode field is set to
Result process logic
For different request results, different actions are to be performed. See the following for details:
- If the value of the result.resultCode is
SUCCESS, the ZOLOZ Face Capture checkresult API is invoked successfully, and results about face capture are returned.
- Otherwise, the invocation of the ZOLOZ Face Capture checkresult API fails. Check the error code and message for more information about the possible reasons.
Common error codes
For the full list of common error codes, see the Common error codes section in the Error handling topic.
API-specific error codes
The following table shows the possible error codes that are specific for the Face Capture checkresult API.
Process is still ongoing, waiting for a face image to be uploaded.
Input parameters are invalid. For more information about which parameters, check the result message or the related log.
The meta information that is returned from the ZOLOZ SDK does not pass the usability check, which indicates the user cannot use the face capture function.
Other internal errors. For more information about the error details, check the result message that is returned and the related log.
The following sample shows what a request that the merchant server sends looks like.
The following sample shows what a response that the ZOLOZ server returns looks like.
The following table shows the fields that can be specified in the ExtInfo data model.
Optional. The captured face image, which is encoded in base64.
Optional. Specifies whether the captured face image is detected as a fake face attack by using the face liveness check algorithm. If the image is not a fake face attack, the value of
Optional. The coordinate data of the face image, for exmaple:
Optional. The quality score of the image. The value of this field is in the range of 0-100.