Skip to main content

Account Deduplication (1:N)

This service is designed to initiate a transaction request for a facial search algorithm. This algorithm is specifically tailored to detect whether a new image or account already exists in the database. The primary purpose of this service is to identify whether the account exists or not.

Create Face Search Transaction

This endpoint will initiate a transaction request and returns reference_id if the request includes proper authentication, and valid fields mentioned below in request parameter.

Endpoint

POSThttps://app.facia.ai/backend/api/transaction/create-transaction/face-deduplication

Authorization:

Token Type: Bearer
Description:

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

You may use your client_id and client_secret key while using "/get-access-token" endpoint in order to get a Bearer token for authorization, while connecting to this API. For further details about Authorization click Here

Request Body Samples:

// Method : POST

{
"type": "string",
"file": file
}

Request Parameter

ParametersDescription
type
Required: Yes
Type: string
Type must be face_search
Example: type=face_search
file
Required: Yes
Type: file
File must be of type .jpg or .png
Example: file=file

Response Sample


{
"status": true,
"message": "Success",
"result": {
"data": {
"reference_id": "W4437KIWN0KDM13"
}
}
}


Response Parameter

ParametersDescription
reference_idType: string
Example: reference_id=W4437KIWN0KDM13
messageType: string
Example: message=Success

Face Search Result

This endpoint accepts a single field in the body request payload; reference_id (String). Once the response has been finalised at the backend, this endpoint returns a face_search_response object with a multiple object ids of images with most similar features with the provided image. Failure to provide a valid reference_id will result in a 422 status code.

Endpoint

POSThttps://app.facia.ai/backend/api/transaction/face-duplication-result

Authorization:

Token Type: Bearer
Description:

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

You may use your client_id and client_secret key while using "/get-access-token" endpoint in order to get a Bearer token for authorization, while connecting to this API. For further details about Authorization click Here

Request Body Samples:

// Method : POST

{
"reference_id": "string"
}

Request Parameter

ParametersDescription
reference_id
required
Type: string
Example: reference_id=W4437KIWN0KDM13

Response Sample



{
"status": true,
"message": "Success",
"result": {
"data": {
"deleted_at": "64918c825b6bdfaa65024ffc",
"updated_at": "64918c825b6bdfaa65024ffc",
"account_exist": "true",
"face_found": "true"
}
}
}



Response Parameter

ParametersDescription
deleted_atType: string
Example: deleted_at=2023-06-21T11:26:53.496000Z
updated_atType: string
Example: updated_at=64918c825b6bdfaa65024ffc
account_existType: string
Example: account_exist=true
face_foundType: string
Example: face_found=true