Skip to main content
Before you can add a clothing item to a wardrobe, you need a processed image. Drssed provides an image processing pipeline that takes a raw clothing photo, strips the background, and returns both a clean image URL and a set of AI-detected metadata — category, color, seasons, and tags — that you can use directly when creating the clothing item. This saves you from having to classify items manually and gives your users a consistent image presentation.

​
POST /images/preview

This endpoint accepts a clothing photo and returns the processed result.

​
Request

Send the image as a file field named file in a multipart/form-data request body.

​
Response fields

Status: 201 Created

​
Example request

​
Example response

POST /images/preview is rate limited to 1 request per minute per user. Design your upload flow to process one image at a time and avoid retrying failed uploads in rapid succession.
The response includes image_category, image_seasons, and image_tags detected by the AI. You can use these as default values when creating the clothing item — just pre-fill the form fields in your UI from the response and let the user adjust anything the AI got wrong.

​
Using image_id when creating a clothing item

The image_id returned by POST /images/preview is the value you pass in the image_id field when calling POST /users/me/clothing. Without it, you cannot create a clothing item — the field is required. The typical flow is:
  1. Call POST /images/preview with the photo.
  2. Store the returned image_id (and optionally pre-fill image_category, image_seasons, image_tags).
  3. Call POST /users/me/clothing with the image_id and any other clothing fields.

​
GET /uploads/clothing_images/

Once a clothing item has been created, you can retrieve its processed image using this endpoint. Pass the clothing_id of the item as a path parameter. The endpoint returns the processed image file directly, suitable for displaying in a wardrobe view.

​
Error cases