Clothes Data Retrieval API designed to identify the dominant garment or category within an image. Unlike more complex solutions geared toward comprehensive outfit analysis, this API provides an accurate and straightforward answer to a single question: What type of garment visually dominates the image?
The API supports a wide variety of predefined categories, including top, t-shirt, sweatshirt, outerwear, vest, shorts, trousers, skirt, dress, hat, glasses, watch, belt, footwear, bag, and scarf.
It features two endpoints that allow for flexible image processing, either via URL or compatible inputs, adapting to different integration workflows. Its lightweight design and specific focus make it ideal for applications that require quick decisions without the need for in-depth analysis of multiple garments or attributes.
In summary, it is a practical, fast, and focused solution that allows you to detect the main category of a garment in an image, optimizing workflows and improving efficiency in applications related to fashion and visual content.
Identifies the dominant clothing category in an image, returning the primary garment type with a confidence level for fast tagging and filtering.
Classify Category - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"category":"sweatshirt","confidence":"high"}
curl --location --request POST 'https://zylalabs.com/api/12303/clothes+data+retrieval+api/23114/classify+category' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"image_url": "https://images.pexels.com/photos/6311392/pexels-photo-6311392.jpeg"}'
Classify Category and accesories - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"main_category":"glasses","clothing_items":[{"category":"top","confidence":"high"}],"accessories":[{"category":"glasses","confidence":"high"}]}
curl --location --request POST 'https://zylalabs.com/api/12303/clothes+data+retrieval+api/23115/classify+category+and+accesories' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"image_url": "https://media.glamour.mx/photos/6190986aa6e030d6480ff3c7/master/w_1600%2Cc_limit/185450.jpg"}'
| 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 "Classify Category" endpoint returns the dominant clothing category and its confidence level. The "Classify Category and Accessories" endpoint provides the main clothing category, a detailed list of detected garments, their confidence levels, and any accessories identified.
Key fields include "category" and "confidence" in the first endpoint, while the second endpoint includes "main_category," "clothing_items" (with individual "category" and "confidence"), and "accessories."
The response data is structured in JSON format. The first endpoint returns a simple object with category and confidence. The second endpoint returns a more complex object with a main category and an array of clothing items, each with its own category and confidence level.
Both endpoints accept image inputs either as a URL or as binary data. Users can customize requests by providing different image sources to analyze various clothing items.
Typical use cases include fashion applications that require quick identification of clothing types for tagging, filtering, or enhancing user experience in e-commerce platforms and fashion-related websites.
Users can leverage the "category" and "confidence" fields for tagging items in their applications, while the detailed breakdown from the second endpoint allows for richer filtering and outfit analysis, enhancing user engagement.
Data accuracy is maintained through advanced image processing algorithms that focus on identifying dominant clothing categories, ensuring reliable results for garment classification.
Users can expect consistent patterns in responses, such as high confidence levels for clearly visible garments and potential empty accessory lists if no accessories are detected in the image.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,040ms
Service Level:
100%
Response Time:
1,007ms
Service Level:
100%
Response Time:
10,663ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
793ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,280ms
Service Level:
100%
Response Time:
198ms
Service Level:
98%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
800ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
920ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
1,127ms
Service Level:
100%
Response Time:
280ms
Service Level:
100%
Response Time:
465ms