google-api-python-client 2.187.0__py3-none-any.whl → 2.189.0__py3-none-any.whl

googleapiclient/discovery_cache/documents/merchantapi.issueresolution_v1beta.json

@@ -209,7 +209,7 @@
 "type": "string"
 },
 "name": {
-"description": "Required. The name of the product to fetch issues for. Format: `accounts/{account}/products/{product}`",
+"description": "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`.",
 "location": "path",
 "pattern": "^accounts/[^/]+/products/[^/]+$",
 "required": true,
@@ -233,7 +233,7 @@
 ]
 },
 "triggeraction": {
-"description": "Start an action. The action can be requested by a business in third-party application. Before the business can request the action, the third-party application needs to show them action specific content and display a user input form. The action can be successfully started only once all `required` inputs are provided. If any `required` input is missing, or invalid value was provided, the service will return 400 error. Validation errors will contain Ids for all problematic field together with translated, human readable error messages that can be shown to the user.",
+"description": "Start an action. The action can be requested by a business in third-party application. Before the business can request the action, the third-party application needs to show them action specific content and display a user input form. Access to the `triggeraction` method is restricted to an allowlist. You can request access using [Trigger action allowlist form](https://docs.google.com/forms/d/e/1FAIpQLSfeV_sBW9MBQv9BMTV6JZ1g11PGHLdHsrefca-9h0LmpU7CUg/viewform?usp=sharing). The action can be successfully started only once all `required` inputs are provided. If any `required` input is missing, or invalid value was provided, the service will return 400 error. Validation errors will contain Ids for all problematic field together with translated, human readable error messages that can be shown to the user.",
 "flatPath": "issueresolution/v1beta/accounts/{accountsId}:triggeraction",
 "httpMethod": "POST",
 "id": "merchantapi.issueresolution.triggeraction",
@@ -268,7 +268,7 @@
 }
 }
 },
-"revision": "20250830",
+"revision": "20260118",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "Action": {

googleapiclient/discovery_cache/documents/merchantapi.notifications_v1.json

@@ -110,7 +110,7 @@
 "notificationsubscriptions": {
 "methods": {
 "create": {
-"description": "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. 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.",
+"description": "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.",
 "flatPath": "notifications/v1/accounts/{accountsId}/notificationsubscriptions",
 "httpMethod": "POST",
 "id": "merchantapi.accounts.notificationsubscriptions.create",
@@ -262,7 +262,7 @@
 }
 }
 },
-"revision": "20250804",
+"revision": "20260118",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "Empty": {
@@ -290,7 +290,7 @@
 "type": "object"
 },
 "NotificationSubscription": {
-"description": "Represents a notification subscription owned by a Merchant account.",
+"description": "Represents a notification subscription owned by a Merchant account. 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.",
 "id": "NotificationSubscription",
 "properties": {
 "allManagedAccounts": {

googleapiclient/discovery_cache/documents/merchantapi.notifications_v1beta.json

@@ -110,7 +110,7 @@
 "notificationsubscriptions": {
 "methods": {
 "create": {
-"description": "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. 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.",
+"description": "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.",
 "flatPath": "notifications/v1beta/accounts/{accountsId}/notificationsubscriptions",
 "httpMethod": "POST",
 "id": "merchantapi.accounts.notificationsubscriptions.create",
@@ -262,7 +262,7 @@
 }
 }
 },
-"revision": "20250621",
+"revision": "20260118",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "Empty": {
@@ -290,7 +290,7 @@
 "type": "object"
 },
 "NotificationSubscription": {
-"description": "Represents a notification subscription owned by a Merchant account.",
+"description": "Represents a notification subscription owned by a Merchant account. 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.",
 "id": "NotificationSubscription",
 "properties": {
 "allManagedAccounts": {

googleapiclient/discovery_cache/documents/merchantapi.products_v1.json

@@ -124,7 +124,7 @@
 "type": "string"
 },
 "name": {
-"description": "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`.",
+"description": "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`.",
 "location": "path",
 "pattern": "^accounts/[^/]+/productInputs/[^/]+$",
 "required": true,
@@ -173,7 +173,7 @@
 ]
 },
 "patch": {
-"description": "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.",
+"description": "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.",
 "flatPath": "products/v1/accounts/{accountsId}/productInputs/{productInputsId}",
 "httpMethod": "PATCH",
 "id": "merchantapi.accounts.productInputs.patch",
@@ -187,7 +187,7 @@
 "type": "string"
 },
 "name": {
-"description": "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`.",
+"description": "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`.",
 "location": "path",
 "pattern": "^accounts/[^/]+/productInputs/[^/]+$",
 "required": true,
@@ -225,7 +225,7 @@
 ],
 "parameters": {
 "name": {
-"description": "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`.",
+"description": "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`.",
 "location": "path",
 "pattern": "^accounts/[^/]+/products/[^/]+$",
 "required": true,
@@ -281,7 +281,7 @@
 }
 }
 },
-"revision": "20251007",
+"revision": "20260113",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "AutomatedDiscounts": {
@@ -1696,6 +1696,13 @@ false
 },
 "type": "array"
 },
+"shippingHandlingBusinessDays": {
+"description": "The business days during which orders can be handled. If not provided, Monday to Friday business days will be assumed.",
+"items": {
+"$ref": "ShippingBusinessDaysConfig"
+},
+"type": "array"
+},
 "shippingHeight": {
 "$ref": "ShippingDimension",
 "description": "Height of the item for shipping."
@@ -1708,6 +1715,13 @@ false
 "$ref": "ShippingDimension",
 "description": "Length of the item for shipping."
 },
+"shippingTransitBusinessDays": {
+"description": "The business days during which orders are in transit. If not provided, Monday to Friday business days will be assumed.",
+"items": {
+"$ref": "ShippingBusinessDaysConfig"
+},
+"type": "array"
+},
 "shippingWeight": {
 "$ref": "ShippingWeight",
 "description": "Weight of the item for shipping."
@@ -1794,7 +1808,7 @@ false
 },
 "subscriptionCost": {
 "$ref": "SubscriptionCost",
-"description": "Number of periods (months or years) and amount of payment per period for an item with an associated subscription contract."
+"description": "Number of periods (weeks, months or years) and amount of payment per period for an item with an associated subscription contract."
 },
 "sustainabilityIncentives": {
 "description": "The list of sustainability incentive programs.",
@@ -2026,7 +2040,7 @@ false
 "type": "boolean"
 },
 "name": {
-"description": "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`.",
+"description": "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`.",
 "type": "string"
 },
 "offerId": {
@@ -2294,6 +2308,21 @@ false
 },
 "type": "object"
 },
+"ShippingBusinessDaysConfig": {
+"description": "The business days during which orders are on their path to fulfillment. If not provided, Monday to Friday business days will be assumed.",
+"id": "ShippingBusinessDaysConfig",
+"properties": {
+"businessDays": {
+"description": "Effective days of the week considered for the delivery time calculation. May not be empty. The more business days included the faster the delivery. Can be set through individual days (e.g. `MTWRF`), or day ranges (e.g. `Mon-Fri`). For more information about accepted formats, see [Shipping handling business days](https://support.google.com/merchants/answer/16072859).",
+"type": "string"
+},
+"country": {
+"description": "The [CLDR territory code](http://www.unicode.org/repos/cldr/tags/latest/common/main/en.xml) of the country to which an item will ship.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "ShippingDimension": {
 "description": "The ShippingDimension of the product.",
 "id": "ShippingDimension",
@@ -2385,16 +2414,18 @@ false
 "description": "The amount the buyer has to pay per subscription period."
 },
 "period": {
-"description": "The type of subscription period. Supported values are: * \"`month`\" * \"`year`\"",
+"description": "The type of subscription period. Supported values are: * \"`month`\" * \"`year`\" * \"`week`\"",
 "enum": [
 "SUBSCRIPTION_PERIOD_UNSPECIFIED",
 "MONTH",
-"YEAR"
+"YEAR",
+"WEEK"
 ],
 "enumDescriptions": [
 "Indicates that the subscription period is unspecified.",
 "Indicates that the subscription period is month.",
-"Indicates that the subscription period is year."
+"Indicates that the subscription period is year.",
+"Indicates that the subscription period is week."
 ],
 "type": "string"
 },

googleapiclient/discovery_cache/documents/merchantapi.products_v1beta.json

@@ -124,7 +124,7 @@
 "type": "string"
 },
 "name": {
-"description": "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`.",
+"description": "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`.",
 "location": "path",
 "pattern": "^accounts/[^/]+/productInputs/[^/]+$",
 "required": true,
@@ -173,7 +173,7 @@
 ]
 },
 "patch": {
-"description": "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.",
+"description": "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.",
 "flatPath": "products/v1beta/accounts/{accountsId}/productInputs/{productInputsId}",
 "httpMethod": "PATCH",
 "id": "merchantapi.accounts.productInputs.patch",
@@ -187,7 +187,7 @@
 "type": "string"
 },
 "name": {
-"description": "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`.",
+"description": "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`.",
 "location": "path",
 "pattern": "^accounts/[^/]+/productInputs/[^/]+$",
 "required": true,
@@ -225,7 +225,7 @@
 ],
 "parameters": {
 "name": {
-"description": "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`.",
+"description": "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`.",
 "location": "path",
 "pattern": "^accounts/[^/]+/products/[^/]+$",
 "required": true,
@@ -281,7 +281,7 @@
 }
 }
 },
-"revision": "20251007",
+"revision": "20260113",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "Attributes": {
@@ -700,7 +700,7 @@
 },
 "subscriptionCost": {
 "$ref": "SubscriptionCost",
-"description": "Number of periods (months or years) and amount of payment per period for an item with an associated subscription contract."
+"description": "Number of periods (weeks, months or years) and amount of payment per period for an item with an associated subscription contract."
 },
 "sustainabilityIncentives": {
 "description": "The list of sustainability incentive programs.",
@@ -1464,7 +1464,7 @@ false
 "type": "string"
 },
 "name": {
-"description": "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`.",
+"description": "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`.",
 "type": "string"
 },
 "offerId": {
@@ -1765,16 +1765,18 @@ false
 "description": "The amount the buyer has to pay per subscription period."
 },
 "period": {
-"description": "The type of subscription period. Supported values are: * \"`month`\" * \"`year`\"",
+"description": "The type of subscription period. Supported values are: * \"`month`\" * \"`year`\" * \"`week`\"",
 "enum": [
 "SUBSCRIPTION_PERIOD_UNSPECIFIED",
 "MONTH",
-"YEAR"
+"YEAR",
+"WEEK"
 ],
 "enumDescriptions": [
 "Indicates that the subscription period is unspecified.",
 "Indicates that the subscription period is month.",
-"Indicates that the subscription period is year."
+"Indicates that the subscription period is year.",
+"Indicates that the subscription period is week."
 ],
 "type": "string"
 },

googleapiclient/discovery_cache/documents/merchantapi.quota_v1.json

@@ -107,6 +107,76 @@
 "resources": {
 "accounts": {
 "resources": {
+"limits": {
+"methods": {
+"get": {
+"description": "Retrieves an account limit.",
+"flatPath": "quota/v1/accounts/{accountsId}/limits/{limitsId}",
+"httpMethod": "GET",
+"id": "merchantapi.accounts.limits.get",
+"parameterOrder": [
+"name"
+],
+"parameters": {
+"name": {
+"description": "Required. The name of the limit to retrieve. Format: `accounts/{account}/limits/{limit}` For example: `accounts/123/limits/products~ADS_NON_EEA`",
+"location": "path",
+"pattern": "^accounts/[^/]+/limits/[^/]+$",
+"required": true,
+"type": "string"
+}
+},
+"path": "quota/v1/{+name}",
+"response": {
+"$ref": "AccountLimit"
+},
+"scopes": [
+"https://www.googleapis.com/auth/content"
+]
+},
+"list": {
+"description": "Lists the limits of an account.",
+"flatPath": "quota/v1/accounts/{accountsId}/limits",
+"httpMethod": "GET",
+"id": "merchantapi.accounts.limits.list",
+"parameterOrder": [
+"parent"
+],
+"parameters": {
+"filter": {
+"description": "Required. A filter on the limit `type` is required, for example, `type = \"products\"`.",
+"location": "query",
+"type": "string"
+},
+"pageSize": {
+"description": "Optional. The maximum number of limits to return. The service may return fewer than this value. If unspecified, at most 100 limits will be returned. The maximum value is 100; values above 100 will be coerced to 100.",
+"format": "int32",
+"location": "query",
+"type": "integer"
+},
+"pageToken": {
+"description": "Optional. A page token, received from a previous `ListAccountLimits` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `ListAccountLimits` must match the call that provided the page token.",
+"location": "query",
+"type": "string"
+},
+"parent": {
+"description": "Required. The parent account. Format: `accounts/{account}`",
+"location": "path",
+"pattern": "^accounts/[^/]+$",
+"required": true,
+"type": "string"
+}
+},
+"path": "quota/v1/{+parent}/limits",
+"response": {
+"$ref": "ListAccountLimitsResponse"
+},
+"scopes": [
+"https://www.googleapis.com/auth/content"
+]
+}
+}
+},
 "quotas": {
 "methods": {
 "list": {
@@ -150,9 +220,42 @@
 }
 }
 },
-"revision": "20250804",
+"revision": "20251118",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
+"AccountLimit": {
+"description": "A limit of a certain type that is applied to an account.",
+"id": "AccountLimit",
+"properties": {
+"name": {
+"description": "Identifier. The limit part of the name will be a combination of the type and the scope. For example: `accounts/123/limits/products~ADS_NON_EEA` Format: `accounts/{account}/limits/{limit}`",
+"type": "string"
+},
+"products": {
+"$ref": "ProductLimit",
+"description": "The limit for products."
+}
+},
+"type": "object"
+},
+"ListAccountLimitsResponse": {
+"description": "Response message for the `ListAccountLimits` method.",
+"id": "ListAccountLimitsResponse",
+"properties": {
+"accountLimits": {
+"description": "The limits for the given account.",
+"items": {
+"$ref": "AccountLimit"
+},
+"type": "array"
+},
+"nextPageToken": {
+"description": "A token, which can be sent as `page_token` to retrieve the next page. If this field is omitted, there are no subsequent pages.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "ListQuotaGroupsResponse": {
 "description": "Response message for the ListMethodGroups method.",
 "id": "ListQuotaGroupsResponse",
@@ -284,6 +387,32 @@ false
 },
 "type": "object"
 },
+"ProductLimit": {
+"description": "The limit for products.",
+"id": "ProductLimit",
+"properties": {
+"limit": {
+"description": "Required. The maximum number of products that are allowed in the account in the given scope.",
+"format": "int64",
+"type": "string"
+},
+"scope": {
+"description": "Required. The scope of the product limit.",
+"enum": [
+"SCOPE_UNSPECIFIED",
+"ADS_NON_EEA",
+"ADS_EEA"
+],
+"enumDescriptions": [
+"Default value. Should not be used.",
+"Limit for products in non-EEA countries.",
+"Limit for products in EEA countries."
+],
+"type": "string"
+}
+},
+"type": "object"
+},
 "ProductStatusChangeMessage": {
 "description": "The message that the merchant will receive to notify about product status change event",
 "id": "ProductStatusChangeMessage",

googleapiclient/discovery_cache/documents/merchantapi.reports_v1.json

@@ -142,7 +142,7 @@
 }
 }
 },
-"revision": "20250808",
+"revision": "20260106",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "BestSellersBrandView": {
@@ -1367,7 +1367,7 @@ false
 "type": "string"
 },
 "clickPotentialRank": {
-"description": "Rank of the product based on its click potential. A product with `click_potential_rank` 1 has the highest click potential among the merchant's products that fulfill the search query conditions.",
+"description": "Normalized click potential of the product. Values range from 1 to 1000, where 1 is the highest click potential and 1000 is the theoretical lowest.",
 "format": "int64",
 "type": "string"
 },

googleapiclient/discovery_cache/documents/merchantapi.reports_v1beta.json

@@ -142,7 +142,7 @@
 }
 }
 },
-"revision": "20250808",
+"revision": "20260106",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "BestSellersBrandView": {
@@ -1367,7 +1367,7 @@ false
 "type": "string"
 },
 "clickPotentialRank": {
-"description": "Rank of the product based on its click potential. A product with `click_potential_rank` 1 has the highest click potential among the merchant's products that fulfill the search query conditions.",
+"description": "Normalized click potential of the product. Values range from 1 to 1000, where 1 is the highest click potential and 1000 is the theoretical lowest.",
 "format": "int64",
 "type": "string"
 },

googleapiclient/discovery_cache/documents/metastore.v1.json

@@ -565,7 +565,7 @@
 "type": "string"
 },
 "returnPartialSuccess": {
-"description": "When set to true, operations that are reachable are returned as normal, and those that are unreachable are returned in the ListOperationsResponse.unreachable field.This can only be true when reading across collections e.g. when parent is set to \"projects/example/locations/-\".This field is not by default supported and will result in an UNIMPLEMENTED error if set unless explicitly documented otherwise in service or product specific documentation.",
+"description": "When set to true, operations that are reachable are returned as normal, and those that are unreachable are returned in the ListOperationsResponse.unreachable field.This can only be true when reading across collections. For example, when parent is set to \"projects/example/locations/-\".This field is not supported by default and will result in an UNIMPLEMENTED error if set unless explicitly documented otherwise in service or product specific documentation.",
 "location": "query",
 "type": "boolean"
 }
@@ -1695,7 +1695,7 @@
 }
 }
 },
-"revision": "20251023",
+"revision": "20260122",
 "rootUrl": "https://metastore.googleapis.com/",
 "schemas": {
 "AlterMetadataResourceLocationRequest": {
@@ -2072,7 +2072,8 @@
 "type": "object"
 },
 "CustomRegionMetadata": {
-"description": "Metadata about a custom region. This is only populated if the region is a custom region. For single/multi regions, it will be empty.",
+"deprecated": true,
+"description": "Deprecated: Use a single region service instead. Metadata about a custom region. This is only populated if the region is a custom region. For single/multi regions, it will be empty.",
 "id": "CustomRegionMetadata",
 "properties": {
 "optionalReadOnlyRegions": {
@@ -2586,7 +2587,7 @@
 "type": "array"
 },
 "unreachable": {
-"description": "Unordered list. Unreachable resources. Populated when the request sets ListOperationsRequest.return_partial_success and reads across collections e.g. when attempting to list all resources across all supported locations.",
+"description": "Unordered list. Unreachable resources. Populated when the request sets ListOperationsRequest.return_partial_success and reads across collections. For example, when attempting to list all resources across all supported locations.",
 "items": {
 "type": "string"
 },
@@ -2659,7 +2660,8 @@
 "id": "LocationMetadata",
 "properties": {
 "customRegionMetadata": {
-"description": "Possible configurations supported if the current region is a custom region.",
+"deprecated": true,
+"description": "Deprecated: Use a single region service instead. Possible configurations supported if the current region is a custom region.",
 "items": {
 "$ref": "CustomRegionMetadata"
 },
@@ -2667,7 +2669,8 @@
 },
 "multiRegionMetadata": {
 "$ref": "MultiRegionMetadata",
-"description": "The multi-region metadata if the current region is a multi-region."
+"deprecated": true,
+"description": "Deprecated: Use a single region service instead. The multi-region metadata if the current region is a multi-region."
 },
 "supportedHiveMetastoreVersions": {
 "description": "The versions of Hive Metastore that can be used when creating a new metastore service in this location. The server guarantees that exactly one HiveMetastoreVersion in the list will set is_default.",
@@ -2971,7 +2974,8 @@
 "type": "object"
 },
 "MultiRegionMetadata": {
-"description": "The metadata for the multi-region that includes the constituent regions. The metadata is only populated if the region is multi-region. For single region or custom dual region, it will be empty.",
+"deprecated": true,
+"description": "Deprecated: Use a single region service instead. The metadata for the multi-region that includes the constituent regions. The metadata is only populated if the region is multi-region. For single region or custom dual region, it will be empty.",
 "id": "MultiRegionMetadata",
 "properties": {
 "constituentRegions": {