Hanzo
OpenapiCommerce

Change part of a collection

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,…

PATCH /v1/commerce/collection/{collectionid}

Addresshttps://api.hanzo.ai/v1/commerce/collection/{collectionid}
MethodPATCH
Operationpatch_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. Loads the stored row and decodes the body OVER it, so only the fields the body names change and everything else keeps its stored value — the difference from the full replace, which clears what it is not told. Answers the merged row. An id absent from the caller org's namespace is 404 and a body that fails to decode is 400. 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 ReadCollection and WriteCollection together.

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 update <collectionid>

Commerce API · All Hanzo APIs · Interactive reference

How is this guide?

On this page