Our Facial Landmarks Detection API provides an advanced solution for detecting and analyzing facial landmarks with high precision. This API supports the detection of 72, 150, and 201 key points, covering essential facial features such as eyes, eyebrows, lips, and nose contours. Additionally, it offers precise localization of facial features, including eyebrows, eyes, nose, mouth, and cheeks, as well as accurate identification of facial contours for both single and multiple faces. The API also includes face angle estimation, allowing for the determination of various facial poses in the image. Ideal for developers in the fields of photography, augmented reality, and biometric security, this API enables enhanced facial recognition and image processing capabilities. Integrate our Facial Landmarks Detection API into your application to provide users with robust and precise facial analysis tools, improving the accuracy and functionality of your facial recognition and image editing solutions.
Accurately detect and analyze facial landmarks with our Facial Landmarks Detection API, supporting up to 201 key points for precise facial feature and contour identification.
Field | Required | Type | Scope | Defaults | Example | Description |
---|---|---|---|---|---|---|
image |
YES | file |
||||
max_face_num |
NO | integer |
|
1 | The maximum number of faces to process. The default value is 1 (only the face with the largest area in the image is detected). |
|
face_field |
NO | string |
|
age,gender,landmark4 |
Returns more information about the face (by default only face_token, face frame, probability and rotation angle are returned).
|
Viewing Public Parameters and Error Codes
Field | Type | Scope | Description |
---|---|---|---|
result |
object |
The content of the result data returned. | |
+face_num |
integer |
The number of faces in the picture. | |
+face_list |
array |
List of face information. | |
++face_token |
string |
Face Token. | |
++location |
object |
The position of the face in the picture. | |
+++left |
float |
The distance of the face area from the left border. | |
+++top |
float |
The distance of the face area from the upper boundary. | |
+++width |
float |
The width of the face area. | |
+++height |
float |
The height of the face area. | |
+++rotation |
integer |
[-180, 180] | The clockwise rotation angle of the face frame with respect to the vertical direction. |
++face_probability |
float |
[0, 1] | Face confidence. |
++angle |
object |
Face rotation parameters, refer to Face Spatial Pose Angle Reference for detailed description. | |
+++yaw |
float |
[-90, 90] | The left and right rotation angle of 3D rotation. |
+++pitch |
float |
[-90, 90] | Three-dimensional rotation of the pitch angle. |
+++roll |
float |
[-180, 180] | In-plane rotation angle. |
++age |
float |
Age. | |
++gender |
object |
Gender information. | |
+++type |
string |
|
|
+++probability |
float |
[0, 1] | Gender confidence. |
++landmark4 |
array |
4 feature points. | |
++landmark72 |
array |
72 feature points. Refer to 72 feature points for details. | |
++landmark150 |
object |
150 feature points. Refer to 150 feature points for details. | |
++landmark201 |
object |
201 feature points. Refer to 201 feature points for details. |
Facial Landmarks - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] File Binary |
{
"request_id": "",
"log_id": "",
"error_code": 0,
"error_code_str": "",
"error_msg": "",
"error_detail": {
"status_code": 200,
"code": "",
"code_message": "",
"message": ""
},
"result": {
"face_num": "",
"face_list": [
{
"face_token": "",
"location": {
"left": 0,
"top": 0,
"width": 0,
"height": 0,
"rotation": 0
}
}
],
"face_probability": 0,
"angle": [
{
"yaw": 0,
"pitch": 0,
"roll": 0
}
],
"age": 0,
"gender": [
{
"type": "",
"probability": 0
}
],
"landmark4": [],
"landmark72": [],
"landmark150": {},
"landmark201": {}
}
}
curl --location 'https://zylalabs.com/api/4439/facial+landmarks+api/5452/facial+landmarks' \
--header 'Content-Type: application/json' \
--form 'image=@"FILE_PATH"'
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.
Our Facial Landmarks Detection API provides an advanced solution for detecting and analyzing facial landmarks with high precision. This API supports the detection of 72, 150, and 201 key points, covering essential facial features such as eyes, eyebrows, lips, and nose contours. Additionally, it offers precise localization of facial features, including eyebrows, eyes, nose, mouth, and cheeks, as well as accurate identification of facial contours for both single and multiple faces. The API also includes face angle estimation, allowing for the determination of various facial poses in the image.
Facial Recognition: Enhancing the accuracy of facial recognition systems by identifying key facial features. Animation and Gaming: Creating realistic facial animations by mapping facial landmarks for character models. Augmented Reality (AR): Enabling AR applications to accurately place virtual elements on usersβ faces, such as filters and masks. Beauty and Cosmetics: Powering virtual makeup and beauty apps to apply cosmetics accurately on facial features. Photography and Videography: Improving facial detection for better focusing and exposure settings in cameras.
High Precision: Provides accurate identification of key facial features, enhancing the effectiveness of applications relying on facial analysis. Real-Time Processing: Capable of identifying facial landmarks in real time, making it suitable for live applications such as AR and security monitoring. Versatility: Applicable to various fields, including facial recognition, animation, AR, medical diagnostics, beauty, photography, security, and human-computer interaction. Consistency: Delivers reliable and consistent results across different faces and conditions.
Yes, we do have more detailed [API documentation](https://www.ailabtools.com/doc/ai-portrait/analysis/face-key-points/api-marketplace) available. You can access it on our website or by contacting our support team for assistance.
Computer Vision Researchers and Engineers: Professionals and academics who work on developing facial recognition systems, emotion detection algorithms, and other applications requiring precise facial landmark localization. Augmented Reality (AR) and Virtual Reality (VR) Developers: Individuals creating immersive experiences that involve facial tracking and interaction. Healthcare Practitioners and Researchers: Those studying facial anatomy for medical diagnosis, facial reconstruction, or facial expression analysis in psychological research. Digital Artists and Animators: Creators who use facial landmarks for character animation, facial morphing, and other visual effects.
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:
3,271ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
908ms
Service Level:
100%
Response Time:
8,904ms
Service Level:
100%
Response Time:
6,046ms
Service Level:
100%
Response Time:
334ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
744ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
3,942ms
Service Level:
100%
Response Time:
0ms
Service Level:
98%
Response Time:
0ms
Service Level:
100%
Response Time:
4,800ms
Service Level:
100%
Response Time:
2,218ms
Service Level:
100%
Response Time:
0ms