Update modifier group in Clover
POS API · write, waits for approval · 100% field coverage
Your agent can update modifier group in Clover through Apideck's POS API, the same call it makes for every POS app. It changes data in the customer's Clover account, so it stops with the exact request until a person approves it. Apideck adds the customer's Clover credentials, so no token ever reaches the agent.
The call
PATCH https://unify.apideck.com/pos/modifier-groups/{id}
Headers: x-apideck-service-id: clover, plus your app id and the customer's consumer id. Apideck MCP tool: pos-modifier-groups-update. Agent operation id: unified.pos.modifierGroupsUpdate.
| Parameter | In | Description |
|---|---|---|
| id · required | path | ID of the record you are acting upon. |
Body fields
| Field | Type | Description |
|---|---|---|
| name | string | |
| alternate_name | string | |
| minimum_required | integer | |
| maximum_allowed | integer | |
| selection_type | string | |
| present_at_all_locations | boolean | |
| modifiers | array | |
| deleted | boolean | Flag to indicate if the object is deleted. |
| row_version | string | A binary value used to detect updates to a object and prevent data conflicts. It is incremented each time an update is m |
More for modifier groups in Clover
list_modifier_groupscreate_modifier_groupget_modifier_groupdelete_modifier_group
Update modifier group in other POS apps
The same call works for each of these; only the service id changes.