FaceFace Liveness Check

Face Liveness Detection — Anti-Spoofing Check

Detect if a face image is a real person or a spoof attempt (photo, screen, mask). Passive liveness check — no user action required.

curl -X POST "https://production.deepvue.tech/v1/liveness-check" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN (JWT)" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
  "image": "example_string"
}'
{
  "code": 200,
  "timestamp": null,
  "transaction_id": "string",
  "sub_code": "SUCCESS",
  "message": "Request processed successfully",
  "data": {
    "is_live": true,
    "score": null
  }
}
POST
/v1/liveness-check
POST
Bearer Token (JWT)
Bearer Tokenstring
Required

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
API Key (header: x-api-key)
x-api-keystring
Required

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Content-Typestring
Required

The media type of the request body

Options: application/json
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token (JWT). ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

header
x-api-keystring
Required

API Key for authentication. The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

Body

application/json

Responses

codeinteger
timestampinteger
transaction_idstring
sub_codestring
messagestring
dataobject

Overview

Liveness Check is a process of verifying that a real person is present and not a photo or video. It is a critical step in the KYC process. This API employs passive liveness detection, analyzing a user-provided selfie or image to determine authenticity without requiring active user participation.

The API accepts image data either as a URL or as a base64-encoded string within the request body. Successful requests return confirmation that a live face was detected with an is_live boolean flag, or notification that no face was detected in the submitted image.