Partial Content Update
PATCHOverview
Section titled “Overview”This endpoint is ideal for making small, frequent updates to existing objects, such as changing a product price, description, or availability. You only need to send the identity of the object and the specific fields you want to add or modify.
Key behaviour
Section titled “Key behaviour”- This operation is incremental and does not affect fields you omit from the request.
- It cannot be used to create new objects. If an
identityis not found, the request returns an error. - You cannot change an object’s
type.
Common use cases
Section titled “Common use cases”- Updating prices or stock levels.
- Adding a promotional label or updating a product description.
- Changing
availabilitystatus. - Synchronizing real-time data from your database to the search index without a full reindex.
The batch limit for this endpoint is 300 objects per request.
Request parameters
Section titled “Request parameters”The root of your request body must be a JSON object containing a single key, objects.
Top-level Request Structure
Section titled “Top-level Request Structure”| Parameter | Type | Required | Description |
|---|---|---|---|
objects | Array | ✓ | An array of one or more objects to be partially updated. |
Object structure
Section titled “Object structure”Each object in the objects array must contain an identity and the fields you want to change.
| Parameter | Type | Required | Description |
|---|---|---|---|
identity | String | ✓ | The unique identifier of the object you want to update. |
fields | Object | A key-value map of attributes to add or modify. | |
nested | Array | An array of nested objects. Sending this key replaces the entire existing nested array for the object. |
How to Send a Partial Update Request
Section titled “How to Send a Partial Update Request”The examples show how to prepare and send a request to the API endpoint.
Authentication is required for all requests. The code demonstrates how to construct the necessary headers, including Date and Authorization. The Authorization header requires a dynamically generated HMAC signature. For a detailed explanation of how to create this signature, refer to the main API Authentication guide.
Error handling
Section titled “Error handling”| HTTP Status | Description |
|---|---|
| 400 Bad Request | The request structure is invalid, the JSON is malformed, or an object was not found. |
| 413 Payload Too Large | The request exceeds 5 MB, or 10 MB if compressed. Reduce batch size or enable compression. |
| 429 Too Many Requests | The rate limit has been exceeded. Check the Retry-After header and see the Throttling docs. |
Related endpoints
Section titled “Related endpoints”- Content Update creates or replaces objects.
- Content Removal deletes objects from the index.
- Update by Query performs bulk updates based on search criteria.
Was this page helpful?
Thanks.