Upsert several attributes on one product in a single call.

put

https://api-us.bluestonepim.com/pim/products/{id}/attributes

For each attribute in the request body (identified by its attribute definition ID, up to 100 per call) this sets
the given value on the product: if the product already has that attribute its value is updated, otherwise the
attribute is added with that value. Runs synchronously and completes before responding; returns no body and no
job to poll. Fails if no product with the given ID exists.

Use this to set multiple different attributes on a single product at once. To change one attribute across many
products instead, use the upsert or update endpoints on /products/attributes/by-ids. To add a single attribute
to one product without touching others, use POST /products/{id}/attributes.

For more information, refer to the Create, edit or remove
attributes article.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

string

required

The internal ID of the product for which the attributes are being updated.

Example: 634c26e14cedfd0001775e9f

Query Params

forceVla

boolean

Defaults to false

Specifies whether to force the update of a variant level attribute (VLA) value down from a
VARIANT GROUP product to all child VARIANT products.

This flag is only taken into consideration for VARIANT GROUP products and only where the attribute is
currently set as a VLA on the VARIANT GROUP product.

If omitted, the default value false will be used which means that possible VLA values on a VARIANT GROUP
product will not be enforced down to child VARIANT products.

Note that forceVla flag is only taken into consideration when the attribute change will be an update operation
but not an add value (insert) operation on a VARIANT product.

This means that a child VARIANT product will get the new value if it does not have the attribute assigned or
an attribute value defined even if forceVla is false while other child VARIANT products that already have
an attribute value defined will be left unchanged.

This is because a VARIANT product without the attribute or without an attribute value defined is treated as an
add value (insert) operation while the other VARIANT products are treated as update operations.

For more detailed information on working with VLAs in Bluestone PIM, refer to our help pages The data model -
Variant Level Attribute (VLA).

Body Params

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

boolean

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

204

No Content

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.