curl --request POST \
--url https://{environment-subdomain}.idmetagroup.com/api/v3/verifications/biometrics-verification-passthrough \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD..."
}
'{
"success": true,
"message": "Biometrics verification processed successfully",
"data": {
"livenessPass": true,
"livenessScore": 98.12
},
"verificationStatus": "VERIFIED",
"verificationStatusCode": 3,
"transactionId": "9d4f2b18-6c31-4e75-8a90-2f1b7c3e5d60",
"verificationType": "biometrics_verification",
"metadata": {
"customerReference": "CUST-10294"
},
"createdAt": "2026-09-14 04:12:37+0000"
}Biometrics Verification
Run a face liveness check on a selfie
curl --request POST \
--url https://{environment-subdomain}.idmetagroup.com/api/v3/verifications/biometrics-verification-passthrough \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD..."
}
'{
"success": true,
"message": "Biometrics verification processed successfully",
"data": {
"livenessPass": true,
"livenessScore": 98.12
},
"verificationStatus": "VERIFIED",
"verificationStatusCode": 3,
"transactionId": "9d4f2b18-6c31-4e75-8a90-2f1b7c3e5d60",
"verificationType": "biometrics_verification",
"metadata": {
"customerReference": "CUST-10294"
},
"createdAt": "2026-09-14 04:12:37+0000"
}livenessThreshold.
This endpoint runs liveness only. It does not screen for duplicates or blacklists, and it does not compare two faces.
| If you need | Use |
|---|---|
| Duplicate or blacklist screening | Biometrics Detection |
| Whether two faces belong to the same person | Biometrics Face Compare |
Authorizations
Use your API token as a Bearer token in the Authorization header.
Headers
"Bearer {your_api_token}"
Body
Base64 data URI (for example data:image/jpeg;base64,...), or a multipart file upload when posting multipart/form-data.
Minimum liveness confidence as a percentage (0–100), on the same scale as livenessScore. livenessPass is true and verificationStatus is VERIFIED when the score is greater than or equal to this value. May only tighten the result, never loosen it.
0 <= x <= 100Free-form correlation data, echoed back on the response.
Response
Liveness completed. Passed, rejected, and review-needed outcomes all use HTTP 200 when the engine returns a liveness verdict.
true
Biometrics verification successful when liveness passed; Biometrics verification rejected when liveness failed.
Show child attributes
Show child attributes
Liveness verdict.
VERIFIED, REVIEW_NEEDED, REJECTED 3 = Verified, 2 = Review Needed, 1 = Rejected.
3, 2, 1 "biometrics_verification"
"2026-09-14 04:12:37+0000"