Update a catalog entry
Authentication
Path parameters
Headers
API version to use (optional, defaults to latest). Supported values: 1.0.0, 1.1.0.
Request
ERP Vendor id from ERP/accounting system
Accepted but has no effect. On every save, catalog_unique_key is unconditionally regenerated from the company’s configured key format (see catalog_unique_key on the create request) — a value submitted here is not stored and does not rename or override the entry’s key.
Deprecated: use item_name instead. This field will be removed in a future API version.
Buying format distinguishing multiple purchasing formats for the same item (e.g., ‘CASE’, ‘EACH’). Used as part of the composite unique key for integrations that differentiate catalog entries by buying format. Optional — null or omitted for integrations that do not use buying format.
Optional. Human-readable vendor name attached to erp_vendor_id, sourced from the originating system. Note: reads return the resolved vendor name for the entry, which may come from upstream ERP/sync sources rather than this field. Omit to leave unchanged; pass empty string to clear.
POS dimensions for this catalog entry — these are point-of-sale system dimensions, separate from ERP/accounting dimensions and not validated against your accounting configuration. Input Structure: a list of objects, each with one dimension-type key (value = dimension name) plus an optional ‘code’, e.g. [{“DEPARTMENT”: “Marketing”, “code”: “321654”}]. Dimension-type keys are uppercased in the response regardless of the case submitted. Omit the field or pass null to leave dimensions unchanged.

