Web live detection API
Performs a face liveness detection on two images, see Face Liveness Detection.
To perform a live detection, exactly two live recorded images are required. These are sent to the quality-check where, among other things, the face detection is done. If the images are suitable, the live-detection is executed.
To perform a live detection with challenge-response, please use the LivenessDetection API or one of the methods
This API call requires Basic Authentication, i.e. you have to provide an HTTP authorization header using the authorization method Basic and the base64 encoded string
App-ID:App-Secret (therefore the transport is secured using TLS/SSL). To receive the necessary BWS WebAPI access data (
App-Secret) you have to register your application on the BWS Management Portal first. This requires a valid BWS subscription.
or using the application/x-www-form-urlencoded media type:
If all two provided images could be processed successfully, this method returns the OK HTTP status code (200) with simply
false in the body content, indicating whether the submitted images prove that they are recorded from a live person or not.
In case something goes wrong, an error HTTP status code is returned together with some additional information if available.
Response HTTP Status Codes
The call returns one of the standard HTTP status codes:
|200 OK||The response body simply says true or false, indicating whether the images prove that they are recorded from a live person or not.|
|400 Bad Request||Invalid samples have been uploaded or they could not be processed successfully, e.g. no face found, etc. The response body typically has a |
|401 Unauthorized||Basic Authentication is required.|
|415 Unsupported Media Type||You probably forgot to specify the media type, e. g. application/json.|
|500 Internal Server Error||A server side exception occurred. The content may contain a |