Partially update a catalog node's (category's) main details.

patch

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

Updates only the fields present in the request body (name, number, description); omitted fields are left
unchanged. Use this for a partial edit. To replace all of a node's details in one call, use the full-update PUT
on the same path instead.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

string

required

The internal ID for the catalog node/category you want to update.

Example: 634c26e14cedfd0001775e9f

Body Params

description

object | null

name

object | null

number

string | null

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.

Responses

204

No Content

This response status indicates that the request was successfully processed and there is no content to
return.

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.