You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/merchantapi_accounts_v1beta.accounts.issues.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,7 @@ <h3>Method Details</h3>
96
96
Args:
97
97
parent: string, Required. The parent, which owns this collection of issues. Format: `accounts/{account}` (required)
98
98
languageCode: string, Optional. The issues in the response will have human-readable fields in the given language. The format is [BCP-47](https://tools.ietf.org/html/bcp47), such as `en-US` or `sr-Latn`. If not value is provided, `en-US` will be used.
99
-
pageSize: integer, Optional. The maximum number of issues to return. The service may return fewer than this value. If unspecified, at most 50 users will be returned. The maximum value is 100; values above 100 will be coerced to 100
99
+
pageSize: integer, Optional. The maximum number of issues to return. The service may return fewer than this value. If unspecified, at most 50 issues will be returned. The maximum value is 100; values above 100 will be coerced to 100
100
100
pageToken: string, Optional. A page token, received from a previous `ListAccountIssues` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provided to `ListAccountIssues` must match the call that provided the page token.
101
101
timeZone: string, Optional. The [IANA](https://www.iana.org/time-zones) timezone used to localize times in human-readable fields. For example 'America/Los_Angeles'. If not set, 'America/Los_Angeles' will be used.
Copy file name to clipboardExpand all lines: docs/dyn/merchantapi_accounts_v1beta.accounts.termsOfServiceAgreementStates.html
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -103,11 +103,11 @@ <h3>Method Details</h3>
103
103
Returns:
104
104
An object of the form:
105
105
106
-
{ # This resource represents the agreement state for a given account and terms of service kind. The state is as follows: * If the merchant has accepted a terms of service: [accepted](TermsOfServiceAggrementState.accepted) will be populated, otherwise it will be empty * If the merchant must sign a terms of service: [required](TermsOfServiceAggrementState.required) will be populated, otherwise it will be empty. Note that both [required](TermsOfServiceAggrementState.required) and [accepted](TermsOfServiceAggrementState.accepted) can be present. In this case the `accepted` terms of services will have an expiration date set in the [valid_until](Accepted.valid_until) field. The `required` terms of services need to be accepted before `valid_until` in order for the account to continue having a valid agreement. When accepting new terms of services we expect 3Ps to display the text associated with the given terms of service agreement (the url to the file containing the text is added in the Required message below as [tos_file_uri](Accepted.tos_file_uri). The actual acceptance of the terms of service is done by calling accept on the [TermsOfService](TermsOfService) resource.
106
+
{ # This resource represents the agreement state for a given account and terms of service kind. The state is as follows: * If the merchant has accepted a terms of service, `accepted` will be populated, otherwise it will be empty * If the merchant must sign a terms of service, `required` will be populated, otherwise it will be empty. Note that both `required` and `accepted` can be present. In this case the `accepted` terms of services will have an expiration date set in the `valid_until` field. The `required` terms of services need to be accepted before `valid_until` in order for the account to continue having a valid agreement. When accepting new terms of services we expect 3Ps to display the text associated with the given terms of service agreement (the url to the file containing the text is added in the Required message below as `tos_file_uri`. The actual acceptance of the terms of service is done by calling accept on the `TermsOfService` resource.
107
107
"accepted": { # Describes the accepted terms of service. # The accepted terms of service of this kind and for the associated region_code
108
108
"acceptedBy": "A String", # The account where the acceptance was recorded. This can be the account itself or, in the case of subaccounts, the MCA account.
109
109
"termsOfService": "A String", # The accepted [termsOfService](google.shopping.merchant.accounts.v1main.TermsOfService).
110
-
"validUntil": { # Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp # When set, it states that the accepted [TermsOfService](google.shopping.merchant.accounts.v1main.TermsOfService) is only valid until the end of this date (in UTC). A new one must be accepted before then. The information of the required [TermsOfService](google.shopping.merchant.accounts.v1main.TermsOfService) is found in the [Required](Required) message.
110
+
"validUntil": { # Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp # When set, it states that the accepted `TermsOfService` is only valid until the end of this date (in UTC). A new one must be accepted before then. The information of the required `TermsOfService` is found in the `Required` message.
111
111
"day": 42, # Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
112
112
"month": 42, # Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
113
113
"year": 42, # Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
@@ -116,8 +116,8 @@ <h3>Method Details</h3>
116
116
"name": "A String", # Identifier. The resource name of the terms of service version. Format: `accounts/{account}/termsOfServiceAgreementState/{identifier}` The identifier format is: `{TermsOfServiceKind}-{country}` For example, an identifier could be: `MERCHANT_CENTER-US`
117
117
"regionCode": "A String", # Region code as defined by https://cldr.unicode.org/. This is the country the current state applies to.
118
118
"required": { # Describes the terms of service which are required to be accepted. # The required terms of service
119
-
"termsOfService": "A String", # The [termsOfService](google.shopping.merchant.accounts.v1main.TermsOfService) that need to be accepted.
120
-
"tosFileUri": "A String", # Full URL to the terms of service file. This field is the same as [TermsOfService.file_uri](TermsOfService.file_uri), it is added here for convenience only.
119
+
"termsOfService": "A String", # The `TermsOfService` that need to be accepted.
120
+
"tosFileUri": "A String", # Full URL to the terms of service file. This field is the same as `TermsOfService.file_uri`, it is added here for convenience only.
121
121
},
122
122
"termsOfServiceKind": "A String", # Terms of Service kind associated with the particular version.
123
123
}</pre>
@@ -137,11 +137,11 @@ <h3>Method Details</h3>
137
137
Returns:
138
138
An object of the form:
139
139
140
-
{ # This resource represents the agreement state for a given account and terms of service kind. The state is as follows: * If the merchant has accepted a terms of service: [accepted](TermsOfServiceAggrementState.accepted) will be populated, otherwise it will be empty * If the merchant must sign a terms of service: [required](TermsOfServiceAggrementState.required) will be populated, otherwise it will be empty. Note that both [required](TermsOfServiceAggrementState.required) and [accepted](TermsOfServiceAggrementState.accepted) can be present. In this case the `accepted` terms of services will have an expiration date set in the [valid_until](Accepted.valid_until) field. The `required` terms of services need to be accepted before `valid_until` in order for the account to continue having a valid agreement. When accepting new terms of services we expect 3Ps to display the text associated with the given terms of service agreement (the url to the file containing the text is added in the Required message below as [tos_file_uri](Accepted.tos_file_uri). The actual acceptance of the terms of service is done by calling accept on the [TermsOfService](TermsOfService) resource.
140
+
{ # This resource represents the agreement state for a given account and terms of service kind. The state is as follows: * If the merchant has accepted a terms of service, `accepted` will be populated, otherwise it will be empty * If the merchant must sign a terms of service, `required` will be populated, otherwise it will be empty. Note that both `required` and `accepted` can be present. In this case the `accepted` terms of services will have an expiration date set in the `valid_until` field. The `required` terms of services need to be accepted before `valid_until` in order for the account to continue having a valid agreement. When accepting new terms of services we expect 3Ps to display the text associated with the given terms of service agreement (the url to the file containing the text is added in the Required message below as `tos_file_uri`. The actual acceptance of the terms of service is done by calling accept on the `TermsOfService` resource.
141
141
"accepted": { # Describes the accepted terms of service. # The accepted terms of service of this kind and for the associated region_code
142
142
"acceptedBy": "A String", # The account where the acceptance was recorded. This can be the account itself or, in the case of subaccounts, the MCA account.
143
143
"termsOfService": "A String", # The accepted [termsOfService](google.shopping.merchant.accounts.v1main.TermsOfService).
144
-
"validUntil": { # Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp # When set, it states that the accepted [TermsOfService](google.shopping.merchant.accounts.v1main.TermsOfService) is only valid until the end of this date (in UTC). A new one must be accepted before then. The information of the required [TermsOfService](google.shopping.merchant.accounts.v1main.TermsOfService) is found in the [Required](Required) message.
144
+
"validUntil": { # Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp # When set, it states that the accepted `TermsOfService` is only valid until the end of this date (in UTC). A new one must be accepted before then. The information of the required `TermsOfService` is found in the `Required` message.
145
145
"day": 42, # Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
146
146
"month": 42, # Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
147
147
"year": 42, # Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
@@ -150,8 +150,8 @@ <h3>Method Details</h3>
150
150
"name": "A String", # Identifier. The resource name of the terms of service version. Format: `accounts/{account}/termsOfServiceAgreementState/{identifier}` The identifier format is: `{TermsOfServiceKind}-{country}` For example, an identifier could be: `MERCHANT_CENTER-US`
151
151
"regionCode": "A String", # Region code as defined by https://cldr.unicode.org/. This is the country the current state applies to.
152
152
"required": { # Describes the terms of service which are required to be accepted. # The required terms of service
153
-
"termsOfService": "A String", # The [termsOfService](google.shopping.merchant.accounts.v1main.TermsOfService) that need to be accepted.
154
-
"tosFileUri": "A String", # Full URL to the terms of service file. This field is the same as [TermsOfService.file_uri](TermsOfService.file_uri), it is added here for convenience only.
153
+
"termsOfService": "A String", # The `TermsOfService` that need to be accepted.
154
+
"tosFileUri": "A String", # Full URL to the terms of service file. This field is the same as `TermsOfService.file_uri`, it is added here for convenience only.
155
155
},
156
156
"termsOfServiceKind": "A String", # Terms of Service kind associated with the particular version.
Copy file name to clipboardExpand all lines: docs/dyn/merchantapi_accounts_v1beta.termsOfService.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ <h3>Method Details</h3>
93
93
94
94
Args:
95
95
name: string, Required. The resource name of the terms of service version. Format: `termsOfService/{version}` (required)
96
-
account: string, Required. The account for which to accept the ToS.
96
+
account: string, Required. The account for which to accept the ToS. Format: `accounts/{account}`
97
97
regionCode: string, Required. Region code as defined by [CLDR](https://cldr.unicode.org/). This is either a country when the ToS applies specifically to that country or 001 when it applies globally.
Copy file name to clipboardExpand all lines: docs/dyn/merchantapi_inventories_v1beta.accounts.products.regionalInventories.html
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,7 @@ <h3>Method Details</h3>
124
124
125
125
{ # Regional inventory information for the product. Represents specific information like price and availability for a given product in a specific `region`. For a list of all accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/9698880).
126
126
"account": "A String", # Output only. The account that owns the product. This field will be ignored if set by the client.
127
-
"availability": "A String", # Availability of the product in this region. For accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/3061342)
127
+
"availability": "A String", # Availability of the product in this region. For accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/6324448).
128
128
"customAttributes": [ # A list of custom (merchant-provided) attributes. You can also use `CustomAttribute` to submit any attribute of the data specification in its generic form.
129
129
{ # A message that represents custom attributes. Exactly one of `value` or `group_values` must not be empty.
130
130
"groupValues": [ # Subattributes within this attribute group. If `group_values` is not empty, `value` must be empty.
@@ -160,7 +160,7 @@ <h3>Method Details</h3>
160
160
161
161
{ # Regional inventory information for the product. Represents specific information like price and availability for a given product in a specific `region`. For a list of all accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/9698880).
162
162
"account": "A String", # Output only. The account that owns the product. This field will be ignored if set by the client.
163
-
"availability": "A String", # Availability of the product in this region. For accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/3061342)
163
+
"availability": "A String", # Availability of the product in this region. For accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/6324448).
164
164
"customAttributes": [ # A list of custom (merchant-provided) attributes. You can also use `CustomAttribute` to submit any attribute of the data specification in its generic form.
165
165
{ # A message that represents custom attributes. Exactly one of `value` or `group_values` must not be empty.
166
166
"groupValues": [ # Subattributes within this attribute group. If `group_values` is not empty, `value` must be empty.
@@ -208,7 +208,7 @@ <h3>Method Details</h3>
208
208
"regionalInventories": [ # The `RegionalInventory` resources for the given product from the specified account.
209
209
{ # Regional inventory information for the product. Represents specific information like price and availability for a given product in a specific `region`. For a list of all accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/9698880).
210
210
"account": "A String", # Output only. The account that owns the product. This field will be ignored if set by the client.
211
-
"availability": "A String", # Availability of the product in this region. For accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/3061342)
211
+
"availability": "A String", # Availability of the product in this region. For accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/6324448).
212
212
"customAttributes": [ # A list of custom (merchant-provided) attributes. You can also use `CustomAttribute` to submit any attribute of the data specification in its generic form.
213
213
{ # A message that represents custom attributes. Exactly one of `value` or `group_values` must not be empty.
214
214
"groupValues": [ # Subattributes within this attribute group. If `group_values` is not empty, `value` must be empty.
0 commit comments