Fabric documentation
V1BrandsBrandidAttributesAttributeid

Update an attribute definition

PUT
/v1/brands/{brandId}/attributes/{attributeId}

Replaces the editable fields. The key is not among them — every existing value joins on it, so re-keying would orphan the column.

The FAQ, meta title and meta description attributes Fabric generates into (fabric.faq, fabric.meta_title, fabric.meta_description) keep their kind and type: changing either answers 409. Their name and extract stay editable, and extract: false stops Fabric generating them.

Authorization

apiKey
headerAuthorizationBearer <token>

Your API key. X-Api-Key: <key> is accepted as an alternative.

A key belongs to an organization, not a user, so it outlives whoever created it. It carries two independent things, and both are checked: an org role (a member key cannot approve a publish or activate a mapping) and a set of scopes — catalog:read, catalog:write, enrichment:write, publishing:read, publishing:write, org:read, org:write. Holding a scope does not grant a role, and holding a role does not grant a scope.

GET /v1/me returns both for the key you are holding.

Path Parameters

brandId*string

The brand to read.

attributeId*string

Request Body

application/json
  1. body
allowedValues?|

A newline- or comma-separated list, meaningful only for Enum and List types. Empty is stored as null.

extract*boolean

Whether enrichment may write this attribute.

kind*string
Value in"information""filtering""media_ref""metadata""alt_image_text""meta_tags""faq"
name*string
Lengthlength <= 120
type*string
Value in"String""Number""Boolean""Enum""Date""List""Price"

Response Body

Updated.

application/json
  1. response
id*string
Example Request
curl -X PUT 'https://fabric.inc/api/v1/brands/string/attributes/string' \  -H 'Content-Type: application/json' \  -d '{  "extract": true,  "kind": "information",  "name": "string",  "type": "String"}'
Example Response
{  "id": "string"}