The Face Recognition API allows you to send an image and receive detailed information about the objects detected, including their exact location using coordinates (x, y, width, height) and key points (landmarks) that describe specific characteristics of the object, such as facial features, body joints, or relevant object details.
Thanks to state-of-the-art detection and segmentation algorithms, the API accurately identifies each object within the image and calculates its landmarks, enabling applications such as motion tracking, facial recognition, pose analysis, augmented reality, smart editors, and security systems. Each response includes an operation status, a message, and an array of results with absolute coordinates, ensuring that developers can immediately integrate the information into their applications.
The API is designed to support images in various formats and resolutions, ensuring consistency and accuracy in the results.
In short, the Face Recognition API offers a comprehensive solution for any project that requires image analysis with precise coordinates and key points. Whether for facial recognition, motion tracking, pose analysis, augmented reality, or advanced computer vision, this API delivers fast, consistent, and highly accurate results, facilitating the development of intelligent and visually advanced applications.
Receives an image and returns coordinates, facilitating face detection.
Face Detection - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"status": 0, "message": "", "result": [{"x": 96, "y": 48, "w": 79, "h": 79, "landmark": [{"x": 99, "y": 76}, {"x": 99, "y": 86}, {"x": 100, "y": 96}, {"x": 102, "y": 105}, {"x": 105, "y": 114}, {"x": 111, "y": 121}, {"x": 119, "y": 127}, {"x": 125, "y": 132}, {"x": 133, "y": 134}, {"x": 140, "y": 133}, {"x": 146, "y": 127}, {"x": 152, "y": 121}, {"x": 157, "y": 114}, {"x": 161, "y": 107}, {"x": 163, "y": 99}, {"x": 164, "y": 91}, {"x": 165, "y": 83}, {"x": 109, "y": 77}, {"x": 113, "y": 71}, {"x": 120, "y": 69}, {"x": 127, "y": 71}, {"x": 134, "y": 74}, {"x": 143, "y": 75}, {"x": 149, "y": 73}, {"x": 155, "y": 73}, {"x": 161, "y": 75}, {"x": 162, "y": 81}, {"x": 139, "y": 79}, {"x": 139, "y": 85}, {"x": 139, "y": 90}, {"x": 139, "y": 96}, {"x": 130, "y": 98}, {"x": 133, "y": 100}, {"x": 137, "y": 102}, {"x": 141, "y": 101}, {"x": 144, "y": 99}, {"x": 117, "y": 79}, {"x": 121, "y": 77}, {"x": 125, "y": 77}, {"x": 128, "y": 80}, {"x": 124, "y": 80}, {"x": 121, "y": 79}, {"x": 145, "y": 81}, {"x": 149, "y": 79}, {"x": 153, "y": 80}, {"x": 156, "y": 82}, {"x": 152, "y": 82}, {"x": 149, "y": 82}, {"x": 119, "y": 107}, {"x": 125, "y": 106}, {"x": 132, "y": 106}, {"x": 136, "y": 108}, {"x": 139, "y": 107}, {"x": 144, "y": 107}, {"x": 148, "y": 109}, {"x": 143, "y": 115}, {"x": 139, "y": 118}, {"x": 135, "y": 118}, {"x": 130, "y": 118}, {"x": 124, "y": 114}, {"x": 121, "y": 107}, {"x": 132, "y": 108}, {"x": 135, "y": 108}, {"x": 139, "y": 108}, {"x": 146, "y": 109}, {"x": 139, "y": 114}, {"x": 135, "y": 115}, {"x": 131, "y": 114}]}]}
curl --location --request POST 'https://zylalabs.com/api/11323/face+recognition+api/21463/face+detection' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"url": "https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcT6Fo-gbghS19ipMBMeqD0HtEjHDnCHkIpfcg&s"
}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Face Detection endpoint returns data including the status of the operation, a message, and an array of detected faces. Each face entry contains coordinates (x, y, width, height) and landmarks that represent specific facial features.
The key fields in the response data include "status" (indicating success or failure), "message" (providing additional information), and "result" (an array of detected faces with their coordinates and landmarks).
The response data is structured as a JSON object. It includes a top-level object with "status," "message," and "result." The "result" field contains an array of objects, each representing a detected face with its coordinates and landmarks.
The Face Detection endpoint provides information on detected faces, including their bounding box coordinates (x, y, width, height) and detailed landmark coordinates that describe facial features.
The Face Detection endpoint accepts an image file as input. Users can customize their requests by specifying the image format and resolution, ensuring compatibility with the API's processing capabilities.
Users can utilize the returned data by extracting the coordinates and landmarks for each detected face. This information can be integrated into applications for facial recognition, tracking, or augmented reality features.
Data accuracy is maintained through the use of state-of-the-art detection and segmentation algorithms. Continuous updates and improvements to these algorithms help ensure high precision in object and landmark detection.
Typical use cases include facial recognition systems, motion tracking applications, pose analysis for fitness apps, augmented reality experiences, and security systems that require real-time face detection and analysis.
The Face Detection endpoint supports various image formats, including JPEG, PNG, and BMP. It can handle images of different resolutions, ensuring flexibility for developers to integrate the API into diverse applications.
Users can customize requests by specifying the image format and resolution. This allows for optimized processing based on the specific needs of their application, ensuring better performance and accuracy.
The "landmark" data in the response represents specific facial features, such as eyes, nose, and mouth positions. Each landmark is provided as coordinates, allowing for detailed analysis of facial expressions and orientations.
The "status" field indicates the success or failure of the request. A status of 0 typically means success, while any other value indicates an error, prompting users to check the accompanying "message" for details.
If the response contains no detected faces, users should check the input image quality and ensure it meets the API's requirements. Low resolution or poor lighting may affect detection accuracy.
Advanced applications include real-time facial recognition for security systems, emotion detection in marketing analytics, and interactive augmented reality experiences that respond to user expressions.
Users can ensure optimal results by providing high-quality images with good lighting and clear visibility of faces. Additionally, using images that conform to the supported formats and resolutions enhances detection accuracy.
The "message" field provides additional context about the operation's outcome. It may include error descriptions or confirmations of successful processing, helping users troubleshoot or validate their requests.
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, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
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 3,600, it means 3,600 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
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 free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
0ms
Service Level:
62%
Response Time:
737ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
4,650ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
436ms
Service Level:
100%
Response Time:
3,406ms
Service Level:
100%
Response Time:
1,170ms
Service Level:
59%
Response Time:
711ms
Service Level:
100%
Response Time:
1,770ms
Service Level:
100%
Response Time:
532ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,563ms
Service Level:
100%
Response Time:
6,988ms
Service Level:
100%
Response Time:
616ms