Skip to main content

Face Match (1:1)

Within FACIA, the Face Match service takes center stage as a dynamic endpoint, propelling transaction requests into the realm of facial matching algorithms. This innovative algorithm meticulously evaluates the likeness between a Selfie (Photo) and either a Document or another Selfie (Photo), adopting a seamless 1:1 matching approach.

Create Face Match Transaction

This endpoint initiates a transaction request for the face match algorithm, serving as a 1:1 service. The endpoint accepts three fields in the request payload, as mentioned in the request parameters.

Endpoint

POSThttps://api.facia.ai/face-match

Authorization:

Token Type: Bearer
Description:

This API utilizes Access token or Client-Secret key in header for authentication.

You can use your client_id and client_secret key when using the "/request-access-token" endpoint to obtain a Bearer token for authorization while connecting to this API. For additional details on Authorization, click Here

Run in Postman

Request Body Samples:

//POST /face-match  HTTP/1.1
//Host: https://api.facia.ai
//Content-Type: application/json
//client-secret: <your client_secret key>

{
"type": "photo_id_match",
"face_frame": "file.jpg",
"id_frame": "file.jpg",
"client_reference": "QWERTY12345",
"allow_override": 0,
"enroll_face":true
}

Request Parameter

ParametersDescription
type Required: Yes
Type: string
Example: type=photo_id_match
The type must be "photo_id_match".
face_frame Required: Yes
Type: file
Example: face_frame=file
File must be of type .jpeg, .jpg or .png.
id_frame Required: Yes
Type: file
Example: id_frame=file
File must be of type .jpeg, .jpg or .png.
client_reference Required: No
Type: string
Minimum: 5 characters
Maximum: 255 characters
Example: client_reference="QWERTY12345"
Required if allow_override field set to 1.
allow_override Required: No
Type: boolean
Default value: 0
Accepted values: 0,1
The client reference is mandatory if the value of the override key is set as 1. The override key allow the system to replace the latest previous image with the new one against the specified reference number of the client’s reference.
enroll_face
Required: No
Type: boolean
Example: enroll_face=true
Default value: true
If you do not want the system to enroll the face then set the value of the key as false.

Response Sample


{
"status": true,
"message": "Transaction Created",
"result": {
"data": {
"reference_id": "W4437KIWN0KDM13",
"similarity_status": "1",
"similarity_score": "0.98",
"client_reference": "QWERTY12345"
}
}
}


Response Parameter

ParametersDescription
reference_id Type: string
Example: reference_id=W4437KIWN0KDM13
The unique identifier associated with the created transaction.
similarity_status Type: string
Example: similarity_status=1
1 means matched and 0 means not matched.
similarity_score Type: string
Example: similarity_score=0.98
Indicates the calculated similarity score of the images provided.
client_reference Type: string
Example: client_reference=QWERTY12345
Contains the unique ID defined for the end user.