Square Connect API V2：能否对目录对象执行部分更新？

Absolutely, Square Connect API V2 does support partial updates for catalog objects—you don’t have to maintain and send full object data every time you want to make a change. Let’s break down the best ways to handle this, especially for your scenario with modifier_list_info:

1. Use the UpdateCatalogObject endpoint (recommended) #

This endpoint is built specifically for partial updates. When you call it, you only need to send three key pieces of information:

• The ID of the catalog object you want to modify
• The specific fields you need to update
• The object type (e.g., ITEM)

Any fields you don’t include in the request will stay exactly as they are—so your modifier_list_info won’t get cleared out. Here’s a quick example of what the request body might look like if you only want to update an item’s name:

{
  "id": "your-item-id-123",
  "object": {
    "type": "ITEM",
    "item_data": {
      "name": "Freshly Updated Coffee"
      // No modifier_list_info here? No problem—it remains unchanged
    }
  }
}

2. If you must use UpsertCatalogObject #

Upsert works by either creating a new object or replacing an existing one entirely. That’s why omitting modifier_list_info clears it out—Square interprets the missing field as a request to set it to null. If you need to use upsert, you have two workarounds:

• First fetch the existing object: Call RetrieveCatalogObject to get the full current state of the item, modify only the fields you want to change, then pass the complete object to upsert. Just note this adds two API calls and potential concurrency risks if the object is updated between fetch and upsert.
• Explicitly include the existing modifier_list_info: If you already store this data locally, include it in the upsert request alongside the fields you’re updating. But this defeats the purpose of avoiding maintenance, so the UpdateCatalogObject endpoint is far more practical here.

To sum it up: Stick with UpdateCatalogObject for partial updates—it’s the cleanest, most efficient way to avoid accidentally clearing fields like modifier_list_info while making targeted changes.

内容的提问来源于stack exchange，提问作者RaresMan