Hanzo
OpenapiCommerce

Delete a collection, keeping a recoverable copy

A collection is a merchandising group a storefront renders — a slug and name, copy and media, flat lists of the product and variant ids it holds,…

DELETE /v1/commerce/collection/{collectionid}

Addresshttps://api.hanzo.ai/v1/commerce/collection/{collectionid}
MethodDELETE
Operationdelete_commerce_collection_by_collectionid
AuthAuthorization: Bearer $HANZO_API_KEY

A collection is a merchandising group a storefront renders — a slug and name, copy and media, flat lists of the product and variant ids it holds, published, preorder and out-of-stock flags, and an availability window. Membership lives on the collection as those id lists rather than as a join, so putting a product into a collection is a write here and not on the product. Removes the addressed row and answers 204 with no body. Before the live row goes it is written once more under a deleted tombstone kind, so a deletion leaves a recoverable copy rather than destroying the record outright — and a tombstone that cannot be written fails the call with 500 before anything is removed. The id is resolved inside the caller org's own namespace, so an absent or foreign id is 404. Any valid access token reaches it. The org must also be entitled to the commerce admin: the paywall answers 402 subscription_required unless the org holds an active or trialing pro subscription, a live trial credit or a redeemed invite, and 503 when that entitlement cannot be read rather than admitting on an unknown. The internal service token and a platform superadmin pass straight through. The token must also carry Admin or WriteCollection.

Request

1 field.

FieldInTypeRequiredDescription
collectionidpathstringyes

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo commerce collection rm <collectionid>

Commerce API · All Hanzo APIs · Interactive reference

How is this guide?

On this page