Skip to main content
Every piece you add to Drssed is stored as a clothing item — a structured record that describes a single garment with its category, color, seasons, tags, and a link to a processed image. Understanding this model helps you work with the wardrobe endpoints effectively, interpret responses correctly, and decide how to present data in your app.

The clothing item object

A clothing item has the following fields:

Category values

The category field uses a fixed set of values:
  • JACKET — outerwear including jackets and coats
  • TOP — anything worn on the upper body: shirts, t-shirts, sweaters, hoodies
  • BOTTOM — lower-body garments: jeans, trousers, shorts, skirts
  • FOOTWEAR — all footwear types: sneakers, boots, sandals, heels

Season and tag arrays

Both seasons and tags are optional arrays. You can assign multiple values — for example, a versatile jacket might carry ["Spring", "Autumn"], and a blazer might have ["Formal", "Vintage"].

Public and private items

The is_public flag controls visibility beyond the owning user. When is_public is false, the item is only accessible to its owner. Setting is_public to true makes the item retrievable by other authenticated users. You control is_public at creation time and can update it later via PATCH /clothing/{clothing_id}.

Pagination

The wardrobe list endpoint (GET /users/me/clothing) returns items in pages. Use the limit and offset query parameters to move through the collection: For example, to fetch the second page of 20 items, use ?limit=20&offset=20.

Example clothing item object

The image_id field must be obtained from the response of POST /images/preview before you create a clothing item. See AI image processing for details.