@googleapis/merchantapi 17.2.0 → 17.4.0

package/products_v1.ts

@@ -235,6 +235,19 @@ export namespace merchantapi_products_v1 {
      */
     unitCode?: string | null;
   }
+  /**
+   * The co2 emission of the vehicle.
+   */
+  export interface Schema$Co2Emissions {
+    /**
+     * The unit of the co2 emission.
+     */
+    unit?: string | null;
+    /**
+     * The co2 emission value.
+     */
+    value?: string | null;
+  }
   /**
    * A message that represents custom attributes. Exactly one of `value` or `group_values` must not be empty.
    */
@@ -253,7 +266,7 @@ export namespace merchantapi_products_v1 {
     value?: string | null;
   }
   /**
-   * The destination status of the product status.
+   * The destination status of the product status. Equivalent to `StatusPerReportingContext` in Reports API.
    */
   export interface Schema$DestinationStatus {
     /**
@@ -277,6 +290,19 @@ export namespace merchantapi_products_v1 {
    * A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); \}
    */
   export interface Schema$Empty {}
+  /**
+   * The energy consumption of the vehicle.
+   */
+  export interface Schema$EnergyConsumption {
+    /**
+     * The unit of the energy consumption.
+     */
+    unit?: string | null;
+    /**
+     * The energy consumption value.
+     */
+    value?: number | null;
+  }
   /**
    * Conditions to be met for a product to have free shipping.
    */
@@ -290,6 +316,19 @@ export namespace merchantapi_products_v1 {
      */
     priceThreshold?: Schema$Price;
   }
+  /**
+   * The fuel consumption of the vehicle.
+   */
+  export interface Schema$FuelConsumption {
+    /**
+     * The unit of the fuel consumption.
+     */
+    unit?: string | null;
+    /**
+     * The fuel consumption value.
+     */
+    value?: number | null;
+  }
   /**
    * Configuration for offer or offer-country level shipping handling cutoff time.
    */
@@ -396,7 +435,7 @@ export namespace merchantapi_products_v1 {
     ratio?: number | null;
   }
   /**
-   * LINT.IfChange(LoyaltyProgram) A message that represents loyalty program.
+   * A message that represents loyalty program.
    */
   export interface Schema$LoyaltyProgram {
     /**
@@ -428,6 +467,19 @@ export namespace merchantapi_products_v1 {
      */
     tierLabel?: string | null;
   }
+  /**
+   * The mileage of the vehicle.
+   */
+  export interface Schema$Mileage {
+    /**
+     * The unit of the mileage.
+     */
+    unit?: string | null;
+    /**
+     * The distance value.
+     */
+    value?: string | null;
+  }
   /**
    * The price represented as a number and currency.
    */
@@ -449,6 +501,10 @@ export namespace merchantapi_products_v1 {
      * Output only. The automated discounts information for the product.
      */
     automatedDiscounts?: Schema$AutomatedDiscounts;
+    /**
+     * Output only. The **unpadded base64url encoded name** of the product. Format: `accounts/{account\}/products/{product\}` where the last section `product` is the unpadded base64url encoding of the `content_language~feed_label~offer_id` name. Example: `accounts/123/products/ZW5-VVN-c2t1LzEyMw` for the decoded product name `accounts/123/products/en~US~sku/123`. This field can be used directly as input to the API methods that require the product name to be encoded if it contains special characters, for example [`GetProduct`](https://developers.google.com/merchant/api/reference/rest/products_v1/accounts.products/get).
+     */
+    base64EncodedName?: string | null;
     /**
      * Output only. The two-letter [ISO 639-1](http://en.wikipedia.org/wiki/ISO_639-1) language code for the product.
      */
@@ -530,6 +586,10 @@ export namespace merchantapi_products_v1 {
      * The day a pre-ordered product becomes available for delivery, in [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) format.
      */
     availabilityDate?: string | null;
+    /**
+     * The [body style](https://support.google.com/google-ads/answer/14157085) of the vehicle.
+     */
+    bodyStyle?: string | null;
     /**
      * [Brand](https://support.google.com/merchants/answer/6324351) of the item. For example, "Google".
      */
@@ -546,10 +606,18 @@ export namespace merchantapi_products_v1 {
      * Product Certifications, for example for energy efficiency labeling of products recorded in the [EU EPREL](https://eprel.ec.europa.eu/screen/home) database. See the [Help Center](https://support.google.com/merchants/answer/13528839) article for more information.
      */
     certifications?: Schema$ProductCertification[];
+    /**
+     * Whether the vehicle is OEM [certified pre-owned](https://support.google.com/google-ads/answer/14156475).
+     */
+    certifiedPreOwned?: boolean | null;
     /**
      * Extra fields to export to the Cloud Retail program.
      */
     cloudExportAdditionalProperties?: Schema$CloudExportAdditionalProperties[];
+    /**
+     * The [co2 emission](https://support.google.com/google-ads/answer/14546146) of the vehicle.
+     */
+    co2Emissions?: Schema$Co2Emissions;
     /**
      * [Color](https://support.google.com/merchants/answer/6324487) of the item. For example, "red".
      */
@@ -582,6 +650,10 @@ export namespace merchantapi_products_v1 {
      * [Custom label 4](https://support.google.com/merchants/answer/6324473) for custom grouping of items in a Shopping campaign.
      */
     customLabel4?: string | null;
+    /**
+     * The date the vehicle was first registered. Format: `YYYY-MM`. See the [Date first registered](https://support.google.com/google-ads/answer/14546138) for more information.
+     */
+    dateFirstRegistered?: string | null;
     /**
      * Description of the item.
      */
@@ -610,10 +682,26 @@ export namespace merchantapi_products_v1 {
      * Offer margin for dynamic remarketing campaigns. For more information, see [Display ads attribute](https://support.google.com/merchants/answer/6069387).
      */
     displayAdsValue?: number | null;
+    /**
+     * The [electric range](https://support.google.com/google-ads/answer/15162232) of the vehicle in miles/kms.
+     */
+    electricRange?: Schema$Mileage;
+    /**
+     * The [emission standard](https://support.google.com/google-ads/answer/14869021) of the vehicle.
+     */
+    emissionsStandard?: string | null;
+    /**
+     * The [energy consumption](https://support.google.com/google-ads/answer/14546149) of the vehicle.
+     */
+    energyConsumption?: Schema$EnergyConsumption;
     /**
      * The [energy efficiency class](https://support.google.com/merchants/answer/7562785) as defined in EU directive 2010/30/EU.
      */
     energyEfficiencyClass?: string | null;
+    /**
+     * The [engine](https://support.google.com/google-ads/answer/14156068) type of the vehicle.
+     */
+    engine?: string | null;
     /**
      * The list of destinations to exclude for this target (corresponds to unchecked check boxes in Merchant Center). For more information, see [Excluded destination](https://support.google.com/merchants/answer/6324486). Note: We recommend setting destinations on datasources level for most use cases. Use this field within products to only setup exceptions.
      */
@@ -630,6 +718,14 @@ export namespace merchantapi_products_v1 {
      * Conditions to be met for a product to have free shipping.
      */
     freeShippingThreshold?: Schema$FreeShippingThreshold[];
+    /**
+     * The [fuel consumption](https://support.google.com/google-ads/answer/14543580) of the vehicle.
+     */
+    fuelConsumption?: Schema$FuelConsumption;
+    /**
+     * The fuel consumption of the vehicle when the hybrid battery is discharged. See the [Help Center article](https://support.google.com/google-ads/answer/15162033) for more information.
+     */
+    fuelConsumptionDischargedBattery?: Schema$FuelConsumption;
     /**
      * Target [gender](https://support.google.com/merchants/answer/6324479) of the item.
      */
@@ -639,7 +735,7 @@ export namespace merchantapi_products_v1 {
      */
     googleProductCategory?: string | null;
     /**
-     * Global Trade Item Numbers ([GTIN](https://support.google.com/merchants/answer/188494#gtin)) of the item. You can provide up to 10 GTINs.
+     * Global Trade Item Numbers ([GTIN](https://support.google.com/merchants/answer/6324461)) of the item. You can provide up to 10 GTINs.
      */
     gtins?: string[] | null;
     /**
@@ -706,6 +802,10 @@ export namespace merchantapi_products_v1 {
      * Maximum retail price (MRP) of the item. Applicable to India only.
      */
     maximumRetailPrice?: Schema$Price;
+    /**
+     * The number of miles/kms on the vehicle. See the [Mileage](https://support.google.com/google-ads/answer/14156166) for more information.
+     */
+    mileage?: Schema$Mileage;
     /**
      * The [energy efficiency class](https://support.google.com/merchants/answer/7562785) as defined in EU directive 2010/30/EU.
      */
@@ -714,6 +814,10 @@ export namespace merchantapi_products_v1 {
      * Minimal product handling time (in business days).
      */
     minHandlingTime?: string | null;
+    /**
+     * The [minimum value](https://support.google.com/merchants/answer/16989009) in the cart before a customer can initiate checkout. Supports multiple minimum order values. Different minimum order values can be specified per country, service and surface. Maximum entries: 100.
+     */
+    minimumOrderValues?: Schema$ProductMinimumOrderValue[];
     /**
      * URL for the mobile-optimized version of your item's landing page.
      */
@@ -723,7 +827,11 @@ export namespace merchantapi_products_v1 {
      */
     mobileLinkTemplate?: string | null;
     /**
-     * Manufacturer Part Number ([MPN](https://support.google.com/merchants/answer/188494#mpn)) of the item.
+     * The [Model](https://support.google.com/google-ads/answer/14154511) of the vehicle, such as `LX`, `EX`, and others.
+     */
+    model?: string | null;
+    /**
+     * Manufacturer Part Number ([MPN](https://support.google.com/merchants/answer/6324482)) of the item.
      */
     mpn?: string | null;
     /**
@@ -782,6 +890,10 @@ export namespace merchantapi_products_v1 {
      * The unique ID of a promotion.
      */
     promotionIds?: string[] | null;
+    /**
+     * The return label of the product, used to group products in account-level return policies. Max. 100 characters. For more information, see [Return policy label](https://support.google.com/merchants/answer/9445425).
+     */
+    returnPolicyLabel?: string | null;
     /**
      * Advertised sale price of the item.
      */
@@ -807,7 +919,7 @@ export namespace merchantapi_products_v1 {
      */
     shippingHeight?: Schema$ShippingDimension;
     /**
-     * The shipping label of the product, used to group product in account-level shipping rules.
+     * The shipping label of the product, used to group products in account-level shipping rules. Max. 100 characters. For more information, see [Shipping label](https://support.google.com/merchants/answer/6324504).
      */
     shippingLabel?: string | null;
     /**
@@ -866,6 +978,10 @@ export namespace merchantapi_products_v1 {
      * The transit time label of the product, used to group product in account-level transit time tables.
      */
     transitTimeLabel?: string | null;
+    /**
+     * The [Trim](https://support.google.com/google-ads/answer/14154176) of the vehicle model, such as `S`, `SV`, `SL` and others.
+     */
+    trim?: string | null;
     /**
      * The preference of the denominator of the unit price.
      */
@@ -874,10 +990,46 @@ export namespace merchantapi_products_v1 {
      * The measure and dimension of an item.
      */
     unitPricingMeasure?: Schema$UnitPricingMeasure;
+    /**
+     * The all-in advertised price for a vehicle, which includes costs for the following – any accessories attached to the vehicle, environmental levies, extra warranty, fuel, freight, pre-delivery inspection (PDI), dealer fees for handling licensing, provincial regulatory fees, miscellaneous dealer charges for security etching and nitrogen tire fill, and factory-to-customer or dealer-to-customer discounts or incentives. See the [Vehicle all-in price](https://support.google.com/google-ads/answer/14156981) for more information.
+     */
+    vehicleAllInPrice?: Schema$Price;
+    /**
+     * The miscellaneous expenses like insurance and registration fees of the vehicle. See the [Vehicle expenses](https://support.google.com/google-ads/answer/15957154) for more information.
+     */
+    vehicleExpenses?: Schema$Price;
+    /**
+     * Whether the vehicle is sold with mandatory inspection and maintenance performed before delivery. See the [Vehicle mandatory inspection included](https://support.google.com/google-ads/answer/15956630) for more information.`
+     */
+    vehicleMandatoryInspectionIncluded?: boolean | null;
+    /**
+     * The MSRP (Manufacturer Suggested Retail Price) for the vehicle in its current configuration. See the [Vehicle MSRP](https://support.google.com/google-ads/answer/14154171) for more information.
+     */
+    vehicleMsrp?: Schema$Price;
+    /**
+     * The [price type](https://support.google.com/google-ads/answer/14592783) of the vehicle.
+     */
+    vehiclePriceType?: string | null;
+    /**
+     * Optional. A list of video URLs for the item. Use this attribute to provide more visuals for your product beyond your image attributes. See the [Help Center article](https://support.google.com/merchants/answer/15216925) for more information.
+     */
+    videoLinks?: string[] | null;
+    /**
+     * The [Vehicle Identification Number (VIN)](https://support.google.com/google-ads/answer/14154510) of the vehicle.
+     */
+    vin?: string | null;
     /**
      * URL of the 3D image of the item. See the [Help Center article](https://support.google.com/merchants/answer/13674896) for more information.
      */
     virtualModelLink?: string | null;
+    /**
+     * The [warranty](https://support.google.com/google-ads/answer/15957626) of the vehicle.
+     */
+    warranty?: Schema$Warranty;
+    /**
+     * The [Year](https://support.google.com/google-ads/answer/14152816) of the vehicle model.
+     */
+    year?: string | null;
   }
   /**
    * Product [certification](https://support.google.com/merchants/answer/13528839), initially introduced for EU energy efficiency labeling compliance using the EU EPREL database.
@@ -955,6 +1107,14 @@ export namespace merchantapi_products_v1 {
    * This resource represents input data you submit for a product, not the processed product that you see in Merchant Center, in Shopping ads, or across Google surfaces. Product inputs, rules and supplemental data source data are combined to create the processed Product. For more information, see [Manage products](/merchant/api/guides/products/overview). Required product input attributes to pass data validation checks are primarily defined in the [Products Data Specification](https://support.google.com/merchants/answer/188494). The following attributes are required: feedLabel, contentLanguage and offerId. After inserting, updating, or deleting a product input, it may take several minutes before the processed product can be retrieved. All fields in the product input and its sub-messages match the English name of their corresponding attribute in the [Products Data Specification](https://support.google.com/merchants/answer/188494) with [some exceptions](https://support.google.com/merchants/answer/7052112). The following reference documentation lists the field names in the **camelCase** casing style while the Products Data Specification lists the names in the **snake_case** casing style.
    */
   export interface Schema$ProductInput {
+    /**
+     * Output only. The **unpadded base64url encoded name** of the product input. Format: `accounts/{account\}/productInputs/{productinput\}` where the last section `productinput` is the unpadded base64url encoding of the `content_language~feed_label~offer_id` name. Example: `accounts/123/productInputs/ZW5-VVN-c2t1LzEyMw` for the decoded product input name `accounts/123/productInputs/en~US~sku/123`. This field can be used directly as input to the API methods that require the product input name to be encoded if it contains special characters, for example [`GetProductInput`](https://developers.google.com/merchant/api/reference/rest/products_v1/accounts.productInputs/get).
+     */
+    base64EncodedName?: string | null;
+    /**
+     * Output only. The **unpadded base64url encoded name** of the processed product. Format: `accounts/{account\}/products/{product\}` where the last section `product` is the unpadded base64url encoding of the `content_language~feed_label~offer_id` name. Example: `accounts/123/products/ZW5-VVN-c2t1LzEyMw` for the decoded product name `accounts/123/products/en~US~sku/123`. This field can be used directly as input to the API methods that require the product name to be encoded if it contains special characters, for example [`GetProduct`](https://developers.google.com/merchant/api/reference/rest/products_v1/accounts.products/get).
+     */
+    base64EncodedProduct?: string | null;
     /**
      * Required. Immutable. The two-letter [ISO 639-1](http://en.wikipedia.org/wiki/ISO_639-1) language code for the product.
      */
@@ -972,7 +1132,7 @@ export namespace merchantapi_products_v1 {
      */
     legacyLocal?: boolean | null;
     /**
-     * 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) 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 `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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~content_language~feed_label~offer_id`, for example: `accounts/123/productinputs/online~en~US~sku123`.
+     * 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{productinput\}` segment must be the unpadded base64url encoding of this string, which is `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be `accounts/123/productInputs/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{productinput\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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.
      */
     name?: string | null;
     /**
@@ -1000,6 +1160,10 @@ export namespace merchantapi_products_v1 {
      * The amount the buyer has to pay per month.
      */
     amount?: Schema$Price;
+    /**
+     * Optional. Annual percentage rate for `credit_type` finance
+     */
+    annualPercentageRate?: number | null;
     /**
      * Type of installment payments.
      */
@@ -1012,6 +1176,31 @@ export namespace merchantapi_products_v1 {
      * The number of installments the buyer has to pay.
      */
     months?: string | null;
+    /**
+     * Optional. Total amount the buyer has to pay, including interest.
+     */
+    totalAmount?: Schema$Price;
+  }
+  /**
+   * The minimum order value in the cart before the checkout is permitted.
+   */
+  export interface Schema$ProductMinimumOrderValue {
+    /**
+     * Required. The [CLDR territory code](http://www.unicode.org/repos/cldr/tags/latest/common/main/en.xml) of the country to which an item will ship.
+     */
+    country?: string | null;
+    /**
+     * Required. The minimum cart or basket value before the checkout is permitted.
+     */
+    price?: Schema$Price;
+    /**
+     * A free-form description of the service class or delivery speed. This should match the service value set for the Shipping attribute. See service.
+     */
+    service?: string | null;
+    /**
+     * The surface to which the minimum order value applies. Defaults to `ONLINE_LOCAL` if not configured.
+     */
+    surface?: string | null;
   }
   /**
    * The status of a product, data validation issues, that is, information about a product computed asynchronously.
@@ -1133,6 +1322,14 @@ export namespace merchantapi_products_v1 {
      * The numeric ID of a location that the shipping rate applies to as defined in the [AdWords API](https://developers.google.com/adwords/api/docs/appendix/geotargeting).
      */
     locationId?: string | null;
+    /**
+     * Optional. The label of the [loyalty program](https://support.google.com/merchants/answer/6324484). Must match one of the program labels set in loyalty_programs. When set (in combination with [loyalty_tier_label](https://support.google.com/merchants/answer/6324484)), this shipping option is only applicable to loyalty program members of the specified tier.
+     */
+    loyaltyProgramLabel?: string | null;
+    /**
+     * Optional. The label of the [loyalty tier](https://support.google.com/merchants/answer/6324484) within the loyalty program. Must match one of the tiers set in the loyalty_programs. When set (in combination with [loyalty_program_label](https://support.google.com/merchants/answer/6324484)), this shipping option is only applicable to loyalty program members of the specified tier.
+     */
+    loyaltyTierLabel?: string | null;
     /**
      * Maximum handling time (inclusive) between when the order is received and shipped in business days. 0 means that the order is shipped on the same day as it is received if it happens before the cut-off time. Both maxHandlingTime and maxTransitTime are required if providing shipping speeds. minHandlingTime is optional if maxHandlingTime is present.
      */
@@ -1274,6 +1471,19 @@ export namespace merchantapi_products_v1 {
      */
     value?: number | null;
   }
+  /**
+   * The warranty of the vehicle.
+   */
+  export interface Schema$Warranty {
+    /**
+     * The warranty duration in months.
+     */
+    duration?: string | null;
+    /**
+     * The warranty mileage.
+     */
+    mileage?: Schema$Mileage;
+  }
 
   export class Resource$Accounts {
     context: APIRequestContext;
@@ -1325,7 +1535,7 @@ export namespace merchantapi_products_v1 {
      *   const res = await merchantapi.accounts.productInputs.delete({
      *     // Required. The primary or supplemental data source from which the product input should be deleted. Format: `accounts/{account\}/dataSources/{datasource\}`. For example, `accounts/123456/dataSources/104628`.
      *     dataSource: 'placeholder-value',
-     *     // Required. The name of the product input to delete. 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) 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 `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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~content_language~feed_label~offer_id`, for example: `accounts/123/productinputs/online~en~US~sku123`.
+     *     // Required. The name of the product input to delete. 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{productInput\}` segment must be the unpadded base64url encoding of this string, which is `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be `accounts/123/productInputs/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{productInput\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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.
      *     name: 'accounts/my-account/productInputs/my-productInput',
      *   });
      *   console.log(res.data);
@@ -1469,6 +1679,8 @@ export namespace merchantapi_products_v1 {
      *     requestBody: {
      *       // request body parameters
      *       // {
+     *       //   "base64EncodedName": "my_base64EncodedName",
+     *       //   "base64EncodedProduct": "my_base64EncodedProduct",
      *       //   "contentLanguage": "my_contentLanguage",
      *       //   "customAttributes": [],
      *       //   "feedLabel": "my_feedLabel",
@@ -1485,6 +1697,8 @@ export namespace merchantapi_products_v1 {
      *
      *   // Example response
      *   // {
+     *   //   "base64EncodedName": "my_base64EncodedName",
+     *   //   "base64EncodedProduct": "my_base64EncodedProduct",
      *   //   "contentLanguage": "my_contentLanguage",
      *   //   "customAttributes": [],
      *   //   "feedLabel": "my_feedLabel",
@@ -1624,7 +1838,7 @@ export namespace merchantapi_products_v1 {
      *   const res = await merchantapi.accounts.productInputs.patch({
      *     // Required. The primary or supplemental product data source where `data_source` name identifies the product input to be updated. Only API data sources are supported. Format: `accounts/{account\}/dataSources/{datasource\}`. For example, `accounts/123456/dataSources/104628`.
      *     dataSource: 'placeholder-value',
-     *     // 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) 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 `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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~content_language~feed_label~offer_id`, for example: `accounts/123/productinputs/online~en~US~sku123`.
+     *     // 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{productinput\}` segment must be the unpadded base64url encoding of this string, which is `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be `accounts/123/productInputs/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{productinput\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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.
      *     name: 'accounts/my-account/productInputs/my-productInput',
      *     // Optional. The list of product attributes to be updated. If the update mask is omitted, then it is treated as implied field mask equivalent to all fields that are populated (have a non-empty value). Attributes specified in the update mask without a value specified in the body will be deleted from the product. Update mask can only be specified for top level fields in attributes and custom attributes. To specify the update mask for custom attributes you need to add the `custom_attribute.` prefix. Providing special "*" value for full product replacement is not supported.
      *     updateMask: 'placeholder-value',
@@ -1633,6 +1847,8 @@ export namespace merchantapi_products_v1 {
      *     requestBody: {
      *       // request body parameters
      *       // {
+     *       //   "base64EncodedName": "my_base64EncodedName",
+     *       //   "base64EncodedProduct": "my_base64EncodedProduct",
      *       //   "contentLanguage": "my_contentLanguage",
      *       //   "customAttributes": [],
      *       //   "feedLabel": "my_feedLabel",
@@ -1649,6 +1865,8 @@ export namespace merchantapi_products_v1 {
      *
      *   // Example response
      *   // {
+     *   //   "base64EncodedName": "my_base64EncodedName",
+     *   //   "base64EncodedProduct": "my_base64EncodedProduct",
      *   //   "contentLanguage": "my_contentLanguage",
      *   //   "customAttributes": [],
      *   //   "feedLabel": "my_feedLabel",
@@ -1763,7 +1981,7 @@ export namespace merchantapi_products_v1 {
      */
     dataSource?: string;
     /**
-     * Required. The name of the product input to delete. 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) 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 `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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~content_language~feed_label~offer_id`, for example: `accounts/123/productinputs/online~en~US~sku123`.
+     * Required. The name of the product input to delete. 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{productInput\}` segment must be the unpadded base64url encoding of this string, which is `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be `accounts/123/productInputs/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{productInput\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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.
      */
     name?: string;
   }
@@ -1788,7 +2006,7 @@ export namespace merchantapi_products_v1 {
      */
     dataSource?: 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) 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 `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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~content_language~feed_label~offer_id`, for example: `accounts/123/productinputs/online~en~US~sku123`.
+     * 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: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. 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 `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{productinput\}` segment must be the unpadded base64url encoding of this string, which is `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be `accounts/123/productInputs/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{productinput\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for 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.
      */
     name?: string;
     /**
@@ -1839,7 +2057,7 @@ export namespace merchantapi_products_v1 {
      *
      *   // Do the magic
      *   const res = await merchantapi.accounts.products.get({
-     *     // Required. The name of the product. Format: `accounts/{account\}/products/{product\}` The `{product\}` segment is a unique identifier for the product. This identifier must be unique within a merchant account and generally follows the structure: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. Example: `local~en~US~sku123` The format of the `{product\}` segment in the URL is automatically detected by the server, supporting two options: 1. **Encoded Format**: The `{product\}` segment is an unpadded base64url encoded string (RFC 4648 Section 5). The decoded string must result in the `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{product\}` segment must be the base64url encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full resource name for the product would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw`. 2. **Plain Format**: The `{product\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for all product IDs to ensure correct parsing, especially those containing special characters. The presence of tilde (`~`) characters in the `{product\}` segment is used to differentiate between the two formats. Note: For calls to the v1beta version, the plain format is `channel~content_language~feed_label~offer_id`, for example: `accounts/123/products/online~en~US~sku123`.
+     *     // Required. The name of the product. Format: `accounts/{account\}/products/{product\}` The `{product\}` segment is a unique identifier for the product. This identifier must be unique within a merchant account and generally follows the structure: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. Example: `local~en~US~sku123` The format of the `{product\}` segment in the URL is automatically detected by the server, supporting two options: 1. **Encoded Format**: The `{product\}` segment is an unpadded base64url encoded string (RFC 4648 Section 5). The decoded string must result in the `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{product\}` segment must be the unpadded base64url encoding of this string, which is `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be `accounts/123/products/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{product\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for all product IDs to ensure correct parsing, especially those containing special characters. The presence of tilde (`~`) characters in the `{product\}` segment is used to differentiate between the two formats. Note: For calls to the v1beta version, the plain format is `channel~content_language~feed_label~offer_id`, for example: `accounts/123/products/online~en~US~sku123`.
      *     name: 'accounts/my-account/products/my-product',
      *   });
      *   console.log(res.data);
@@ -1847,6 +2065,7 @@ export namespace merchantapi_products_v1 {
      *   // Example response
      *   // {
      *   //   "automatedDiscounts": {},
+     *   //   "base64EncodedName": "my_base64EncodedName",
      *   //   "contentLanguage": "my_contentLanguage",
      *   //   "customAttributes": [],
      *   //   "dataSource": "my_dataSource",
@@ -2102,7 +2321,7 @@ export namespace merchantapi_products_v1 {
 
   export interface Params$Resource$Accounts$Products$Get extends StandardParameters {
     /**
-     * Required. The name of the product. Format: `accounts/{account\}/products/{product\}` The `{product\}` segment is a unique identifier for the product. This identifier must be unique within a merchant account and generally follows the structure: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. Example: `local~en~US~sku123` The format of the `{product\}` segment in the URL is automatically detected by the server, supporting two options: 1. **Encoded Format**: The `{product\}` segment is an unpadded base64url encoded string (RFC 4648 Section 5). The decoded string must result in the `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{product\}` segment must be the base64url encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full resource name for the product would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw`. 2. **Plain Format**: The `{product\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for all product IDs to ensure correct parsing, especially those containing special characters. The presence of tilde (`~`) characters in the `{product\}` segment is used to differentiate between the two formats. Note: For calls to the v1beta version, the plain format is `channel~content_language~feed_label~offer_id`, for example: `accounts/123/products/online~en~US~sku123`.
+     * Required. The name of the product. Format: `accounts/{account\}/products/{product\}` The `{product\}` segment is a unique identifier for the product. This identifier must be unique within a merchant account and generally follows the structure: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the structure is: `local~content_language~feed_label~offer_id`. Example: `local~en~US~sku123` The format of the `{product\}` segment in the URL is automatically detected by the server, supporting two options: 1. **Encoded Format**: The `{product\}` segment is an unpadded base64url encoded string (RFC 4648 Section 5). The decoded string must result in the `content_language~feed_label~offer_id` structure. This encoding MUST be used if any part of the product identifier (like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{product\}` segment must be the unpadded base64url encoding of this string, which is `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be `accounts/123/products/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{product\}` segment is the tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format** for all product IDs to ensure correct parsing, especially those containing special characters. The presence of tilde (`~`) characters in the `{product\}` segment is used to differentiate between the two formats. Note: For calls to the v1beta version, the plain format is `channel~content_language~feed_label~offer_id`, for example: `accounts/123/products/online~en~US~sku123`.
      */
     name?: string;
   }