ShopEazydevelopers
API referenceMerchant API BetaProducts

Change a customisation group

Beta
Credentials
  • OAuth access token
Scopes
listings:write
Subscription
Needs an active plan. Otherwise 403 subscription_locked.
Idempotency
Send an Idempotency-Key header. A retry with the same key does the work once.
PATCH
/v1/merchant/stores/{storeId}/customisation-groups/{groupId}

Send only what changes. A choices list replaces the whole list: keep a choice's id so listings keep their price overrides for it. status: active brings an archived group back.

Access: OAuth scope listings:write; write-gated by the subscription.

Authorization

merchantOAuth listings:write
headerAuthorizationBearer <token>

OAuth 2.1 (authorization code + PKCE S256, public clients, dynamic registration) for connected AI apps. Effective power is scopes granted AND the person's role today AND the plan. orders:refund, billing:write and team:write are opt-in on the consent screen. Write implies read for marketing:read and messages:read, so a grant holding marketing:write passes a marketing:read check, and messages:send passes messages:read.

Scope: listings:write

Path Parameters

storeId*string

A store the person can reach. Any other id answers 404, never 403.

groupId*string

A customisation group id, from GET /customisation-groups.

Header Parameters

Idempotency-Key*string

Required on every write. Minted on the device when the person taps, reused on every retry. A write without one, or with one that does not match the pattern, is refused with 422 validation_error. Scoped to the token's subject, remembered 24 hours. A replay returns the first 2xx response with Idempotent-Replay: true; a request still running answers 409 in_flight; the same key with a different method, path or body answers 409 idempotency_key_reused; non-2xx results are not remembered. If the key store cannot be read nothing is processed and the answer is 503 idempotency_unavailable: retry with the same key.

Match^[A-Za-z0-9_-]{8,128}$

Request Body

application/json
  1. body

Any of the group's fields (the rest are kept), and status.

name?string
Lengthlength <= 60
description?|
Lengthlength <= 240
select?string
Value in"one""many"
required?boolean
max?|
Range1 <= value
choices?array<>
Items1 <= items <= 50
status?string
Value in"active""archived"

Response Body

OK

application/json
  1. response
data*

A group and the ids of the listings that offer it.

Example Request
curl -X PATCH 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/customisation-groups/<groupId>' \  -H 'Authorization: Bearer <access_token>' \  -H 'Idempotency-Key: <unique_key>' \  -H 'Content-Type: application/json' \  -d '{  "description": "Choose how it arrives. Cards are written by hand.",  "max": 1}'
Example Response
{  "data": {    "id": "QdChQIpRuzJvj6uu3Huc",    "name": "Gift wrapping",    "description": "Choose how it arrives. Cards are written by hand.",    "select": "one",    "required": false,    "max": null,    "status": "active",    "sortOrder": 0,    "choices": [      {        "id": "f0e14318",        "name": "Plain brown paper",        "price": {          "amount": 0,          "currency": "ZAR"        },        "available": true,        "description": null,        "imageUrl": null      },      {        "id": "a26f9c74",        "name": "Ribbon and card",        "price": {          "amount": 4500,          "currency": "ZAR"        },        "available": true,        "description": "A handwritten card in the box.",        "imageUrl": null      }    ],    "updatedAt": 1792924389056,    "listingIds": []  }}

One customisation group and the listings that offer it GET

Access: OAuth scope `listings:read`; not write-gated.

Archive a customisation group DELETE

Groups are archived, never deleted: orders hold what was picked by id. Listings keep the attachment, and the shop stops offering the group. Bring it back with updateCustomisationGroup (`status: active`). Archiving twice is fine. Access: OAuth scope `listings:write`; write-gated by the subscription.