Create compound Category Level Attribute (CLA) and schedule propagation task.

post

https://api-us.bluestonepim.com/pim/catalogs/nodes/{id}/attributes/{attributeDefinitionId}/compound

Creates a new compound Category Level Attribute (CLA) for the specified catalog node/category and schedules a propagation task. This operation is useful for managing complex attributes across multiple catalog nodes efficiently. Propagation means that the CLA will be added to all products in the category and all underlying subcategories.

For more detailed information on how to work with Category Level Attributes in Bluestone PIM, refer to our help pages Category Level Attributes (CLA).

Path Params

string

required

The ID for the catalog node/category.

Example: 634c26e14cedfd0001775e9f

attributeDefinitionId

string

required

The ID for the attribute definition.

Example: 634c26e14cedfd0001775e9e

Headers

context

string

Specifies the context in which to operate. If omitted, the default context en is used.

In Bluestone PIM, the context is generally synonymous with the language setting. The context determines how product information is tailored and presented based on language or other local specifications.

For more detailed information on how context relates to language settings in Bluestone PIM, refer to the Languages and Context documentation.

Note: The default context is identified by the ID "en". IDs for additional contexts begin with a lowercase "L", not with the digit "1", followed by a number. This naming convention helps distinguish between default and custom contexts within Bluestone PIM.

context-fallback

string

Specifies whether to enable the fallback mechanism for the context. If omitted, the default value true will be used. When set to true, the system will provide a default translation or relevant information if the requested context's specific translation is missing.

For more detailed information on how context relates to language settings in Bluestone PIM, refer to the Languages and Context documentation.

Note: Setting the context-fallback parameter to false disables the fallback mechanism. In this configuration, if a translation or specific context information is not available, the system will not provide an alternative or default content. This ensures that only content that matches the exact context ID requested is returned, potentially leading to cases where no content is available if the specific translation is missing.

Responses

202

Accepted

The request has been accepted for processing, but the processing has not been completed.

400Bad Request This response indicates that the server could not understand the request due to invalid syntax. It is typically triggered by client-side input errors such as improperly formatted requests, missing required fields, or invalid data values.

404Not Found This response indicates that the requested resource could not be found on the server. It typically occurs when no resource matches the requested URI, or the resource identifier used in the request does not exist.

409Conflict This response indicates that the request could not be completed due to a conflict with the current state of the target resource. This typically occurs when there are duplicate entries or other data conflicts.