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*
Send image with image URL - Endpoint Features
| 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'
| 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 like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). 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 paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
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.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the ‘X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The ‘X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
58%
Response Time:
474ms
Service Level:
100%
Response Time:
334ms
Service Level:
100%
Response Time:
6,046ms
Service Level:
100%
Response Time:
4,800ms
Service Level:
93%
Response Time:
1,024ms
Service Level:
100%
Response Time:
3,942ms
Service Level:
100%
Response Time:
1,726ms
Service Level:
100%
Response Time:
1,527ms
Service Level:
100%
Response Time:
3,121ms
Service Level:
100%
Response Time:
0ms
Service Level:
89%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,627ms
Service Level:
100%
Response Time:
2,528ms
Service Level:
98%
Response Time:
0ms
Service Level:
100%
Response Time:
744ms
Service Level:
100%
Response Time:
1,437ms
