Delete modifier in Clover
POS API · write, waits for approval · 100% field coverage
Your agent can delete 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
DELETE https://unify.apideck.com/pos/modifiers/{id}
Headers: x-apideck-service-id: clover, plus your app id and the customer's consumer id. Apideck MCP tool: pos-modifiers-delete. Agent operation id: unified.pos.modifiersDelete.
| Parameter | In | Description |
|---|---|---|
| id · required | path | ID of the record you are acting upon. |
| filter[modifier_group_id] | query | Id of the job to filter on |
More for modifiers in Clover
Delete modifier in other POS apps
The same call works for each of these; only the service id changes.