Create a modifier group
A modifier group is the “header” choice presented at order time (“Size”, “Toppings”). After creating it:
- Add modifier options via
linkModifiersToGroup— the options themselves are items created withonlyModifier: true. - Attach the group to one or more items via
linkModifierGroupToItem.
max is mandatory and ≥ min.
Authorizations
Authorization: Basic base64(partner_key:secret_key).
Credentials are issued by a klikit operator. The plaintext
secret_key is shown once at issuance and cannot be retrieved
later — store it securely. If lost, ask your operator to rotate
the secret to receive a new one. The old secret stops working
immediately on rotation; there is no overlap window.
Body
Locale-keyed text. Keys are ISO 639-1 codes (en, id, ja, ...).
Use whichever key matches your storefront; klikit ships a value
for every locale your business is configured for.
Maximum number of modifiers a customer may pick. Required.
Locale-keyed text. Keys are ISO 639-1 codes (en, id, ja, ...).
Use whichever key matches your storefront; klikit ships a value
for every locale your business is configured for.
Per-provider visibility flag. Keys are provider ids (as strings)
from GET /v1/partner/providers. Set a provider's value to
true to publish on that channel. Providers absent from the map
default to hidden.
Klikit's own marketplace is provider id "1".
Minimum number of modifiers a customer must pick.
Response
Modifier group created. data.id is the modifier-group id.
Canonical response wrapper. Every response — success or error —
carries the request_id so you can quote one id to klikit
support to correlate a request end-to-end.
"req_4d1b7e3f-..."
Endpoint-specific payload on success.
Machine-readable error code + human message. The code is stable
across releases — switch on code in your client code rather
than parsing the message text.
Common codes you will encounter as a partner: