FluentaAPI
Catalogue

Update catalogue entry

updateCatalogueEntryPermission program

Edit a template of the «Catálogo de referencias»: only the fields sent change; null clears an optional one. No OC changes.

PATCH/v1/external/organizations/{organizationId}/catalogue/{templateId}

Authorization

apiToken
AuthorizationBearer <token>

An API token created in Configuración › Tokens de API, or a connected app’s access token

In: header

Path Parameters

templateId*integer
organizationId*integer

The organization, from getMe or listOrganizations.

Header Parameters

Idempotency-Key?string

A fresh unique string per intended write (1 to 255 visible ASCII characters). Sent again unchanged only to retry THAT write after a timeout or a 409 IDEMPOTENCY_IN_PROGRESS: the stored answer comes back (Idempotency-Replayed: true) and nothing is written twice. The same key with another request is a 422 IDEMPOTENCY_KEY_REUSED.

Length1 <= length <= 255

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

curl -X PATCH "https://api.fluenta.io/v1/external/organizations/0/catalogue/0" \  -H "Authorization: Bearer fluenta_live_XXXX" \  -H "Content-Type: application/json" \  -d '{}'
{  "id": 0,  "name": "string",  "description": "string",  "garment": "string",  "goal": 0,  "price": 0,  "color": "string",  "orderNumber": "string",  "total": 0,  "step1Name": "string",  "step1Goal": 0,  "step2Name": "string",  "step2Goal": 0}

Create catalogue entry POST

Add a reusable style to the «Catálogo de referencias», as its «Nueva referencia» does: the name is unique in the catálogo (409 `REFERENCE_TEMPLATE_EXISTS`).

Delete catalogue entry DELETE

Delete a template of the «Catálogo de referencias» (no OC changes), only with the `confirmationToken` its preview returned once the usuario said yes: 422 `CONFIRMATION_REQUIRED` without it, 409 `PREVIEW_STALE` when it ran out or the template changed since.