The
scene array defines how clothing items are visually arranged in the outfit collage. Each entry is a CanvasPlacement object that references a clothing item by its clothing_id and specifies its position (x, y), depth (z), scale, and rotation.1
Create an outfit
Call A successful response returns
POST /users/me/outfits to create a new outfit. At minimum you must provide a name. You can optionally include a description, a scene layout, seasons, tags, and visibility settings.Body fields:Each object in the
scene array must include:201 Created with the new outfit:2
List outfits
You have two options for listing outfits depending on whose wardrobe you are viewing.Both routes accept The response includes the outfit list alongside pagination metadata:
GET /users/me/outfits returns all of your outfits, including private ones. GET /users/{user_id}/outfits returns only the public outfits for a given user. Use the /me route when building your own wardrobe view; use the /{user_id} route when displaying another user’s public outfits.limit (default 50) and offset (default 0) for pagination.3
Get a specific outfit
Retrieve the full details of a single outfit — including its complete scene array — with
GET /outfits/{outfit_id}.4
Update an outfit
Use A successful update returns
PATCH /outfits/{outfit_id} to update any subset of fields. All fields are optional — only what you include is changed. To rearrange items in the scene, pass the full updated scene array.Updatable fields: name, is_favorite, is_public, seasons, tags, scene200 OK with the updated outfit object.5
Delete an outfit
Remove an outfit with A successful deletion returns
DELETE /outfits/{outfit_id}. Like clothing items, outfits are soft-deleted — they disappear from your list immediately but are not permanently erased right away.204 No Content with an empty body.Rate limits
Most outfit endpoints are limited to 5 requests per minute. ThePATCH /outfits/{outfit_id} endpoint has a stricter limit of 3 requests per minute.