Create modifier in Clover
POS API · write, waits for approval · 100% field coverage
Your agent can create modifier 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
POST https://unify.apideck.com/pos/modifiers
Headers: x-apideck-service-id: clover, plus your app id and the customer's consumer id. Apideck MCP tool: pos-modifiers-add. Agent operation id: unified.pos.modifiersAdd.
Body fields
| Field | Type | Description |
|---|---|---|
| idempotency_key | string | A value you specify that uniquely identifies this request among requests you have sent. |
| name · required | string | |
| alternate_name | string | |
| price_amount | number | |
| currency | string | Indicates the associated currency for an amount of money. Values correspond to [ISO 4217](https://en.wikipedia.org/wiki/ |
| modifier_group_id · required | string | |
| available | boolean |
More for modifiers in Clover
Create modifier in other POS apps
The same call works for each of these; only the service id changes.