Requires
write_collection
access scope. More access scope
The Update Collection API allows users to update details of an existing collection by providing the collection ID and the desired updates in the request body. This API supports updates to various attributes, including the title, description, SEO details, associated products, and more.This API is especially useful for:
- Modify collection details such as title, description, or handle.
- Update the associated image, SEO metadata, and sorting order for merchandise.
Note: The operation is scoped to a specific shop, identified by its unique domain prefix (shopdomain), ensuring all updates are applied to the correct store. be store123
.
Public Request Parameters
Parameter Name | Type | Required | Parameter Location | Parameter Value | Description |
---|---|---|---|---|---|
Access-Token | String | Yes | Header | Bx-_5aV eXNwl-4AB98s5xLV yg0fNzGf MuTpqtlBA | Used to authenticate API requests. Obtain an access token from the Access Token Guide. Pass it in the Authorization header for every request. |
Content-Type | String | Yes | Header | application /json | Indicates the media type of the request body. It tells the server how to parse the request and the client how to interpret the response. For more details, visit Content-Type. |
Public Response Parameters
Parameter Name | Type | Mandatory | Parameter Location | Example Value | Description |
---|---|---|---|---|---|
error | String | No | Response Body | { "error": "store is not active" } | Indicates an error encountered during the process. This field typically appears when the Access Token is missing or invalid. Example: { "error": "store is not active" } . |
errors | Array | No | Response Body | { "errors"["No Context"] } | A list of errors that occurred during the request processing. Example: { "errors": [ "No Context" ] } . |
Request-Id | String | Yes | Header | Bx-_5aV eXNwl-4AB98s5xLV yg0fNzGf MuTpqtlBA | A unique identifier for each request. It helps in identifying and debugging specific requests. |
Error and Errors Clarification:
Added explanation that the error and errors fields are currently dependent on the API implementation, with plans for future unification.
Request Parameters
Path Parameters
Parameter | Type | Required | Example | Description |
---|---|---|---|---|
id | string | Yes | a60fe556-43ad-4e07-9125-507ac1bf71f7 | Unique identifier of the collection. |
Body Parameters
Field | Type | Example | Description |
---|---|---|---|
collection.title | string | Summer Collection | Name of the collection. |
collection.handle | string | summer-collection | URL-friendly handle for the collection. |
collection.description | string | A collection for summer wear. | Description of the collection. |
collection.image.src | string | //cdn.shoplazza.com/image.jpg | Source URL of the collection image. |
collection.image.width | integer | 800 | Width of the collection image in pixels. |
collection.image.height | integer | 600 | Height of the collection image in pixels. |
collection.image.alt | string | Summer wear collection image. | Alt text for the collection image. |
collection.seo_title | string | Best Summer Collection | SEO title for the collection. |
collection.seo_description | string | Shop the best summer collection. | SEO description for the collection. |
collection.seo_keywords | string | summer, clothing, fashion | SEO keywords for the collection, comma-separated. |
collection.sort_order | string | title-asc | Sorting order for merchandise. Options include manual (default), sales-desc , price-asc , price-desc , views-desc , and more. |
collection.product_ids | string | prod1-id,prod2-id | Comma-separated list of product IDs to associate with the collection. |
collection.is_clear_all_product_ids | boolean | false | Indicates whether to remove all associated product IDs. |
Response Explanation
Successful Response
Field | Type | Example | Description |
---|---|---|---|
collection.id | string | a60fe556-43ad-4e07-9125-507ac1bf71f7 | Unique identifier of the collection. |
collection.title | string | Test-Collection | Name of the collection. |
collection.description | string | Desc | Description of the collection. |
collection.handle | string | test-collection | URL-friendly handle for the collection. |
collection.smart | boolean | false | Indicates whether the collection is smart. |
collection.image | object | Image Object | Object containing details of the collection image. |
collection.image.src | string | //cdn.shoplazza.com/loading.png | Source URL of the collection image. |
collection.image.width | integer | 100 | Width of the collection image in pixels. |
collection.image.height | integer | 100 | Height of the collection image in pixels. |
collection.image.alt | string | "" | Alt text for the collection image. |
collection.image.path | string | loading.png | File path of the collection image. |
collection.seo_title | string | seo_title | SEO title of the collection. |
collection.seo_description | string | Desc | SEO description of the collection. |
collection.seo_keywords | string | test | SEO keywords associated with the collection. |
collection.sort_order | string | title-asc | Merchandise sorting rules. Options include: manual (default), sales-desc , price-asc , price-desc , views-desc , vendor-asc , vendor-desc , created-desc , and more. (see Sort Order Options). |
collection.created_at | string | 2024-04-16T10:31:12Z | Timestamp when the collection was created. |
collection.updated_at | string | 2024-04-16T10:31:12Z | Timestamp when the collection was last updated. |
Error Response
Error responses in the API can be represented using two different fields: errors
and error
. Both fields provide details about issues encountered during request processing. Below is an explanation of the fields with their respective examples and descriptions.
Field | Type | Example | Description |
---|---|---|---|
errors | Array | [ "Collection not found"] | A list of errors encountered during the request processing. |
Field | Type | Example | Description |
---|---|---|---|
error | Array | "store is not active" | Indicates an error encountered during the process. |
Request Examples
curl --request PUT \
--url https://{shopdomain}.myshoplazza.com/openapi/2022-01/collections/{id} \
--header 'accept: application/json' \
--header 'access-token: {your-access-token}' \
--header 'content-type: application/json' \
--data '{
"collection": {
"title": "Updated Summer Collection",
"description": "Updated description for summer collection.",
"image": {
"src": "//cdn.shoplazza.com/image.jpg",
"width": 800,
"height": 600,
"alt": "Updated collection image"
},
"seo_title": "Updated Best Summer Collection",
"seo_description": "Updated shop the best summer collection.",
"seo_keywords": "summer, updated clothing, fashion",
"sort_order": "sales-desc",
"product_ids": "prod1-id,prod3-id",
"is_clear_all_product_ids": false
}
}'
Success Response Example
{
"collection": {
"id": "a60fe556-43ad-4e07-9125-507ac1bf71f7",
"title": "Test-Collection",
"description": "Desc",
"handle": "test-collection",
"smart": false,
"image": {
"src": "//cdn.shoplazza.com/loading.png",
"width": 100,
"height": 100,
"alt": "",
"path": "loading.png"
},
"seo_title": "seo_title",
"seo_description": "Desc",
"seo_keywords": "test",
"sort_order": "title-asc",
"created_at": "2024-04-16T10:31:12Z",
"updated_at": "2024-04-16T10:31:12Z"
}
}
Error Response Example
{
"errors": [
"Collection not found"
]
}
{
"error": "store is not active"
}
Error Details
Status Code | Message | Possible Reason | Example Response |
---|---|---|---|
400 | Bad Request | Invalid input format or request structure (e.g., missing required fields or incorrect data types). | Bad Request |
Unauthorized | The request is missing valid authentication credentials or the credentials provided are invalid. | Unauthorized | |
404 | Collection Not Found | The collection ID provided in the request does not exist. | { "errors": ["Collection not found"] } |
422 | Invalid UUID | - Invalid or empty collection_id . - Invalid product_ids provided (non-UUID values). | { "errors": [ "productId has an invalid UUID"]} |
Invalid Date Format | updated_at_min or updated_at_max has an incorrect date format. | { "errors": [ "updated_at_min has an invalid date format"]} |