openintegration200+ connectors

Create item in Clover

POS API · write, waits for approval · 100% field coverage

Your agent can create item 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.

Paste into Claude Code, Cursor or any coding agent.

The call

POST https://unify.apideck.com/pos/items

Headers: x-apideck-service-id: clover, plus your app id and the customer's consumer id. Apideck MCP tool: pos-items-add. Agent operation id: unified.pos.itemsAdd.

Body fields

FieldTypeDescription
idstring
idempotency_keystringA value you specify that uniquely identifies this request among requests you have sent.
name · requiredstring
descriptionstring
abbreviationstring
product_typestring
price_amountnumber
pricing_typestring
price_currencystringIndicates the associated currency for an amount of money. Values correspond to [ISO 4217](https://en.wikipedia.org/wiki/
costnumber
tax_idsarrayA list of Tax IDs for the product.
is_revenuebooleanTrue if this item should be counted as revenue. For example, gift cards and donations would not be counted as revenue.
use_default_tax_ratesboolean
absent_at_location_idsarrayA list of locations where the object is not present, even if present_at_all_locations is true. This can include location
present_at_all_locationsboolean
available_for_pickupboolean
available_onlineboolean
skustringSKU of the item
codestringProduct code, e.g. UPC or EAN
categoriesarray
optionsarrayList of options pertaining to this item's attribute variation
variationsarray
modifier_groupsarray
availableboolean
hiddenboolean
deletedbooleanFlag to indicate if the object is deleted.

More for items in Clover

list_itemsget_itemupdate_itemdelete_item

Create item in other POS apps

The same call works for each of these; only the service id changes.

Square