Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.drssed.app/llms.txt

Use this file to discover all available pages before exploring further.

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:
FieldTypeDescription
clothing_idstring (UUID)Unique identifier for the clothing item.
namestringA display name for the item (e.g. "Blue Oxford Shirt").
categorystring (enum)The garment category. One of JACKET, TOP, BOTTOM, or FOOTWEAR.
colorstringDominant color — either a hex code (e.g. "#3A86FF") or a color name (e.g. "navy").
seasonsarray of stringsThe seasons the item suits. Any combination of Spring, Summer, Autumn, Winter.
tagsarray of stringsStyle tags. Any combination of Casual, Formal, Sports, Vintage.
descriptionstringOptional free-text description.
image_idstringReference to the processed image uploaded via POST /images/preview.
is_publicbooleanWhether the item is visible to other users.
user_idstringThe ID of the user who owns this item.
created_atstring (ISO 8601)Timestamp of when the item was created, e.g. "2025-09-01T14:30:00+00:00".

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:
ParameterTypeDescription
limitintegerMaximum number of items to return in a single response.
offsetintegerNumber of items to skip before starting to return results.
For example, to fetch the second page of 20 items, use ?limit=20&offset=20.

Example clothing item object

{
  "clothing_id": "c3d4e5f6-7890-abcd-ef01-234567890abc",
  "name": "Blue Oxford Shirt",
  "category": "TOP",
  "color": "#3A86FF",
  "seasons": ["Spring", "Summer"],
  "tags": ["Casual", "Formal"],
  "description": "A lightweight Oxford shirt, works well for smart-casual occasions.",
  "image_id": "img_a1b2c3d4e5f6",
  "is_public": false,
  "user_id": "u9f8e7d6c-5b4a-3210-fedc-ba9876543210",
  "created_at": "2025-09-01T14:30:00+00:00"
}
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.