Know Your Customer
Liveliness
Face Match
introduction face match api is used to ensure that two images belong to same person/individual in this we need to either upload two images or give urls of two images to match ,as input to the api you can also provide a optional threshold value between 0 05 0 95 to decide which match is false or true if match percentage is greater than or equal to threshold then true otherwise false it compares two images and gives the ratio of matching between them and matchpercentage between them in response, it gives three things as mentioned below verified true or false a message that says whether the verification completed with positive result or negative result a matchpercentage to signify the percentage of match between the two given images face mask detection signzy is one of the first movers in the industry to develop its proprietary face mask detection solutions which detects if a user is wearing a mask or not during a remote unassisted onboarding use case it works with our current face match solution and makes gtm faster for our current clientele the user flow for face mask detection consists of the following steps end customer provides a selfie client sends the selfie image to signzy signzy detects the mask on the face of the user by identifying facial landmarks on the face signzy provides the response to the client that the user is wearing a mask or not with confidence score given below are the features of face mask detection that are worth noting accuracy is more than 98% platform agnostic as we provide restful api faster response time i e less than 3 seconds secure data storage & purging policy jpg & png images are supported max image size supported is 7 mb how to call the api you must first login before sending the request the authorization header in the request must include the access token obtained from the login api call api input guidelines both firstimage url and secondimage url are mandatory parameters sample curl production curl location request post 'https //api signzy app/api/v3/internals/facematch/facematches' \\ \ header 'content type application/json' \\ \ header 'authorization \<token>' \\ \ data raw '{ "firstimage" "\<url of image 1>", "secondimage" "\<url of image 2", "detectmask" \[ "\<image 1 url>", ] }' preproduction curl location request post 'https //api preproduction signzy app/api/v3/internals/facematch/facematches' \\ \ header 'content type application/json' \\ \ header 'authorization \<token>' \\ \ data raw '{ "firstimage" "\<url of image 1>", "secondimage" "\<url of image 2", "detectmask" \[ "\<image 1 url", "\<image 2 url" ] }' input parameters 207,243,293 false true unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type false unhandled content type false unhandled content type false unhandled content type sample response json { "firstimage" "\<first image url>", "secondimage" "\<second image url>", "detectmask" \[ "\<masked image url>" ], "facematchprovider" "aws", "id" 16, "result" { "verified" false, "message" "verification completed with negative result", "matchpercentage" "0 00%" } } response parameters 208,565 false true left unhandled content type left unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left false unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type status codes false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at help\@signzy com