/Liveliness API

Enables businesses to verify if a person is a real human being and not a fraudster

Base URL

sdkbio.faceki.com

Liveliness End Point API

https://sdkbio.faceki.com/liveness

The Liveliness API is a key feature of FACEKI Biometric Authentication solution that enables businesses to verify if a person is a real human being and not a fraudster using photos or videos. The API uses advanced facial recognition technology to detect and analyze various features of a person's face to determine if they are a live human being or not.

With the Liveliness API, businesses can be confident that they are protecting themselves and their customers from identity theft and fraud. The API works by requiring the user to perform a simple task, such as blinking their eyes, nodding their head, or moving their lips. This ensures that the user is a real person and not a bot or fraudster trying to spoof the system.

The Liveliness API is available in both on-premises and cloud solutions, and it can be integrated into a variety of applications, including mobile apps and websites. It is also available in multiple programming languages, making it easy for developers to integrate into their existing applications.

To use the Liveliness API, businesses simply need to send a request to the API with the user's photo or video. The API will then analyze the image or video to determine if the user is a live human being or not. The API will return a response with a confidence score indicating the likelihood that the user is a live human being.

The Liveliness API is an essential tool for any business that needs to verify the identity of their customers or users. It is fast, reliable, and easy to use, and it provides an added layer of security that can help businesses protect themselves and their customers from fraud and identity theft.

Method: POST

Authorization: Bearer Token

Parameter:

image (Image File) (*Mandatory)

Image data is the file type of PNG, JPEG, PNG

POST https://sdkbio.faceki.com/liveness

Headers

Name	Type	Description
Content-Type:*	String	multipart/form-data
authorization:*	String	Bearer [token]

Request Body

Name	Type	Description
image*	File

200: OK

{
    "responseCode": 0,
    "data": {
        "face_id": "a5383cb2-a464-432d-916b-bb16dee9fcd4",
        "image_id": "117a3ce7-6b6c-346d-aa28-71afe66a2d98",
        "message": "Face is registered to client profile successfully"
    }
}

401: Unauthorized

Error:- 
    "error": "Authentication failed"

400: Bad Request

{
    "status": false,
    "message": "Image is required",
    "statusCode": 422,
    "data": {}
}

400: Bad Request

{
    "status": false,
    "message": "name is required",
    "statusCode": 401,
    "data": {}
}

400: Bad Request

{
    "status": false,
    "message": "email is required",
    "statusCode": 401,
    "data": {}
}

400: Bad Request

{
    "status": false,
    "message": "Mobile number is required",
    "statusCode": 401,
    "data": {}}

Response Parameters

You must make all your requests to the API over HTTPS and TLS 1.2, with Server Name Indication enabled. Any requests made over HTTP will fail.

Responses return JSON with a consistent structure, except downloads.

// Content-Type: application/json