Skip to main content
When to use this. A care instruction layer names a physical layer of a garment — for example “Main”, “Lining”, or “Shell”. Layers are created once in Admin, given a stable user-defined ID, and then selected on styles to organise the composition of each layer’s materials and care icons. Use these endpoints to build and maintain that layer library. Multi-language translation of layer text requires a Professional licence.

​
The workflow

Layers sit one level above materials in the care instruction setup hierarchy: you create the layers, optionally translate them into working languages, and then select them on styles when defining each layer’s fibre composition and washing icons.
1

Create layers

POST /api/care-instruction-layers with the default text and an optional user-defined ID. The body is an array — one or many layers are created in a single all-or-nothing transaction.
2

Add translations (optional)

Include a languages array in the create body, or update an existing layer via PUT /api/care-instruction-layers/{id} with a replacement languages list. Requires a Professional licence and at least one language configured under Admin > General Settings.
3

Find and list layers

GET /api/care-instruction-layers with filters (text, userDefinedIds, state) to look up layers for import verification or to drive a selection dropdown.
4

Retire or bulk-manage

Use PUT /api/care-instruction-layers/{id} to deactivate a single layer, or PUT /api/care-instruction-layers (bulk) to update positions, states, and translations — or hard-delete multiple layers — in one transaction by setting state: "deleted" on those items.

​
Walkthrough

Create a “Lining” layer with a Norwegian translation in a single call.
The response wraps the created layers in the standard envelope. Hold onto each id — it is the stable reference used when reordering or deactivating the layer later.

​
Field reference

​
Roles & permissions

Managing the care instruction layer library requires the company permission on a designer (brand) account — typically CompanyAdmin. The user also needs the Care Instruction role assigned in Admin > Company info > Roles. Supplier accounts collaborate on styles but do not manage a brand’s care instruction layer library.
Multi-language translations require a Professional licence subscription. The languages field is accepted on all tiers but translation values are only surfaced where the feature is enabled.

​
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. Common cases:
  • 409 Conflict on DELETE — the layer is still referenced by one or more styles. Deactivate it with PUT /api/care-instruction-layers/{id} (state: "inactive") instead of deleting it, or remove it from all styles first.
  • 400 validation_error — text is missing on create, or state: "deleted" was passed to the single-update endpoint.
  • 404 resource_error — the id does not exist or does not belong to your organisation.

​
What to call next

Care instructions

Create the washing and handling instructions that sit within each layer on a style.

Colors

Build the colour library used alongside care instruction layers on styles.

Seasons

Create the seasons that styles — and their care instruction layers — are filed under.

Style categories

Organise styles by category before assigning layers and care labels.