@googleapis/merchantapi 16.1.0 → 17.1.0

package/issueresolution_v1.ts

@@ -882,8 +882,7 @@ export namespace merchantapi_issueresolution_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Aggregateproductstatuses$List
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Aggregateproductstatuses$List extends StandardParameters {
     /**
      * Optional. A filter expression that filters the aggregate product statuses. Filtering is only supported by the `reporting_context` and `country` field. For example: `reporting_context = "SHOPPING_ADS" AND country = "US"`.
      */
@@ -1094,10 +1093,8 @@ export namespace merchantapi_issueresolution_v1 {
      *   const res = await merchantapi.issueresolution.renderproductissues({
      *     // Optional. The [IETF BCP-47](https://tools.ietf.org/html/bcp47) language code used to localize an issue resolution content. If not set, the result will be in default language `en-US`.
      *     languageCode: 'placeholder-value',
-     *     // Required. The name of the product to fetch issues for. Format: `accounts/{account\}/products/{product\}`
+     *     // 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`.
      *     name: 'accounts/my-account/products/my-product',
-     *     // Optional. If true, the `{product\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{product\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     *     productIdBase64UrlEncoded: 'placeholder-value',
      *     // Optional. The [IANA](https://www.iana.org/time-zones) timezone used to localize times in an issue resolution content. For example 'America/Los_Angeles'. If not set, results will use as a default UTC.
      *     timeZone: 'placeholder-value',
      *
@@ -1368,8 +1365,7 @@ export namespace merchantapi_issueresolution_v1 {
     }
   }
 
-  export interface Params$Resource$Issueresolution$Renderaccountissues
-    extends StandardParameters {
+  export interface Params$Resource$Issueresolution$Renderaccountissues extends StandardParameters {
     /**
      * Optional. The [IETF BCP-47](https://tools.ietf.org/html/bcp47) language code used to localize issue resolution content. If not set, the result will be in default language `en-US`.
      */
@@ -1388,20 +1384,15 @@ export namespace merchantapi_issueresolution_v1 {
      */
     requestBody?: Schema$RenderIssuesRequestPayload;
   }
-  export interface Params$Resource$Issueresolution$Renderproductissues
-    extends StandardParameters {
+  export interface Params$Resource$Issueresolution$Renderproductissues extends StandardParameters {
     /**
      * Optional. The [IETF BCP-47](https://tools.ietf.org/html/bcp47) language code used to localize an issue resolution content. If not set, the result will be in default language `en-US`.
      */
     languageCode?: string;
     /**
-     * Required. The name of the product to fetch issues for. Format: `accounts/{account\}/products/{product\}`
+     * 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`.
      */
     name?: string;
-    /**
-     * Optional. If true, the `{product\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{product\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     */
-    productIdBase64UrlEncoded?: boolean;
     /**
      * Optional. The [IANA](https://www.iana.org/time-zones) timezone used to localize times in an issue resolution content. For example 'America/Los_Angeles'. If not set, results will use as a default UTC.
      */
@@ -1412,8 +1403,7 @@ export namespace merchantapi_issueresolution_v1 {
      */
     requestBody?: Schema$RenderIssuesRequestPayload;
   }
-  export interface Params$Resource$Issueresolution$Triggeraction
-    extends StandardParameters {
+  export interface Params$Resource$Issueresolution$Triggeraction extends StandardParameters {
     /**
      * Optional. Language code [IETF BCP 47 syntax](https://tools.ietf.org/html/bcp47) used to localize the response. If not set, the result will be in default language `en-US`.
      */

package/issueresolution_v1beta.ts

@@ -883,8 +883,7 @@ export namespace merchantapi_issueresolution_v1beta {
     }
   }
 
-  export interface Params$Resource$Accounts$Aggregateproductstatuses$List
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Aggregateproductstatuses$List extends StandardParameters {
     /**
      * Optional. A filter expression that filters the aggregate product statuses. Filtering is only supported by the `reporting_context` and `country` field. For example: `reporting_context = "SHOPPING_ADS" AND country = "US"`.
      */
@@ -1095,10 +1094,8 @@ export namespace merchantapi_issueresolution_v1beta {
      *   const res = await merchantapi.issueresolution.renderproductissues({
      *     // Optional. The [IETF BCP-47](https://tools.ietf.org/html/bcp47) language code used to localize an issue resolution content. If not set, the result will be in default language `en-US`.
      *     languageCode: 'placeholder-value',
-     *     // Required. The name of the product to fetch issues for. Format: `accounts/{account\}/products/{product\}`
+     *     // 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`.
      *     name: 'accounts/my-account/products/my-product',
-     *     // Optional. If true, the `{product\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{product\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     *     productIdBase64UrlEncoded: 'placeholder-value',
      *     // Optional. The [IANA](https://www.iana.org/time-zones) timezone used to localize times in an issue resolution content. For example 'America/Los_Angeles'. If not set, results will use as a default UTC.
      *     timeZone: 'placeholder-value',
      *
@@ -1369,8 +1366,7 @@ export namespace merchantapi_issueresolution_v1beta {
     }
   }
 
-  export interface Params$Resource$Issueresolution$Renderaccountissues
-    extends StandardParameters {
+  export interface Params$Resource$Issueresolution$Renderaccountissues extends StandardParameters {
     /**
      * Optional. The [IETF BCP-47](https://tools.ietf.org/html/bcp47) language code used to localize issue resolution content. If not set, the result will be in default language `en-US`.
      */
@@ -1389,20 +1385,15 @@ export namespace merchantapi_issueresolution_v1beta {
      */
     requestBody?: Schema$RenderIssuesRequestPayload;
   }
-  export interface Params$Resource$Issueresolution$Renderproductissues
-    extends StandardParameters {
+  export interface Params$Resource$Issueresolution$Renderproductissues extends StandardParameters {
     /**
      * Optional. The [IETF BCP-47](https://tools.ietf.org/html/bcp47) language code used to localize an issue resolution content. If not set, the result will be in default language `en-US`.
      */
     languageCode?: string;
     /**
-     * Required. The name of the product to fetch issues for. Format: `accounts/{account\}/products/{product\}`
+     * 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`.
      */
     name?: string;
-    /**
-     * Optional. If true, the `{product\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{product\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     */
-    productIdBase64UrlEncoded?: boolean;
     /**
      * Optional. The [IANA](https://www.iana.org/time-zones) timezone used to localize times in an issue resolution content. For example 'America/Los_Angeles'. If not set, results will use as a default UTC.
      */
@@ -1413,8 +1404,7 @@ export namespace merchantapi_issueresolution_v1beta {
      */
     requestBody?: Schema$RenderIssuesRequestPayload;
   }
-  export interface Params$Resource$Issueresolution$Triggeraction
-    extends StandardParameters {
+  export interface Params$Resource$Issueresolution$Triggeraction extends StandardParameters {
     /**
      * Optional. Language code [IETF BCP 47 syntax](https://tools.ietf.org/html/bcp47) used to localize the response. If not set, the result will be in default language `en-US`.
      */

package/lfp_v1.ts

@@ -671,8 +671,7 @@ export namespace merchantapi_lfp_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Lfpinventories$Insert
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpinventories$Insert extends StandardParameters {
     /**
      * Required. The LFP provider account. Format: `accounts/{account\}`
      */
@@ -829,8 +828,7 @@ export namespace merchantapi_lfp_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Lfpmerchantstates$Get
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpmerchantstates$Get extends StandardParameters {
     /**
      * Required. The name of the state to retrieve. Format: `accounts/{account\}/lfpMerchantStates/{target_merchant\}`. For example, `accounts/123456/lfpMerchantStates/567890`.
      */
@@ -1011,8 +1009,7 @@ export namespace merchantapi_lfp_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Lfpsales$Insert
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpsales$Insert extends StandardParameters {
     /**
      * Required. The LFP provider account. Format: `accounts/{lfp_partner\}`
      */
@@ -1618,22 +1615,19 @@ export namespace merchantapi_lfp_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Lfpstores$Delete
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpstores$Delete extends StandardParameters {
     /**
      * Required. The name of the store to delete for the target merchant account. Format: `accounts/{account\}/lfpStores/{target_merchant\}~{store_code\}`
      */
     name?: string;
   }
-  export interface Params$Resource$Accounts$Lfpstores$Get
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpstores$Get extends StandardParameters {
     /**
      * Required. The name of the store to retrieve. Format: `accounts/{account\}/lfpStores/{target_merchant\}~{store_code\}`
      */
     name?: string;
   }
-  export interface Params$Resource$Accounts$Lfpstores$Insert
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpstores$Insert extends StandardParameters {
     /**
      * Required. The LFP provider account Format: `accounts/{account\}`
      */
@@ -1644,8 +1638,7 @@ export namespace merchantapi_lfp_v1 {
      */
     requestBody?: Schema$LfpStore;
   }
-  export interface Params$Resource$Accounts$Lfpstores$List
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpstores$List extends StandardParameters {
     /**
      * Optional. The maximum number of `LfpStore` resources for the given account to return. The service returns fewer than this value if the number of stores for the given account is less than the `pageSize`. The default value is 250. The maximum value is 1000; If a value higher than the maximum is specified, then the `pageSize` will default to the maximum.
      */

package/lfp_v1beta.ts

@@ -670,8 +670,7 @@ export namespace merchantapi_lfp_v1beta {
     }
   }
 
-  export interface Params$Resource$Accounts$Lfpinventories$Insert
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpinventories$Insert extends StandardParameters {
     /**
      * Required. The LFP provider account. Format: `accounts/{account\}`
      */
@@ -831,8 +830,7 @@ export namespace merchantapi_lfp_v1beta {
     }
   }
 
-  export interface Params$Resource$Accounts$Lfpmerchantstates$Get
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpmerchantstates$Get extends StandardParameters {
     /**
      * Required. The name of the state to retrieve. Format: `accounts/{account\}/lfpMerchantStates/{target_merchant\}`. For example, `accounts/123456/lfpMerchantStates/567890`.
      */
@@ -1013,8 +1011,7 @@ export namespace merchantapi_lfp_v1beta {
     }
   }
 
-  export interface Params$Resource$Accounts$Lfpsales$Insert
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpsales$Insert extends StandardParameters {
     /**
      * Required. The LFP provider account. Format: `accounts/{lfp_partner\}`
      */
@@ -1626,22 +1623,19 @@ export namespace merchantapi_lfp_v1beta {
     }
   }
 
-  export interface Params$Resource$Accounts$Lfpstores$Delete
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpstores$Delete extends StandardParameters {
     /**
      * Required. The name of the store to delete for the target merchant account. Format: `accounts/{account\}/lfpStores/{target_merchant\}~{store_code\}`
      */
     name?: string;
   }
-  export interface Params$Resource$Accounts$Lfpstores$Get
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpstores$Get extends StandardParameters {
     /**
      * Required. The name of the store to retrieve. Format: `accounts/{account\}/lfpStores/{target_merchant\}~{store_code\}`
      */
     name?: string;
   }
-  export interface Params$Resource$Accounts$Lfpstores$Insert
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpstores$Insert extends StandardParameters {
     /**
      * Required. The LFP provider account Format: `accounts/{account\}`
      */
@@ -1652,8 +1646,7 @@ export namespace merchantapi_lfp_v1beta {
      */
     requestBody?: Schema$LfpStore;
   }
-  export interface Params$Resource$Accounts$Lfpstores$List
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Lfpstores$List extends StandardParameters {
     /**
      * Optional. The maximum number of `LfpStore` resources for the given account to return. The service returns fewer than this value if the number of stores for the given account is less than the `pageSize`. The default value is 250. The maximum value is 1000; If a value higher than the maximum is specified, then the `pageSize` will default to the maximum.
      */

package/notifications_v1.ts

@@ -992,8 +992,7 @@ export namespace merchantapi_notifications_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Notificationsubscriptions$Create
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$Create extends StandardParameters {
     /**
      * Required. The merchant account that owns the new notification subscription. Format: `accounts/{account\}`
      */
@@ -1004,22 +1003,19 @@ export namespace merchantapi_notifications_v1 {
      */
     requestBody?: Schema$NotificationSubscription;
   }
-  export interface Params$Resource$Accounts$Notificationsubscriptions$Delete
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$Delete extends StandardParameters {
     /**
      * Required. The name of the notification subscription to be deleted.
      */
     name?: string;
   }
-  export interface Params$Resource$Accounts$Notificationsubscriptions$Get
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$Get extends StandardParameters {
     /**
      * Required. The `name` of the notification subscription.
      */
     name?: string;
   }
-  export interface Params$Resource$Accounts$Notificationsubscriptions$List
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$List extends StandardParameters {
     /**
      * The maximum number of notification subscriptions to return in a page. The default value for `page_size` is 100. The maximum value is `200`. Values above `200` will be coerced to `200`.
      */
@@ -1033,8 +1029,7 @@ export namespace merchantapi_notifications_v1 {
      */
     parent?: string;
   }
-  export interface Params$Resource$Accounts$Notificationsubscriptions$Patch
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$Patch extends StandardParameters {
     /**
      * Output only. The `name` of the notification configuration. Generated by the Content API upon creation of a new `NotificationSubscription`. The `account` represents the merchant ID of the merchant that owns the configuration. Format: `accounts/{account\}/notificationsubscriptions/{notification_subscription\}`
      */

package/notifications_v1beta.ts

@@ -994,8 +994,7 @@ export namespace merchantapi_notifications_v1beta {
     }
   }
 
-  export interface Params$Resource$Accounts$Notificationsubscriptions$Create
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$Create extends StandardParameters {
     /**
      * Required. The merchant account that owns the new notification subscription. Format: `accounts/{account\}`
      */
@@ -1006,22 +1005,19 @@ export namespace merchantapi_notifications_v1beta {
      */
     requestBody?: Schema$NotificationSubscription;
   }
-  export interface Params$Resource$Accounts$Notificationsubscriptions$Delete
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$Delete extends StandardParameters {
     /**
      * Required. The name of the notification subscription to be deleted.
      */
     name?: string;
   }
-  export interface Params$Resource$Accounts$Notificationsubscriptions$Get
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$Get extends StandardParameters {
     /**
      * Required. The `name` of the notification subscription.
      */
     name?: string;
   }
-  export interface Params$Resource$Accounts$Notificationsubscriptions$List
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$List extends StandardParameters {
     /**
      * The maximum number of notification subscriptions to return in a page. The default value for `page_size` is 100. The maximum value is `200`. Values above `200` will be coerced to `200`.
      */
@@ -1035,8 +1031,7 @@ export namespace merchantapi_notifications_v1beta {
      */
     parent?: string;
   }
-  export interface Params$Resource$Accounts$Notificationsubscriptions$Patch
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Notificationsubscriptions$Patch extends StandardParameters {
     /**
      * Output only. The `name` of the notification configuration. Generated by the Content API upon creation of a new `NotificationSubscription`. The `account` represents the merchant ID of the merchant that owns the configuration. Format: `accounts/{account\}/notificationsubscriptions/{notification_subscription\}`
      */

package/ordertracking_v1.ts

@@ -580,8 +580,7 @@ export namespace merchantapi_ordertracking_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Ordertrackingsignals$Create
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Ordertrackingsignals$Create extends StandardParameters {
     /**
      * Output only. The ID that uniquely identifies this order tracking signal.
      */

package/ordertracking_v1beta.ts

@@ -584,8 +584,7 @@ export namespace merchantapi_ordertracking_v1beta {
     }
   }
 
-  export interface Params$Resource$Accounts$Ordertrackingsignals$Create
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Ordertrackingsignals$Create extends StandardParameters {
     /**
      * Output only. The ID that uniquely identifies this order tracking signal.
      */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@googleapis/merchantapi",
-  "version": "16.1.0",
+  "version": "17.1.0",
   "description": "merchantapi",
   "main": "build/index.js",
   "types": "build/index.d.ts",

package/products_v1.ts

@@ -396,7 +396,7 @@ export namespace merchantapi_products_v1 {
     ratio?: number | null;
   }
   /**
-   * A message that represents loyalty program.
+   * LINT.IfChange(LoyaltyProgram) A message that represents loyalty program.
    */
   export interface Schema$LoyaltyProgram {
     /**
@@ -851,7 +851,7 @@ export namespace merchantapi_products_v1 {
      */
     structuredTitle?: Schema$StructuredTitle;
     /**
-     * Number of periods (months or years) and amount of payment per period for an item with an associated subscription contract.
+     * Number of periods (weeks, months or years) and amount of payment per period for an item with an associated subscription contract.
      */
     subscriptionCost?: Schema$SubscriptionCost;
     /**
@@ -972,7 +972,7 @@ export namespace merchantapi_products_v1 {
      */
     legacyLocal?: boolean | null;
     /**
-     * Identifier. The name of the product input. Format: `accounts/{account\}/productInputs/{productinput\}` where the last section `productinput` consists of: `content_language~feed_label~offer_id` example for product input name is `accounts/123/productInputs/en~US~sku123`. A legacy local product input name would be `accounts/123/productInputs/local~en~US~sku123`. Note: For calls to the v1beta version, the `productInput` section consists of: `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 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`.
      */
     name?: string | null;
     /**
@@ -1240,7 +1240,7 @@ export namespace merchantapi_products_v1 {
      */
     amount?: Schema$Price;
     /**
-     * The type of subscription period. Supported values are: * "`month`" * "`year`"
+     * The type of subscription period. Supported values are: * "`month`" * "`year`" * "`week`"
      */
     period?: string | null;
     /**
@@ -1325,10 +1325,8 @@ 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 resource to delete. Format: `accounts/{account\}/productInputs/{product\}` where the last section `product` consists of: `content_language~feed_label~offer_id` example for product name is `accounts/123/productInputs/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 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`.
      *     name: 'accounts/my-account/productInputs/my-productInput',
-     *     // Optional. If true, the `{productInput\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{productInput\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     *     productIdBase64UrlEncoded: 'placeholder-value',
      *   });
      *   console.log(res.data);
      *
@@ -1594,7 +1592,7 @@ export namespace merchantapi_products_v1 {
     }
 
     /**
-     * Updates the existing product input in your Merchant Center account. After inserting, updating, or deleting a product input, it may take several minutes before the processed product can be retrieved.
+     * Updates the existing product input in your Merchant Center account. The name of the product input to update is taken from the `name` field within the `ProductInput` resource. After inserting, updating, or deleting a product input, it may take several minutes before the processed product can be retrieved.
      * @example
      * ```js
      * // Before running the sample:
@@ -1626,10 +1624,8 @@ 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 input. Format: `accounts/{account\}/productInputs/{productinput\}` where the last section `productinput` consists of: `content_language~feed_label~offer_id` example for product input name is `accounts/123/productInputs/en~US~sku123`. A legacy local product input name would be `accounts/123/productInputs/local~en~US~sku123`. Note: For calls to the v1beta version, the `productInput` section consists of: `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 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`.
      *     name: 'accounts/my-account/productInputs/my-productInput',
-     *     // Optional. If true, the `{productInput\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{productInput\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     *     productIdBase64UrlEncoded: 'placeholder-value',
      *     // 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',
      *
@@ -1761,23 +1757,17 @@ export namespace merchantapi_products_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Productinputs$Delete
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Productinputs$Delete extends StandardParameters {
     /**
      * 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?: string;
     /**
-     * Required. The name of the product input resource to delete. Format: `accounts/{account\}/productInputs/{product\}` where the last section `product` consists of: `content_language~feed_label~offer_id` example for product name is `accounts/123/productInputs/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 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`.
      */
     name?: string;
-    /**
-     * Optional. If true, the `{productInput\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{productInput\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     */
-    productIdBase64UrlEncoded?: boolean;
   }
-  export interface Params$Resource$Accounts$Productinputs$Insert
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Productinputs$Insert extends StandardParameters {
     /**
      * Required. The primary or supplemental product data source name. If the product already exists and data source provided is different, then the product will be moved to a new data source. For more information, see [Create a primary data source](/merchant/api/guides/data-sources/api-sources#create-primary-data-source). Only API data sources are supported. Format: `accounts/{account\}/dataSources/{datasource\}`. For example, `accounts/123456/dataSources/104628`.
      */
@@ -1792,20 +1782,15 @@ export namespace merchantapi_products_v1 {
      */
     requestBody?: Schema$ProductInput;
   }
-  export interface Params$Resource$Accounts$Productinputs$Patch
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Productinputs$Patch extends StandardParameters {
     /**
      * 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?: string;
     /**
-     * Identifier. The name of the product input. Format: `accounts/{account\}/productInputs/{productinput\}` where the last section `productinput` consists of: `content_language~feed_label~offer_id` example for product input name is `accounts/123/productInputs/en~US~sku123`. A legacy local product input name would be `accounts/123/productInputs/local~en~US~sku123`. Note: For calls to the v1beta version, the `productInput` section consists of: `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 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`.
      */
     name?: string;
-    /**
-     * Optional. If true, the `{productInput\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{productInput\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     */
-    productIdBase64UrlEncoded?: boolean;
     /**
      * 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.
      */
@@ -1854,10 +1839,8 @@ export namespace merchantapi_products_v1 {
      *
      *   // Do the magic
      *   const res = await merchantapi.accounts.products.get({
-     *     // Required. The name of the product to retrieve. Format: `accounts/{account\}/products/{product\}` where the last section `product` consists of: `content_language~feed_label~offer_id` example for product name is `accounts/123/products/en~US~sku123`. A legacy local product name would be `accounts/123/products/local~en~US~sku123`. Note: For calls to the v1beta version, the `product` section consists of: `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 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`.
      *     name: 'accounts/my-account/products/my-product',
-     *     // Optional. If true, the `{product\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{product\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     *     productIdBase64UrlEncoded: 'placeholder-value',
      *   });
      *   console.log(res.data);
      *
@@ -2117,19 +2100,13 @@ export namespace merchantapi_products_v1 {
     }
   }
 
-  export interface Params$Resource$Accounts$Products$Get
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Products$Get extends StandardParameters {
     /**
-     * Required. The name of the product to retrieve. Format: `accounts/{account\}/products/{product\}` where the last section `product` consists of: `content_language~feed_label~offer_id` example for product name is `accounts/123/products/en~US~sku123`. A legacy local product name would be `accounts/123/products/local~en~US~sku123`. Note: For calls to the v1beta version, the `product` section consists of: `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 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`.
      */
     name?: string;
-    /**
-     * Optional. If true, the `{product\}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{product\}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.
-     */
-    productIdBase64UrlEncoded?: boolean;
   }
-  export interface Params$Resource$Accounts$Products$List
-    extends StandardParameters {
+  export interface Params$Resource$Accounts$Products$List extends StandardParameters {
     /**
      * The maximum number of products to return. The service may return fewer than this value. The maximum value is 1000; values above 1000 will be coerced to 1000. If unspecified, the default page size of 25 products will be returned.
      */