About the API:
Face liveness detection helps you uncover fraud by ensuring that the image you have been provided isn’t a picture of a picture, a passport-sized image, or an image of another individual on a cell phone/laptop screen. Pair it with the Face Comparison Validator API to have complete confidence that the selfie of the individual is indeed live, and belongs to the same individual as you expect.
This API will receive the image URL that you want to check its liveness. It will provide information like face quality, if the photo is live taken, and its position in the image.
Fraud detection: Face liveness detection helps you uncover fraud by ensuring that the image you have been provided isn’t a picture of a picture, a passport-sized image, or an image of another individual on a cell phone/laptop screen.
Check image properties: Be able to detect if any image is not following your requirements. Check if the face is too far from the camera if its quality is good or poor, and avoid your users to upload images that won't be useful for your platforms.
Receive images for biometric analysis: If you are using biometric analysis in your products, is important to receive images that are taken live from your users. This API will help you with that.
Besides the number of API calls per month, there are no other limitations.
{"request_id":"e4f38d25-822a-44cd-bc67-28abca87a4e9"}
curl --location --request POST 'https://zylalabs.com/api/322/face+liveness+check+api/259/check+liveness' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"task_id": "123",
"group_id": "123",
"data": {
"document1": "https://i0.wp.com/post.medicalnewstoday.com/wp-content/uploads/sites/3/2020/03/GettyImages-1092658864_hero-1024x575.jpg"
}
}'
[{"action":"check_photo_liveness","created_at":"2023-12-07T02:49:13+05:30","group_id":"123","request_id":"cbbc9300-88ba-46e2-bebe-ec024724802e","status":"in_progress","task_id":"123","type":"face"}]
curl --location --request GET 'https://zylalabs.com/api/322/face+liveness+check+api/260/get+results?request_id=d3dc6e39-a4fc-4d6d-88c8-4c23b9ddd360' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The POST Check Liveness endpoint returns a task ID upon submission of an image URL. The GET Get Results endpoint returns analysis data, including the status of the liveness check, creation timestamp, request ID, and task ID.
Key fields in the response include "status" (indicating the current state of the analysis), "request_id" (unique identifier for the request), "task_id" (identifier for tracking the task), and "created_at" (timestamp of when the request was made).
The response data is structured in JSON format. For the GET Results endpoint, it includes an array of objects, each containing fields like "action," "status," and identifiers, allowing users to track and interpret the results easily.
The POST Check Liveness endpoint provides a task ID for tracking, while the GET Get Results endpoint offers insights into face liveness, quality, and position, helping users assess the validity of the submitted image.
The primary parameter for the POST Check Liveness endpoint is the image URL. Users must ensure the URL points to a valid image file for accurate liveness checks.
Users can utilize the returned data by monitoring the "status" field to determine if the liveness check is complete. The "request_id" can be used to fetch results, while "task_id" helps in tracking specific tasks across multiple requests.
Data accuracy is maintained through advanced algorithms that analyze the image for signs of liveness, such as movement or depth, ensuring that the image is not a static representation or a photo of a photo.
Typical use cases include fraud detection in identity verification processes, ensuring compliance with biometric data requirements, and filtering out low-quality images before they are processed in applications.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
5,626ms
Service Level:
100%
Response Time:
904ms
Service Level:
100%
Response Time:
20,002ms
Service Level:
100%
Response Time:
20,002ms
Service Level:
98%
Response Time:
0ms
Service Level:
100%
Response Time:
20,002ms
Service Level:
100%
Response Time:
12,158ms
Service Level:
100%
Response Time:
465ms
Service Level:
89%
Response Time:
0ms
Service Level:
100%
Response Time:
20,003ms
Service Level:
100%
Response Time:
1,045ms
Service Level:
100%
Response Time:
565ms
Service Level:
100%
Response Time:
1,284ms
Service Level:
100%
Response Time:
686ms
Service Level:
98%
Response Time:
396ms
Service Level:
100%
Response Time:
1,953ms
Service Level:
100%
Response Time:
156ms
Service Level:
100%
Response Time:
10,129ms
Service Level:
100%
Response Time:
9,844ms
Service Level:
100%
Response Time:
2,612ms