Delete Collect

🔒

Requires write_collection access scope. More access scope

The Delete Collect API removes an association between a product and a collection by deleting a collect object. This operation ensures the product is no longer part of the specified collection.This API is especially useful for:

  1. Removing products from collections no longer relevant for marketing or categorization.
  2. Cleaning up collections during inventory updates or reorganization.

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.

Public Request Parameters

Parameter NameTypeRequiredParameter LocationParameter ValueDescription
Access-TokenStringYesHeaderBx-_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-TypeStringYesHeaderapplication
/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 NameTypeMandatoryParameter LocationExample ValueDescription
errorStringNoResponse 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" }.
errorsArrayNoResponse Body{ "errors"["ProductId is required"] }A list of errors that occurred during the request processing. Example: { "errors": [ "No Context" ] }.
Request-IdStringYesHeaderBx-_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

ParameterTypeRequiredDescriptionExample
idstringYesUnique identifier of the collect to delete. Must be a valid UUID."123e4567-e89b-12d3-a456-426614174000"

Response Explanation

Successful Response

FieldTypeDescriptionExample
{}objectEmpty object indicating successful deletion.{}

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.

FieldTypeExampleDescription
errorsArray[ "Smart collection can't be updated."]A list of errors encountered during the request processing.
FieldTypeExampleDescription
errorArray "store is not active"Indicates an error encountered during the process.

Request Examples

curl --request DELETE \
     --url https://{shopdomain}.myshoplazza.com/openapi/2022-01/collects/{id} \
     --header 'accept: application/json' \
     --header 'access-token: {your-access-token}'

Success Response Example

{}

Error Response Example

{
  "errors": [
     "Smart collection can't be updated."
  ]
}
{
  "error": "store is not active"
}

Error Details

Status CodeMessagePossible ReasonExample Response
400Bad RequestInvalid input format or request structure (e.g., missing required fields or incorrect data types).Bad Request
UnauthorizedThe request is missing valid authentication credentials or the credentials provided are invalid.Unauthorized
422Invalid or empty collect_idmissing required collect_id or collect_id with incorrect UUID types{ "errors": [ "ID must be a valid UUID"]}
Record not foundThe Record ID provided in the request does not exist.{ "errors": ["Record not found."] }
Smart collection can't be deleteThe collection you are attempting to update is a smart collection{ "errors": ["Smart collection can't be updated."] }
Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!