Upsert the values of one attribute across many products in a single bulk operation.

post

https://api-us.bluestonepim.com/pim/products/attributes/by-ids

For every product listed in the request (selected by ID, max 100) this sets the given values for the one
attribute definition: products that already have the attribute get their values updated, products that do not
have it get the value inserted. Applies to a single attribute definition per call. Runs synchronously and
completes before responding; it returns no body and no job to poll. Fails if any listed product ID does not
exist.

Use this to set attribute values in bulk, including on products that may not yet have the attribute assigned.
The sibling PUT on this same path only updates products that already have the attribute (and can be told to fail
when it is missing); it never inserts. Prefer this upsert unless you specifically want that update-only behavior.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

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

attributeDefinitionId

string

required

attributeValues

array of strings

New values to set for the attribute on the selected products. Omit or pass an empty list to clear the value.

productIds

array of strings, unique

length between 1 and 100

Internal IDs of the products to apply the change to; 1 to 100 IDs. The operation fails if any of them does not exist.

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.