Method: accounts.productInputs.patch

productInput.name

string

Identifier. The name of the product. Format: accounts/{account}/productInputs/{productinput}

The {productinput} segment is a unique identifier for the product. This identifier must be unique within a merchant account and generally follows the structure: contentLanguage~feedLabel~offerId . Example: en~US~sku123 For legacy local products, the structure is: local~contentLanguage~feedLabel~offerId . Example: local~en~US~sku123

The format of the {productinput} segment in the URL is automatically detected by the server, supporting two options:

1. Encoded Format: The {productinput} segment is an unpadded base64url encoded string (RFC 4648 Section 5). The decoded string must result in the contentLanguage~feedLabel~offerId structure. This encoding MUST be used if any part of the product identifier (like offerId ) contains characters such as / , % , or ~ .

   • Example: To represent the product ID en~US~sku/123 , the {productinput} segment must be the base64url encoding of this string, which is ZW5-VVMtc2t1LzEyMw . The full resource name for the product would be accounts/123/productinputs/ZW5-VVMtc2t1LzEyMw .

2. Plain Format: The {productinput} segment is the tilde-separated string contentLanguage~feedLabel~offerId . This format is suitable only when contentLanguage , feedLabel , and offerId do not contain URL-problematic characters like / , % , or ~ .

We recommend using the Encoded Formatfor all product IDs to ensure correct parsing, especially those containing special characters. The presence of tilde ( ~ ) characters in the {productinput} segment is used to differentiate between the two formats.

Note: For calls to the v1beta version, the plain format is channel~contentLanguage~feedLabel~offerId , for example: accounts/123/productinputs/online~en~US~sku123 .