Authenticate Facial
Service that performs facial validation between two faces, including both open images and biometric templates.
This service can be used to perform the following validations:
Facial authentication between two open images, generated or not by FacePhi Widgets.
Facial authentication between two biometric templates, requires Integration of the FacePhi Selphi Mobile or Web Widget.
Facial authentication between an open image and a biometric template, requires Integration of the FacePhi Selphi Mobile or Web Widget.
Facial authentication between the face present in the identity document photo (TokenFaceImage) and a open image, requires Integration of the FacePhi SelphID Mobile Widget.
Facial authentication between the face present in the identity document photo (TokenFaceImage) and a biometric template, requires Integration of the FacePhi Selphi Mobile and SelphID Mobile Widgets.
Integration
For the type 4 and 5 validations, the implementation of the SelphID Mobile Widget is required to generate the property TokenFaceImage.
For the type 2, 3 and 5 validations, the implementation of the Selphi Mobile or Web Widget is required to generate the biometric template property (TemplateRaw).
Endpoint
POST /services/authenticateFacialHeaders
x-api-key
string
Yes
Access authorization API key.
family
string
No
Value: Onboarding. Required with the tracking service.
All calls to the Endpoints for Tracking with Identity Platform must contain the header family.
Request body
Content-Type: application/json
Parameters
token1
string
Yes
Image used as reference for facial comparison. Depending on the invoked method, it can be the token generated by the SelphID Widgets (document photo token), an open image, or a tokenized biometric template.
token2
string
Yes
Image used for the comparison. It can be an open image or a tokenized biometric template.
tracking
object
No
Object that represents the necessary tracking information.
tracking.extraData
string
No
Token generated by the Mobile/Web SDK. Contains tokenized tracking information with the Platform.
tracking.operationId
string
No
Operation identifier generated by the Mobile/Web SDK.
Method Specification
1
Facial authentication using open images
token1: Base64, token2: Base64
2
Facial authentication using biometric templates
token1: templateRaw, token2: templateRaw
3
Facial authentication using an open image and a biometric template
token1: Base64, token2: templateRaw
4
Facial authentication using the token generated by cropping the document photo and an open image
token1: tokenFaceImage, token2: Base64
5
Facial authentication using the token generated by cropping the document photo and a biometric template
token1: tokenFaceImage, token2: templateRaw
Request example
Responses
200 Success
Response parameters
serviceResultCode
integer
Code indicating the overall result of service execution. See Service Result Code
serviceResultLog
string
Descriptive field of the service execution result. Includes details when there is an error or exception in the module.
serviceTime
string
Total processing time (milliseconds).
serviceTransactionId
string
Transaction identifier associated with the request processed by the API.
serviceFacialAuthenticationHash
string
Integrity hash of the biometric template used in a positive or uncertain facial authentication. Only applicable in methods 2, 3 and 5.
serviceFacialAuthenticationResult
integer
Code indicating the facial matching result. See Service Facial Authentication Result
serviceFacialSimilarityResult
number
Value indicating the facial similarity between the face in the identity document photo and the selfie taken by the user. 1.0 = 100%
Service Result Code
The serviceResultCode indicates the overall result of the service execution:
0
The service execution was successful, the module processed the request correctly.
200
Service Facial Authentication Result
The serviceFacialAuthenticationResult indicates the result of the facial matching operations:
0
NONE
Facial verification could not be performed.
1
NEGATIVE
The process was executed correctly. The facial pattern comparison of the faces does not match.
3
POSITIVE
The process was executed correctly. The facial pattern comparison of the faces is positive. The value of serviceFacialSimilarityResult indicates the % of similarity between the compared images.
4
NONE BECAUSE POSE EXCEED
Facial verification could not be performed due to the position of the face.
5
NONE BECAUSE INVALID EXTRACTIONS
Facial verification could not be performed due to problems extracting the facial pattern.
Response example: Positive
Response example: Negative
400 Bad Request
401 Unauthorized
403 Forbidden
502 Bad Gateway
504 Gateway Timeout
Last updated