Liveness API

The ezto verify liveness API enables to automate liveness detection and verification processes directly from their systems through secure, developer-friendly interfaces

Base URL

Path Params

Headers

Request Body

Below is the request body structure for the Liveness endpoint

requestedVerificationstringRequired

client_idstringRequired

metadatastringRequired

video_filefileRequired

expectedstringRequired

hook_urlstringRequired

auth_tokenstring

Sample Request Body

{
    "client_id": "{{client_id}}",
    "requestedVerification": "liveness",
    "video_file" : "{{video file}}",
    "metadata": {
        "blink": {
        "video": {
            "start": 2.93218,
            "end": 3.43198
        }
        },
        "movement": {
        "video": {
            "start": 7.5299700000000005,
            "end": 9.52958
        }
        },
        "fingerCount": {
        "video": {
            "start": 2.39886,
            "end": 3.39886
        }
        },
        "speech": {
        "video": {
            "start": 3.4653,
            "end": 8.49665
        }
        }
    },
    "expected": {
        "fingerCount": {
        "enabled": true,
        "expected": 5
        },
        "blink": {
        "enabled": true,
        "expected": 2
        },
        "speech": {
        "enabled": true,
        "expected": "Hat"
        },
        "movement": {
        "enabled": true
        }
    },
    "hook_url": "https://webhook.site"
}

Response Body

Here is the response body and response sample for the "requestedVerification":"liveness"

bodystring

HTTP STATUS CODE SUMMARY
200	OK	Successfully done.
201	OK	Successfully created.
400	Bad Request	The request was unacceptable, often due to missing a required parameter.
401	Unauthorized	Unauthorized access try with correct access.
402	Request Failed	The parameters were valid but the request failed.
403	Forbidden	The Application doesn't have permissions to perform the request.
404	Not Found	The requested resource doesn't exist.
500	Server Errors	Something went wrong on ezto verify's end. (These are rare.)
503	Server Errors	Service temporarily unavailable.

Loading...