PresentID Photo ID matching API evaluates whether two faces belong to the same person or not. Face verification ensures a one-to-one (1:1) match of a face image captured at the time of onboarding with an image captured from a trusted credential such as a driver’s license, or a passport.
We have created a very deep convolutional neural network to extract very high-level features from a face for each person. We have provided a large-scale image database of faces from many sources e.g. web crowdsourcing, our built-in house dataset. There is a lot of diversity of races in the database. Our model inference time is 115ms on Intel CPU corei7 6700k. Especially in our solution, we save some frames that come from client SDK that is selected based on our own algorithm. This feature makes our matching stronger. Moreover, we save a checksum from a video to check duplicated videos.
Our method has got promising results under large appearance variations e.g. pose, age gaps, skin, glass, makeup, and beard.
**Input:**
- Image URL link
**Output:**
- Result index
- Image specs
- Similar percent
- Result message
**Features:**
- Less than 1second.
- Accuracy is %99.76 on the LFW face verification dataset, a very popular benchmark.
- Support IOS, Android, Windows, and Mac devices.
- The smallest faces are detected (50px * 50px).
- Easy integration with your app.
**Use Cases:**
- Access Control
- Onboarding
- Fintech
- Car sharing & Taxi
- Online Brokers
- Health Care
- Dating Apps
- Customer Support
**Rules & Restrictions:**
- Send data via an image URL.
- Image size should not exceed 8 MB.
- Also, the images should not be larger than 5000 pixels and smaller than 50 pixels.
Face verification API(photo id matching) evaluates whether two faces belong to the same person or not.
*Image size should not exceed 8 MB*
*Also, the images should not be larger than 5000 pixels and smaller than 50 pixels*
| Object | Description |
|---|---|
linkFile1 |
[Required] |
linkFile2 |
[Required] |
Continue with Google
Continue with Github
{
"statusCode": 200,
"statusMessage": "OK",
"hasError": false,
"data": {
"resultIndex": 3,
"resultMessage": "The two faces belong to the different people.",
"similarPercent": 0.5538576119399039
},
"imageSpecs": [
{
"leftTop": {
"isEmpty": false,
"x": 452,
"y": 107
},
"rightTop": {
"isEmpty": false,
"x": 276,
"y": 110
},
"rightBottom": {
"isEmpty": false,
"x": 279,
"y": 286
},
"leftBottom": {
"isEmpty": false,
"x": 455,
"y": 283
}
},
{
"leftTop": {
"isEmpty": false,
"x": 953,
"y": 172
},
"rightTop": {
"isEmpty": false,
"x": 329,
"y": 248
},
"rightBottom": {
"isEmpty": false,
"x": 405,
"y": 872
},
"leftBottom": {
"isEmpty": false,
"x": 1029,
"y": 796
}
}
]
}
curl --location --request POST 'https://zylalabs.com/api/4005/face+verification+api/4788/send+image+with+image+url?linkFile1=https://i.ds.at/PKrIXQ/rs:fill:750:0/plain/2022/11/08/Jordan-StraussInvisionAP.jpg&linkFile2=https://m.media-amazon.com/images/M/MV5BMTc3MzY3MjQ3OV5BMl5BanBnXkFtZTcwODI3NjQxMw@@._V1_.jpg' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Face Verification API REST API, simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
The PresentID Face Verification API is designed to confirm whether two facial images belong to the same individual. This is particularly useful for identity verification processes, such as confirming the match between a person and their photo ID in security checks and registration processes.
To use the API, submit two images via a POST request—one of a person's face and another from a photo ID. The API compares several facial features and structures between the two images, using advanced algorithms to analyze and determine the likelihood that the faces are the same. It then provides a similarity score or a binary result indicating a match or non-match.
The API supports several popular image formats, including JPEG, PNG, and BMP. Ensure that both images are of high quality and that the faces are clearly visible without obstructions for optimal results.
Yes, the API has usage limitations that depend on the user's subscription plan. These may include restrictions on the image file size and the number of verification requests per day or month. Detailed limitations are available on our pricing page or within your user dashboard.
Users might face several common errors: 400 Bad Request: This error can occur if the images are too large, of poor quality, or in an incorrect format. Check to ensure your images meet the API specifications. 401 Unauthorized: Occurs if the API key is missing, invalid, or expired. Verify that your API key is correctly applied to your requests. 429 Too Many Requests: Indicates exceeding the API usage limits according to your subscription plan. Consider adjusting your usage or upgrading your plan.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
1,374ms
Service Level:
100%
Response Time:
801ms
Service Level:
100%
Response Time:
6,321ms
Service Level:
100%
Response Time:
359ms
Service Level:
100%
Response Time:
331ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
4,212ms
Service Level:
100%
Response Time:
2,183ms
Service Level:
100%
Response Time:
3,942ms
Service Level:
100%
Response Time:
5,125ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
80%
Response Time:
0ms
Service Level:
100%
Response Time:
1,527ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
3,121ms
Service Level:
100%
Response Time:
0ms
