Примечания к выпуску API учетных записей торговцев
Оптимизируйте свои подборки
Сохраняйте и классифицируйте контент в соответствии со своими настройками.
{% включают "/merchant/api/release-notes/___accounts.md" %}
Если не указано иное, контент на этой странице предоставляется по лицензии Creative Commons "С указанием авторства 4.0", а примеры кода – по лицензии Apache 2.0. Подробнее об этом написано в правилах сайта. Java – это зарегистрированный товарный знак корпорации Oracle и ее аффилированных лиц.
Последнее обновление: 2025-07-25 UTC.
[null,null,["Последнее обновление: 2025-07-25 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eexternalAccountId\u003c/code\u003e predicate for filtering accounts has moved to the service level, requiring an update to filter syntax.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eprovider\u003c/code\u003e field in account-related requests now uses provider IDs (\u003ccode\u003eproviders/123\u003c/code\u003e) or specific provider names (\u003ccode\u003eproviders/GOOGLE_ADS\u003c/code\u003e, \u003ccode\u003eproviders/GOOGLE_BUSINESS_PROFILE\u003c/code\u003e) instead of account names (\u003ccode\u003eaccounts/123\u003c/code\u003e), though account names are still supported for backwards compatibility.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003epromotions_consent\u003c/code\u003e field in the \u003ccode\u003eBusinessIdentity\u003c/code\u003e resource is now marked as \u003ccode\u003eREQUIRED\u003c/code\u003e for updates, clarifying that it cannot be updated to \u003ccode\u003eUNSPECIFIED\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDocumentation improvements were made across various resources in the accounts bundle, including clearer descriptions of \u003ccode\u003eupdate_mask\u003c/code\u003e fields and supported carriers for \u003ccode\u003eShippingSettings\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eA new \u003ccode\u003eforce\u003c/code\u003e parameter has been launched for the \u003ccode\u003eAccounts.delete\u003c/code\u003e method.\u003c/p\u003e\n"]]],["Key changes include: enhancing documentation for `AccountsService.List`, setting a 10-minute default deadline for RPC methods, and adding program names to `accounts.programs`. The `User.accessRights` became `REQUIRED` and `AccountsService.ListAccounts` now uses eventual consistency. Updates include deprecating the `users` field, clarifying `user` field as `OPTIONAL`, and moving the `externalAccountId` predicate. The `promotions_consent` was made required. The `provider` field was updated to allow `GOOGLE_ADS` and `GOOGLE_BUSINESS_PROFILE`. There were also improvements made to documentation and various fields were marked as required.\n"],null,["# Merchant Accounts API release notes\n\nWeek of Jul 1, 2025\n-------------------\n\n- Launch of CheckoutSettings resource which allow API users to create, update, delete, get checkoutSettings.\n\nWeek of May 26, 2025\n--------------------\n\n- It is now possible to filter accounts by `capabilities`. At the moment the\n only possible value is `CAN_UPLOAD_PRODUCTS`. This filter lets you retrieve\n accounts that are capable of uploading products. This means the following\n clauses can now used at the account level:\n\n - `capabilities:CAN_UPLOAD_PRODUCTS`\n - `-capabilities:CAN_UPLOAD_PRODUCTS`\n - `NOT capabilities:CAN_UPLOAD_PRODUCTS` For more information, see [filtering guide](/merchant/api/guides/accounts/filter).\n- Launch of the read-only access right. Users with the read-only access right\n can view merchant data, but can't modify it.\n\nWeek of May 19, 2025\n--------------------\n\n- Updated documentation for program API, removing incorrect statement that `Enable`/`Disable` methods are restricted to admin users.\n\nWeek of May 12, 2025\n--------------------\n\n- Launch of Online Return Policy resource which allow API users to create, update, and delete return policies.\n- Launch of OmnichannelSettingsService and OmnichannelSetting resource which allows API users to manage their omnichannel experience.\n- Launch of LfpProvidersService and LfpProvider resource which allows API users to manage their Local Feeds Partnership relationship.\n- Launch of GbpAccountsService and GbpAccount resource which allows API users to manage their Google Business Profile.\n - Launch service type LocalListingManagement in AccountService, which links business group which is used for Local Inventory Ads or Free Local Listings.\n\nWeek of Apr 28, 2025\n--------------------\n\n- Launch of AccountService and AccountRelationship resources which allow API users to manage relationships and establish services to service providers.\n\nWeek of Apr 14, 2025\n--------------------\n\n- `TermsOfServiceService.AcceptTermsOfService` now returns the\n `TermsOfServiceAgremeentState` that was accepted wrapped in a response type.\n\n- The verb of the `TermsOfServiceService.AcceptTermsOfService` action is now\n `POST` (used to be `GET`).\n\n- Clarified that `AccountsService.ListSubAccounts` needs to be called using the\n `accounts/...` format (rather than `providers/...`). This is to avoid having\n this method falling out of the `accounts` scope (that means\n `GET accounts/123:listSubAccounts` rather than\n `GET providers/123:listSubAccounts`).\n\nWeek of Mar 31, 2025\n--------------------\n\n- For filtering accounts, the `externalAccountId` filter was announced\n deprecated in the week of Dec 2, 2024 and is now unavailable. This means that\n filtering by `externalAccountId` is now only possible on the `service` level. A\n filter such as `relationship(externalAccountId = \"foo\")` will no longer work and\n needs to be expressed as `relationship(service(externalAccountId = \"foo\"))`.\n\n- Clarified in `AccountsService` documentation that one can't create standalone\n accounts.\n\nWeek of Mar 3, 2025\n-------------------\n\n-The [`accounts.onlineReturnPolicies#SeasonalOverride`](/merchant/api/reference/rest/accounts_v1beta/accounts.onlineReturnPolicies#SeasonalOverride)\nhas been refactored to improve clarity and consistency. These updates include:\n\n- **Field Renaming:**\n - `begin` is now `start_date`.\n - `end` is now `end_date`.\n- **Field Removal:**\n - The deprecated `policy` field has been removed.\n\n-Developers should update their code to reflect these changes.\n\nLaunch of `AutomaticImprovements` service that you can use to manage the\nfollowing:\n\n- [Item updates](https://support.google.com/merchants/answer/12157888)\n- [Image improvements](https://support.google.com/merchants/answer/12724659)\n- [Shipping improvements](https://support.google.com/merchants/answer/10027038)\n\nFor more information, see [Enable automatic improvements](/merchant/api/guides/automatic-improvements/overview).\n\nWeek of Feb 17, 2025\n--------------------\n\nRemoved the `callerHasAccessToProviderFilter()` predicate from the account\nfilter.\n\nWeek of Feb 10, 2025\n--------------------\n\n- Improved documentation for the `AccountsService.List` method. It returns all\n the accounts the user has access to, not just standalone accounts.\n\n- Added default deadline of 10 minutes for all RPC methods.\n\n- Added the list of available program names to\n [`accounts.programs`](/merchant/api/reference/rest/accounts_v1beta/accounts.programs)\n resource description.\n\n- `User.accessRights` is now `REQUIRED` affecting both the `UserService.Create`\n and `AccountsService.CreateAndConfigure` methods.\n\nWeek of Jan 27, 2025\n--------------------\n\n`AccountsService.ListAccounts` (and transitively\n`AccountsService.ListSubAccounts`) now return accounts in an eventual consistent\nmanner rather than being a strong read.\n\nWeek of Jan 20, 2025\n--------------------\n\nThe `users` field of the `CreateAndConfigureAccountRequest` is deprecated in\nfavor of a new `user`. The `CreateUserRequest` that was referenced contains\nthe `parent` field that is not required in the context of the\n`CreateAndConfigureAccountRequest`.\n\nWeek of Jan 6, 2025\n-------------------\n\nThe `user` field of the `CreateUserRequest` message is now correctly marked as\n`OPTIONAL`.\n\nThe `domain` field in returned errors is now populated with\n`merchantapi.googleapis.com` instead of `global`\n\nWeek of Dec 2, 2024\n-------------------\n\nFor filtering accounts, the `externalAccountId` predicate is moved to the\n[`service`](/merchant/api/guides/accounts/filter#service_filters)\nlevel from the\n[`relationship`](/merchant/api/guides/accounts/filter#relationship_filters)\nlevel. So, a filter `relationship(externalAccountId = \"foo\")` would now need to\nbe written as `relationship(service(externalAccountId = \"foo\"))`. The old format\nis still supported for backwards compatibility, but is deprecated and will throw\nan error in the near future. All documentation will only mention the new format.\n\nWeek of Nov 18, 2024\n--------------------\n\nThe provider in the `CreateAndConfigureAccountRequest.service.provider` field\nmay now also be one of `providers/GOOGLE_ADS` or\n`providers/GOOGLE_BUSINESS_PROFILE`. Other accounts should be referred to as\n`providers/123` (rather than `accounts/123`). This means that the field is no\nlonger annotated as an account reference. However, it is still also possible to\nuse account names such as `accounts/123` for backwards compatibility.\n\nThe provider in the `ListSubAccountsRequest` should now be of the form\n`providers/123`, but for backwards compatibility it will still be possible to\nuse `accounts/123`.\n\nWeek of Nov 4, 2024\n-------------------\n\nMark `promotions_consent` `REQUIRED` (from `OPTIONAL`) in `BusinessIdentity`\nresource. This affects the update method only. This is to clarify that it is not\npossible to update `promotions_consent` to `UNSPECIFIED`. This was already not\npossible, but the error is now more descriptive and the field is correctly\nannotated.\n\nWeek of Oct 28, 2024\n--------------------\n\nImprove documentation of various resources of the Accounts sub-API such as\n`User`, `Homepage`, `BusinessInfo` and so on.\n\nWeek of Oct 21, 2024\n--------------------\n\nImprove documentation of `update_mask` fields in update requests throughout to\nspecifically point out which fields are supported for update.\n\nAdded google business help center link for supported carriers to the external\ndoc of `ShippingSettings` resource\n\nWeek of Oct 14, 2024\n--------------------\n\nMark `provider` as `REQUIRED` in\n`AccountsService.CreateAndConfigureAccountRequest.AddAccountService`.\n\nMake `update_mask` optional throughout Accounts sub-API (e.g. business identity,\nbusiness information, homepage etc.) and retroactively for the\n`ConversionSources` resource.\n\nAdded `overwrite` parameter to `ClaimHomepageRequest`.\n\nWeek of Sep 30, 2024\n--------------------\n\nLaunch of 'force' parameter for 'Accounts.delete' method.\n\nWeek of Sep 23, 2024\n--------------------\n\nMark `region_code` and `kind` as `REQUIRED` in\n`RetrieveLatestTermsOfServiceRequest`.\n\nWeek of Sep 16, 2024\n--------------------\n\nChanged the type of `time_zone` parameter to string in the\n`ListAccountIssuesRequest`\n\nWeek of Aug 12, 2024\n--------------------\n\nAdded `korean_business_registration_number` field to the `BusinessInfo`\nresource.\n\nWeek of May 27, 2024\n--------------------\n\nBeta launch of Accounts sub-API"]]
