Create an App Registration Biometric Validation
POST
https://api.verifik.co/v2/biometric-validations/app-registration
A Biometric Validation is an instance within Verifik's system that allows you to process and validate user identities through facial recognition and liveness detection during the onboarding process. This process ensures the authenticity of users by verifying their unique biometric characteristics through advanced security technology. This endpoint is specifically designed for users who are in the middle of an app registration flow.
Headers
Content-Type
application/json
Authorization
Bearer {YOUR_ACCESS_TOKEN}
The JWT Token you should use when creating App Registration Biometric Validations
is provided from the App Registration
in creation.
Body
image
string
Yes
Base64 encoded facial image that will be used for biometric validation and liveness detection.
os
string
Yes
Operating system of the device (e.g., "DESKTOP", "IOS", "ANDROID").
force
boolean
No
Optional flag to force creation even if a person already exists. Defaults to false.
Body Examples
Basic Biometric Validation
{
"image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQ...",
"os": "DESKTOP"
}
Advanced Biometric Validation with Force Flag
{
"image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQ...",
"os": "IOS",
"force": true
}
Request
curl -X POST https://api.verifik.co/v2/biometric-validations/app-registration \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQ...",
"os": "DESKTOP"
}'
Response
The response will contain information about the created biometric validation, including the app registration details, person information, and validation status.
{
"data": {
"_id": "674de8df21c72be3cc42b8a7",
"client": "507f1f77bcf86cd799439013",
"project": "507f1f77bcf86cd799439011",
"projectFlow": "507f1f77bcf86cd799439015",
"status": "STARTED",
"email": "[email protected]",
"countryCode": "+1",
"phone": "5551234567",
"biometricValidation": "674de8df21c72be3cc42b8a8",
"person": "674de8df21c72be3cc42b8a9",
"informationValidation": "674de8df21c72be3cc42b8a10",
"assignedCollection": "507f1f77bcf86cd799439016",
"createdAt": "2024-12-02T17:05:36.788Z",
"updatedAt": "2024-12-02T17:05:36.788Z"
}
}
Notes
App Registration Required: This endpoint requires an active app registration session with status "STARTED" or "ONGOING".
Liveness Detection: Advanced anti-spoofing technology ensures the person being verified is physically present.
Collection Integration: The project must have an assigned collection for biometric data storage.
Person Creation: A person record is automatically created and linked to the app registration.
Credit Charging: This endpoint automatically charges credits from your SmartEnroll plan.
Image Processing: Facial images are processed for both biometric matching and liveness detection.
Force Flag: Use the force flag to override existing person records if needed.
Onboarding Flow Integration
This validation endpoint is part of the larger onboarding flow where:
User creates an app registration
User completes information validation
Biometric validation is initiated with facial image
Liveness detection and facial recognition are performed
Person record is created and linked
User can proceed to the next step in the onboarding process
Liveness Configuration
The system uses the following default liveness settings from the project flow:
Liveness Minimum Score: 0.6 (60% confidence)
Search Mode: ACCURATE
Search Minimum Score: 0.9 (90% confidence)
These settings can be customized in your project flow configuration.
Common Use Cases
User Registration: Verify identity during account creation with biometric data
KYC Processes: Comprehensive identity verification for compliance
Onboarding Security: Ensure users are who they claim to be
Fraud Prevention: Advanced liveness detection prevents spoofing attacks
This endpoint is specifically designed for onboarding-type biometric validations. For general validation or login flows, use the standard biometric validation endpoint instead.
Last updated
Was this helpful?