Skip to main content
When to use this. Style files are the documents attached to a single style (tech packs, artwork, and reference files) filed into that style’s folders. Use these endpoints to read a style’s folders with their files, list files across the organisation with filters, and fetch a single file with its download URL and thumbnails. Adding and editing style files is not yet part of the public API.

The workflow

A style file wraps an uploaded file resource and places it in one of the style’s folders. You read files back in one of two shapes: folder by folder for a single style, or as a flat list you can filter across every style in the organisation.
1

Read a style's folders

GET /api/styles/{styleId}/files returns the style’s folders, each with its files embedded. Communication, measurement and artwork folders are left out unless you ask for them with folder-type (repeat the parameter for several types), and internal folders are left out unless you pass include-internal=true.
2

List and filter files

GET /api/style-files returns a flat, paginated list of style files across the organisation. Filter by styleId, folderId, folderType, state or colorwayId, and sort by id or name (by name when you do not choose). Page with pageSize and pageNumber, or with the cursor from the previous response.
3

Fetch a single file

GET /api/style-files/{id} returns one file by its id, with its folder, colourway link, download url and thumbnails.

Walkthrough

Read a style’s folders with their files embedded. Only the default folder types come back; add folder-type to include communication, measurement or artwork folders.
The response wraps the folders in the standard envelope. Each file reports its folderId, folderType, position, state, and, for colourway-specific files, its colorwayId and colorwayName.

Field reference

The fields that matter most when reading a style file:

Roles & permissions

Reading style files requires read access under the styles permission: style files are part of the style, not a separate library. Every request is scoped to the caller’s organisation: a style or file that belongs to another organisation returns 403, and one that does not exist returns 404. GET /api/style-files/{id} checks the permission before it looks the file up, so a caller without style read access receives 403 whether or not the file exists.

When things go wrong

Errors use the standard envelope (status: "error", a code, and error.details[]). See Errors & responses for the full list of codes and how to resolve them.

What to call next

Styles

Create and manage the styles that files are attached to.

List a style's folders

Read a style’s folders with files embedded: GET /api/styles/{styleId}/files.

List style files

Filter and page through files across styles: GET /api/style-files.

Authentication

How to get and send your X-Auth-Token API key.