@googleapis/merchantapi 18.0.0 → 19.0.0

package/inventories_v1.ts

@@ -124,6 +124,23 @@ export namespace merchantapi_inventories_v1 {
     }
   }
 
+  /**
+   * A message that represents custom attributes. Exactly one of `value` or `group_values` must not be empty.
+   */
+  export interface Schema$CustomAttribute {
+    /**
+     * Subattributes within this attribute group. If `group_values` is not empty, `value` must be empty.
+     */
+    groupValues?: Schema$CustomAttribute[];
+    /**
+     * The name of the attribute.
+     */
+    name?: string | null;
+    /**
+     * The value of the attribute. If `value` is not empty, `group_values` must be empty.
+     */
+    value?: string | null;
+  }
   /**
    * 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); \}
    */
@@ -233,10 +250,18 @@ export namespace merchantapi_inventories_v1 {
      * [Availability](https://support.google.com/merchants/answer/3061342) of the product at this store.
      */
     availability?: string | null;
+    /**
+     * Optional. A list of custom (merchant-provided) attributes. It can also be used for submitting any attribute of the data specification in its generic form (for example, `{ "name": "size type", "value": "regular" \}`). This is useful for submitting attributes not explicitly exposed by the API. Maximum allowed number of characters for each custom attribute is 10240 (represents sum of characters for name and value). Maximum 2500 custom attributes can be set, with total size of 102.4kB. Underscores in custom attribute names are replaced by spaces upon insertion.
+     */
+    customAttributes?: Schema$CustomAttribute[];
     /**
      * Optional. Location of the product inside the store. Maximum length is 20 bytes.
      */
     instoreProductLocation?: string | null;
+    /**
+     * Optional. Specifies a label associated with the shipping for the `LocalInventory` resource. Can be used to group local shipping services to this particular inventory item. For accepted field format, see the [Local delivery](https://support.google.com/merchants/answer/14819809#localdelivery)
+     */
+    localShippingLabel?: string | null;
     /**
      * Optional. An optional list of loyalty programs containing applicable loyalty member prices for this product at this store. This field is used to show store-specific member prices on Local Inventory Ads (LIA). To use this, the loyalty program must be configured in Google Merchant Center. The benefits provided must match the merchant's website and be clear to members. This is only applicable for merchants in supported countries. See [Loyalty program](https://support.google.com/merchants/answer/12922446) for details on supported countries and loyalty program configuration. For local inventory specific details, see the [Local inventory data specification](https://support.google.com/merchants/answer/3061342).
      */
@@ -507,8 +532,7 @@ export namespace merchantapi_inventories_v1 {
         | BodyResponseCallback<Schema$Empty>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$Empty>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$Empty> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$Empty>>
@@ -982,8 +1006,7 @@ export namespace merchantapi_inventories_v1 {
         | BodyResponseCallback<Schema$Empty>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$Empty>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$Empty> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$Empty>>

package/inventories_v1beta.ts

@@ -473,8 +473,7 @@ export namespace merchantapi_inventories_v1beta {
         | BodyResponseCallback<Schema$Empty>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$Empty>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$Empty> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$Empty>>
@@ -964,8 +963,7 @@ export namespace merchantapi_inventories_v1beta {
         | BodyResponseCallback<Schema$Empty>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$Empty>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$Empty> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$Empty>>

package/issueresolution_v1.ts

@@ -587,7 +587,7 @@ export namespace merchantapi_issueresolution_v1 {
      */
     impact?: Schema$Impact;
     /**
-     * Details of the issue as a pre-rendered HTML. HTML elements contain CSS classes that can be used to customize the style of the content. Always sanitize the HTML before embedding it directly to your application. The sanitizer needs to allow basic HTML tags, such as: `div`, `span`, `p`, `a`, `ul`, `li`, `table`, `tr`, `td`. For example, you can use [DOMPurify](https://www.npmjs.com/package/dompurify). CSS classes: * `issue-detail` - top level container for the detail of the issue * `callout-banners` - section of the `issue-detail` with callout banners * `callout-banner` - single callout banner, inside `callout-banners` * `callout-banner-info` - callout with important information (default) * `callout-banner-warning` - callout with a warning * `callout-banner-error` - callout informing about an error (most severe) * `issue-content` - section of the `issue-detail`, contains multiple `content-element` * `content-element` - content element such as a list, link or paragraph, inside `issue-content` * `root-causes` - unordered list with items describing root causes of the issue, inside `issue-content` * `root-causes-intro` - intro text before the `root-causes` list, inside `issue-content` * `segment` - section of the text, `span` inside paragraph * `segment-attribute` - section of the text that represents a product attribute, for example 'image\_link' * `segment-literal` - section of the text that contains a special value, for example '0-1000 kg' * `segment-bold` - section of the text that should be rendered as bold * `segment-italic` - section of the text that should be rendered as italic * `tooltip` - used on paragraphs that should be rendered with a tooltip. A section of the text in such a paragraph will have a class `tooltip-text` and is intended to be shown in a mouse over dialog. If the style is not used, the `tooltip-text` section would be shown on a new line, after the main part of the text. * `tooltip-text` - marks a section of the text within a `tooltip`, that is intended to be shown in a mouse over dialog. * `tooltip-icon` - marks a section of the text within a `tooltip`, that can be replaced with a tooltip icon, for example '?' or 'i'. By default, this section contains a `br` tag, that is separating the main text and the tooltip text when the style is not used. * `tooltip-style-question` - the tooltip shows helpful information, can use the '?' as an icon. * `tooltip-style-info` - the tooltip adds additional information fitting to the context, can use the 'i' as an icon. * `content-moderation` - marks the paragraph that explains how the issue was identified. * `new-element` - Present for new elements added to the pre-rendered content in the future. To make sure that a new content element does not break your style, you can hide everything with this class.
+     * Details of the issue as a pre-rendered HTML. HTML elements contain CSS classes that can be used to customize the style of the content. Always sanitize the HTML before embedding it directly to your application. The sanitizer needs to allow basic HTML tags, such as: `div`, `span`, `p`, `a`, `ul`, `li`, `table`, `tr`, `td`. For example, you can use [DOMPurify](https://www.npmjs.com/package/dompurify). CSS classes: * `issue-detail` - top level container for the detail of the issue * `callout-banners` - section of the `issue-detail` with callout banners * `callout-banner` - single callout banner, inside `callout-banners` * `callout-banner-info` - callout with important information (default) * `callout-banner-warning` - callout with a warning * `callout-banner-error` - callout informing about an error (most severe) * `issue-content` - section of the `issue-detail`, contains multiple `content-element` * `content-element` - content element such as a list, link or paragraph, inside `issue-content` * `root-causes` - unordered list with items describing root causes of the issue, inside `issue-content` * `root-causes-intro` - intro text before the `root-causes` list, inside `issue-content` * `segment` - section of the text, `span` inside paragraph * `segment-attribute` - section of the text that represents a product attribute, for example 'image\_link' * `segment-literal` - section of the text that contains a special value, for example '0-1000 kg' * `segment-bold` - section of the text that should be rendered as bold * `segment-italic` - section of the text that should be rendered as italic * `tooltip` - used on paragraphs that should be rendered with a tooltip. A section of the text in such a paragraph will have a class `tooltip-text` and is intended to be shown in a mouse over dialog. If the style is not used, the `tooltip-text` section would be shown on a new line, after the main part of the text. * `tooltip-text` - marks a section of the text within a `tooltip`, that is intended to be shown in a mouse over dialog. * `tooltip-icon` - marks a section of the text within a `tooltip`, that can be replaced with a tooltip icon, for example '?' or 'i'. By default, this section contains a `br` tag, that is separating the main text and the tooltip text when the style is not used. * `tooltip-style-question` - the tooltip shows helpful information, can use the '?' as an icon. * `tooltip-style-info` - the tooltip adds additional information fitting to the context, can use the 'i' as an icon. * `content-moderation` - marks the paragraph that explains how the issue was identified. * `asset-value` - marks the paragraph that contains the asset information. * `asset-label` - marks the section of the text that contains the label of the asset. * `asset-link` - marks the section of the text that contains a link to the asset. * `asset-provided-value` - marks the section of the text that contains the value of the asset. * `new-element` - Present for new elements added to the pre-rendered content in the future. To make sure that a new content element does not break your style, you can hide everything with this class.
      */
     prerenderedContent?: string | null;
     /**
@@ -729,7 +729,7 @@ export namespace merchantapi_issueresolution_v1 {
     }
 
     /**
-     * Lists the `AggregateProductStatuses` resources for your merchant account. The response might contain fewer items than specified by `pageSize`. If `pageToken` was returned in previous request, it can be used to obtain additional results.
+     * Lists the `AggregateProductStatuses` resources for your merchant account. The response might contain fewer items than specified by `pageSize`. If `pageToken` was returned in previous request, it can be used to obtain additional results. This method can only be accessed by standalone accounts and sub-accounts of an advanced account. To retrieve product statuses for sub-accounts, you must first call the accounts.listSubaccounts method to obtain a list of sub-accounts, and then call `accounts.aggregateProductStatuses.list` for each sub-account individually.
      * @example
      * ```js
      * // Before running the sample:
@@ -765,7 +765,7 @@ export namespace merchantapi_issueresolution_v1 {
      *     pageSize: 'placeholder-value',
      *     // Optional. A page token, received from a previous `ListAggregateProductStatuses` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `ListAggregateProductStatuses` must match the call that provided the page token.
      *     pageToken: 'placeholder-value',
-     *     // Required. The account to list aggregate product statuses for. Format: `accounts/{account\}`
+     *     // Required. The account to list aggregate product statuses for. Format: `accounts/{account\}` Can only be sub-accounts and standalone accounts.
      *     parent: 'accounts/my-account',
      *   });
      *   console.log(res.data);
@@ -896,7 +896,7 @@ export namespace merchantapi_issueresolution_v1 {
      */
     pageToken?: string;
     /**
-     * Required. The account to list aggregate product statuses for. Format: `accounts/{account\}`
+     * Required. The account to list aggregate product statuses for. Format: `accounts/{account\}` Can only be sub-accounts and standalone accounts.
      */
     parent?: string;
   }
@@ -1294,8 +1294,7 @@ export namespace merchantapi_issueresolution_v1 {
     triggeraction(
       params: Params$Resource$Issueresolution$Triggeraction,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$TriggerActionResponse>,
+        MethodOptions | BodyResponseCallback<Schema$TriggerActionResponse>,
       callback: BodyResponseCallback<Schema$TriggerActionResponse>
     ): void;
     triggeraction(

package/issueresolution_v1beta.ts

@@ -587,7 +587,7 @@ export namespace merchantapi_issueresolution_v1beta {
      */
     impact?: Schema$Impact;
     /**
-     * Details of the issue as a pre-rendered HTML. HTML elements contain CSS classes that can be used to customize the style of the content. Always sanitize the HTML before embedding it directly to your application. The sanitizer needs to allow basic HTML tags, such as: `div`, `span`, `p`, `a`, `ul`, `li`, `table`, `tr`, `td`. For example, you can use [DOMPurify](https://www.npmjs.com/package/dompurify). CSS classes: * `issue-detail` - top level container for the detail of the issue * `callout-banners` - section of the `issue-detail` with callout banners * `callout-banner` - single callout banner, inside `callout-banners` * `callout-banner-info` - callout with important information (default) * `callout-banner-warning` - callout with a warning * `callout-banner-error` - callout informing about an error (most severe) * `issue-content` - section of the `issue-detail`, contains multiple `content-element` * `content-element` - content element such as a list, link or paragraph, inside `issue-content` * `root-causes` - unordered list with items describing root causes of the issue, inside `issue-content` * `root-causes-intro` - intro text before the `root-causes` list, inside `issue-content` * `segment` - section of the text, `span` inside paragraph * `segment-attribute` - section of the text that represents a product attribute, for example 'image\_link' * `segment-literal` - section of the text that contains a special value, for example '0-1000 kg' * `segment-bold` - section of the text that should be rendered as bold * `segment-italic` - section of the text that should be rendered as italic * `tooltip` - used on paragraphs that should be rendered with a tooltip. A section of the text in such a paragraph will have a class `tooltip-text` and is intended to be shown in a mouse over dialog. If the style is not used, the `tooltip-text` section would be shown on a new line, after the main part of the text. * `tooltip-text` - marks a section of the text within a `tooltip`, that is intended to be shown in a mouse over dialog. * `tooltip-icon` - marks a section of the text within a `tooltip`, that can be replaced with a tooltip icon, for example '?' or 'i'. By default, this section contains a `br` tag, that is separating the main text and the tooltip text when the style is not used. * `tooltip-style-question` - the tooltip shows helpful information, can use the '?' as an icon. * `tooltip-style-info` - the tooltip adds additional information fitting to the context, can use the 'i' as an icon. * `content-moderation` - marks the paragraph that explains how the issue was identified. * `new-element` - Present for new elements added to the pre-rendered content in the future. To make sure that a new content element does not break your style, you can hide everything with this class.
+     * Details of the issue as a pre-rendered HTML. HTML elements contain CSS classes that can be used to customize the style of the content. Always sanitize the HTML before embedding it directly to your application. The sanitizer needs to allow basic HTML tags, such as: `div`, `span`, `p`, `a`, `ul`, `li`, `table`, `tr`, `td`. For example, you can use [DOMPurify](https://www.npmjs.com/package/dompurify). CSS classes: * `issue-detail` - top level container for the detail of the issue * `callout-banners` - section of the `issue-detail` with callout banners * `callout-banner` - single callout banner, inside `callout-banners` * `callout-banner-info` - callout with important information (default) * `callout-banner-warning` - callout with a warning * `callout-banner-error` - callout informing about an error (most severe) * `issue-content` - section of the `issue-detail`, contains multiple `content-element` * `content-element` - content element such as a list, link or paragraph, inside `issue-content` * `root-causes` - unordered list with items describing root causes of the issue, inside `issue-content` * `root-causes-intro` - intro text before the `root-causes` list, inside `issue-content` * `segment` - section of the text, `span` inside paragraph * `segment-attribute` - section of the text that represents a product attribute, for example 'image\_link' * `segment-literal` - section of the text that contains a special value, for example '0-1000 kg' * `segment-bold` - section of the text that should be rendered as bold * `segment-italic` - section of the text that should be rendered as italic * `tooltip` - used on paragraphs that should be rendered with a tooltip. A section of the text in such a paragraph will have a class `tooltip-text` and is intended to be shown in a mouse over dialog. If the style is not used, the `tooltip-text` section would be shown on a new line, after the main part of the text. * `tooltip-text` - marks a section of the text within a `tooltip`, that is intended to be shown in a mouse over dialog. * `tooltip-icon` - marks a section of the text within a `tooltip`, that can be replaced with a tooltip icon, for example '?' or 'i'. By default, this section contains a `br` tag, that is separating the main text and the tooltip text when the style is not used. * `tooltip-style-question` - the tooltip shows helpful information, can use the '?' as an icon. * `tooltip-style-info` - the tooltip adds additional information fitting to the context, can use the 'i' as an icon. * `content-moderation` - marks the paragraph that explains how the issue was identified. * `asset-value` - marks the paragraph that contains the asset information. * `asset-label` - marks the section of the text that contains the label of the asset. * `asset-link` - marks the section of the text that contains a link to the asset. * `asset-provided-value` - marks the section of the text that contains the value of the asset. * `new-element` - Present for new elements added to the pre-rendered content in the future. To make sure that a new content element does not break your style, you can hide everything with this class.
      */
     prerenderedContent?: string | null;
     /**
@@ -729,7 +729,7 @@ export namespace merchantapi_issueresolution_v1beta {
     }
 
     /**
-     * Lists the `AggregateProductStatuses` resources for your merchant account. The response might contain fewer items than specified by `pageSize`. If `pageToken` was returned in previous request, it can be used to obtain additional results.
+     * Lists the `AggregateProductStatuses` resources for your merchant account. The response might contain fewer items than specified by `pageSize`. If `pageToken` was returned in previous request, it can be used to obtain additional results. This method can only be accessed by standalone accounts and sub-accounts of an advanced account. To retrieve product statuses for sub-accounts, you must first call the accounts.listSubaccounts method to obtain a list of sub-accounts, and then call `accounts.aggregateProductStatuses.list` for each sub-account individually.
      * @example
      * ```js
      * // Before running the sample:
@@ -765,7 +765,7 @@ export namespace merchantapi_issueresolution_v1beta {
      *     pageSize: 'placeholder-value',
      *     // Optional. A page token, received from a previous `ListAggregateProductStatuses` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `ListAggregateProductStatuses` must match the call that provided the page token.
      *     pageToken: 'placeholder-value',
-     *     // Required. The account to list aggregate product statuses for. Format: `accounts/{account\}`
+     *     // Required. The account to list aggregate product statuses for. Format: `accounts/{account\}` Can only be sub-accounts and standalone accounts.
      *     parent: 'accounts/my-account',
      *   });
      *   console.log(res.data);
@@ -897,7 +897,7 @@ export namespace merchantapi_issueresolution_v1beta {
      */
     pageToken?: string;
     /**
-     * Required. The account to list aggregate product statuses for. Format: `accounts/{account\}`
+     * Required. The account to list aggregate product statuses for. Format: `accounts/{account\}` Can only be sub-accounts and standalone accounts.
      */
     parent?: string;
   }
@@ -1295,8 +1295,7 @@ export namespace merchantapi_issueresolution_v1beta {
     triggeraction(
       params: Params$Resource$Issueresolution$Triggeraction,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$TriggerActionResponse>,
+        MethodOptions | BodyResponseCallback<Schema$TriggerActionResponse>,
       callback: BodyResponseCallback<Schema$TriggerActionResponse>
     ): void;
     triggeraction(

package/lfp_v1.ts

@@ -959,8 +959,7 @@ export namespace merchantapi_lfp_v1 {
         | BodyResponseCallback<Schema$LfpSale>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$LfpSale>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$LfpSale> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$LfpSale>>
@@ -1113,8 +1112,7 @@ export namespace merchantapi_lfp_v1 {
         | BodyResponseCallback<Schema$Empty>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$Empty>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$Empty> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$Empty>>
@@ -1257,8 +1255,7 @@ export namespace merchantapi_lfp_v1 {
         | BodyResponseCallback<Schema$LfpStore>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$LfpStore>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$LfpStore> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$LfpStore>>
@@ -1419,8 +1416,7 @@ export namespace merchantapi_lfp_v1 {
         | BodyResponseCallback<Schema$LfpStore>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$LfpStore>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$LfpStore> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$LfpStore>>
@@ -1545,8 +1541,7 @@ export namespace merchantapi_lfp_v1 {
     list(
       params: Params$Resource$Accounts$Lfpstores$List,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$ListLfpStoresResponse>,
+        MethodOptions | BodyResponseCallback<Schema$ListLfpStoresResponse>,
       callback: BodyResponseCallback<Schema$ListLfpStoresResponse>
     ): void;
     list(

package/lfp_v1beta.ts

@@ -961,8 +961,7 @@ export namespace merchantapi_lfp_v1beta {
         | BodyResponseCallback<Schema$LfpSale>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$LfpSale>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$LfpSale> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$LfpSale>>
@@ -1115,8 +1114,7 @@ export namespace merchantapi_lfp_v1beta {
         | BodyResponseCallback<Schema$Empty>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$Empty>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$Empty> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$Empty>>
@@ -1262,8 +1260,7 @@ export namespace merchantapi_lfp_v1beta {
         | BodyResponseCallback<Schema$LfpStore>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$LfpStore>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$LfpStore> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$LfpStore>>
@@ -1427,8 +1424,7 @@ export namespace merchantapi_lfp_v1beta {
         | BodyResponseCallback<Schema$LfpStore>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$LfpStore>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$LfpStore> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$LfpStore>>
@@ -1553,8 +1549,7 @@ export namespace merchantapi_lfp_v1beta {
     list(
       params: Params$Resource$Accounts$Lfpstores$List,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$ListLfpStoresResponse>,
+        MethodOptions | BodyResponseCallback<Schema$ListLfpStoresResponse>,
       callback: BodyResponseCallback<Schema$ListLfpStoresResponse>
     ): void;
     list(

package/notifications_v1.ts

@@ -154,7 +154,7 @@ export namespace merchantapi_notifications_v1 {
      */
     callBackUri?: string | null;
     /**
-     * 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\}`
+     * Output only. The `name` of the notification configuration. Generated by the Merchant 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\}`
      */
     name?: string | null;
     /**
@@ -246,7 +246,7 @@ export namespace merchantapi_notifications_v1 {
     }
 
     /**
-     * Creates a notification subscription for a business. For standalone or subaccounts accounts, the business can create a subscription for self. For MCAs, the business can create a subscription for all managed accounts or for a specific subaccount. See [Decode notifications](/merchant/api/guides/accounts/notifications#decode_notifications) for information on how to decode the notification payload and how to interpret its contents. We will allow the following types of notification subscriptions to exist together (per business as a subscriber per event type): 1. Subscription for all managed accounts + subscription for self. 2. Multiple "partial" subscriptions for managed accounts + subscription for self. we will not allow (per business as a subscriber per event type): 1. Multiple self subscriptions. 2. Multiple "all managed accounts" subscriptions. 3. "All managed accounts" subscription and partial subscriptions at the same time. 4. Multiple partial subscriptions for the same target account.
+     * Creates a notification subscription for a business. For standalone or sub-accounts, the business can create a subscription for self. For advanced accounts, the business can create a subscription for all managed accounts or for a specific subaccount. See [Decode notifications](/merchant/api/guides/accounts/notifications#decode_notifications) for information on how to decode the notification payload and how to interpret its contents. We will allow the following types of notification subscriptions to exist together (per business as a subscriber per event type): 1. Subscription for all managed accounts + subscription for self. 2. Multiple "partial" subscriptions for managed accounts + subscription for self. we will not allow (per business as a subscriber per event type): 1. Multiple self subscriptions. 2. Multiple "all managed accounts" subscriptions. 3. "All managed accounts" subscription and partial subscriptions at the same time. 4. Multiple partial subscriptions for the same target account.
      * @example
      * ```js
      * // Before running the sample:
@@ -331,8 +331,7 @@ export namespace merchantapi_notifications_v1 {
     create(
       params: Params$Resource$Accounts$Notificationsubscriptions$Create,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$NotificationSubscription>,
+        MethodOptions | BodyResponseCallback<Schema$NotificationSubscription>,
       callback: BodyResponseCallback<Schema$NotificationSubscription>
     ): void;
     create(
@@ -488,8 +487,7 @@ export namespace merchantapi_notifications_v1 {
         | BodyResponseCallback<Schema$Empty>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$Empty>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$Empty> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$Empty>>
@@ -612,8 +610,7 @@ export namespace merchantapi_notifications_v1 {
     get(
       params: Params$Resource$Accounts$Notificationsubscriptions$Get,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$NotificationSubscription>,
+        MethodOptions | BodyResponseCallback<Schema$NotificationSubscription>,
       callback: BodyResponseCallback<Schema$NotificationSubscription>
     ): void;
     get(
@@ -863,7 +860,7 @@ export namespace merchantapi_notifications_v1 {
      *
      *   // Do the magic
      *   const res = await merchantapi.accounts.notificationsubscriptions.patch({
-     *     // 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\}`
+     *     // Output only. The `name` of the notification configuration. Generated by the Merchant 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\}`
      *     name: 'accounts/my-account/notificationsubscriptions/my-notificationsubscription',
      *     // List of fields being updated.
      *     updateMask: 'placeholder-value',
@@ -920,8 +917,7 @@ export namespace merchantapi_notifications_v1 {
     patch(
       params: Params$Resource$Accounts$Notificationsubscriptions$Patch,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$NotificationSubscription>,
+        MethodOptions | BodyResponseCallback<Schema$NotificationSubscription>,
       callback: BodyResponseCallback<Schema$NotificationSubscription>
     ): void;
     patch(
@@ -1031,7 +1027,7 @@ export namespace merchantapi_notifications_v1 {
   }
   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\}`
+     * Output only. The `name` of the notification configuration. Generated by the Merchant 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\}`
      */
     name?: string;
     /**

package/notifications_v1beta.ts

@@ -154,7 +154,7 @@ export namespace merchantapi_notifications_v1beta {
      */
     callBackUri?: string | null;
     /**
-     * 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\}`
+     * Output only. The `name` of the notification configuration. Generated by the Merchant 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\}`
      */
     name?: string | null;
     /**
@@ -246,7 +246,7 @@ export namespace merchantapi_notifications_v1beta {
     }
 
     /**
-     * Creates a notification subscription for a business. For standalone or subaccounts accounts, the business can create a subscription for self. For MCAs, the business can create a subscription for all managed accounts or for a specific subaccount. See [Decode notifications](/merchant/api/guides/accounts/notifications#decode_notifications) for information on how to decode the notification payload and how to interpret its contents. We will allow the following types of notification subscriptions to exist together (per business as a subscriber per event type): 1. Subscription for all managed accounts + subscription for self. 2. Multiple "partial" subscriptions for managed accounts + subscription for self. we will not allow (per business as a subscriber per event type): 1. Multiple self subscriptions. 2. Multiple "all managed accounts" subscriptions. 3. "All managed accounts" subscription and partial subscriptions at the same time. 4. Multiple partial subscriptions for the same target account.
+     * Creates a notification subscription for a business. For standalone or sub-accounts, the business can create a subscription for self. For advanced accounts, the business can create a subscription for all managed accounts or for a specific subaccount. See [Decode notifications](/merchant/api/guides/accounts/notifications#decode_notifications) for information on how to decode the notification payload and how to interpret its contents. We will allow the following types of notification subscriptions to exist together (per business as a subscriber per event type): 1. Subscription for all managed accounts + subscription for self. 2. Multiple "partial" subscriptions for managed accounts + subscription for self. we will not allow (per business as a subscriber per event type): 1. Multiple self subscriptions. 2. Multiple "all managed accounts" subscriptions. 3. "All managed accounts" subscription and partial subscriptions at the same time. 4. Multiple partial subscriptions for the same target account.
      * @example
      * ```js
      * // Before running the sample:
@@ -331,8 +331,7 @@ export namespace merchantapi_notifications_v1beta {
     create(
       params: Params$Resource$Accounts$Notificationsubscriptions$Create,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$NotificationSubscription>,
+        MethodOptions | BodyResponseCallback<Schema$NotificationSubscription>,
       callback: BodyResponseCallback<Schema$NotificationSubscription>
     ): void;
     create(
@@ -489,8 +488,7 @@ export namespace merchantapi_notifications_v1beta {
         | BodyResponseCallback<Schema$Empty>
         | BodyResponseCallback<Readable>,
       callback?:
-        | BodyResponseCallback<Schema$Empty>
-        | BodyResponseCallback<Readable>
+        BodyResponseCallback<Schema$Empty> | BodyResponseCallback<Readable>
     ):
       | void
       | Promise<GaxiosResponseWithHTTP2<Schema$Empty>>
@@ -613,8 +611,7 @@ export namespace merchantapi_notifications_v1beta {
     get(
       params: Params$Resource$Accounts$Notificationsubscriptions$Get,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$NotificationSubscription>,
+        MethodOptions | BodyResponseCallback<Schema$NotificationSubscription>,
       callback: BodyResponseCallback<Schema$NotificationSubscription>
     ): void;
     get(
@@ -865,7 +862,7 @@ export namespace merchantapi_notifications_v1beta {
      *
      *   // Do the magic
      *   const res = await merchantapi.accounts.notificationsubscriptions.patch({
-     *     // 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\}`
+     *     // Output only. The `name` of the notification configuration. Generated by the Merchant 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\}`
      *     name: 'accounts/my-account/notificationsubscriptions/my-notificationsubscription',
      *     // List of fields being updated.
      *     updateMask: 'placeholder-value',
@@ -922,8 +919,7 @@ export namespace merchantapi_notifications_v1beta {
     patch(
       params: Params$Resource$Accounts$Notificationsubscriptions$Patch,
       options:
-        | MethodOptions
-        | BodyResponseCallback<Schema$NotificationSubscription>,
+        MethodOptions | BodyResponseCallback<Schema$NotificationSubscription>,
       callback: BodyResponseCallback<Schema$NotificationSubscription>
     ): void;
     patch(
@@ -1033,7 +1029,7 @@ export namespace merchantapi_notifications_v1beta {
   }
   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\}`
+     * Output only. The `name` of the notification configuration. Generated by the Merchant 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\}`
      */
     name?: string;
     /**

package/package.json

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