最新动态
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
获取有关新功能、bug 修复和版本更新的最新公告。
2025 年 7 月
2025 年 7 月
新版变化:
Merchant API (v1) - Content API for Shopping 的正式替代产品现已正式发布。
这意味着,今后 Merchant API 中将仅包含 v1alpha 和 v1 子 API,大多数 v1beta 版本将升级为 v1。敬请关注更多信息。
有新资源。
- Product Studio API(Alpha 版)中的图片资源利用生成式 AI 来生成新的商品背景、移除图片背景以及提高图片分辨率。
- Merchant in Accounts API 上的结账功能可让您创建、更新、删除和获取结账设置。
- Accounts API 中的线上退货政策已迁移,用户功能保持不变。为了保持一致性,我们进行了一些小幅技术改进,例如移除了过时的字段并重命名了现有字段。
- Accounts API 中 AccountRelationship 资源中的
AccountIdAlias
使用的是用户定义的别名,而不是您的内部 ID(账号 ID)。这样一来,您就可以更轻松地管理复杂的账号结构,例如使用面向市场的用户定义别名,而不是内部 ID。
App Script 用户现在可以访问 Merchant API。
问题解决 API 中现已提供新的 AggregateProductStatuses
方法,用于查询有关商品状态的合并统计信息。
具体变化:
即将推出的功能:
- 通过 Model Context Protocol (MCP) 服务器 (v1alpha) 进行访问。
2025 年 5 月
2025 年 5 月
新版变化:
- 我们推出了两个新的子 API。
- 订单跟踪
支持商家订单跟踪历史记录,以便向客户提供精确的配送时间预估。其信号还可让增强版商品详情显示免费快速配送信息。
- 问题解决功能可让您以与 Merchant Center 界面中相同的方式访问诊断内容和支持操作。
- 账号子 API 中提供了新资源。
- Products 子 API 中提供了一种新方法。
- 借助
ProductsUpdate
,您可以更新单个商品,而无需提供 ProductInput
所需的所有字段。
具体变化:
即将推出的功能:
- 弃用并将在未来移除
DataSources
和产品的渠道字段。
- 在报告子 API 下的
productView
表中,针对 clickPotentialRank
推出了更新后的定义:
- 基于
clickPotential
的商品排名已归一化为介于 1 到 1000 之间的值。
clickPotentialRank
较低的商品在满足搜索查询条件的商家商品中仍具有最高的点击潜力。这是一项非破坏性变更,可能会于 2025 年 7 月 1 日推出。
AccountRelationship
资源中的 AccountIdAlias
可帮助您更好地管理复杂的账号结构。例如,购物平台会使用用户定义的别名,而不是商家的内部 ID(例如账号 ID)。
2025 年 4 月
2025 年 4 月
新版变化:
具体变化:
- 我们现在支持数据源子 API 的目标平台(在 Merchant Center 中称为“营销方式”)。
- 我们对该资源进行了多项调整,建议您查看账号版本说明了解详情。
- 根据 Content API 中
accounttax
的弃用情况,Products 子 API 中的字段 taxes
和 tax_category
也已弃用。
即将推出的功能:
- 我们已将您的反馈纳入考虑范围,并正在努力改进 API 开发者文档的多个方面。
- 请继续关注并更频繁地回来查看,也欢迎随时向我们提供更多反馈。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-22。
[null,null,["最后更新时间 (UTC):2025-08-22。"],[],[],null,["# Latest updates\n\nGet the latest announcements on new features, bug fixes, and release updates.\n\n\u003cbr /\u003e\n\nJuly 2025\n\n\u003cbr /\u003e\n\nJuly 2025\n---------\n\nWhat's new:\n\n- Merchant API (v1) - The official successor of the Content API for Shopping\n is now generally available.\n\n This means that going forward, there will only be v1alpha and v1 sub-APIs\n within Merchant API, with most v1beta versions graduating to v1. Stay tuned\n for more information.\n- New resources are available.\n\n - [Image resource](https://developers.google.com/merchant/api/release-notes/rest/product-studio) in Product Studio API (alpha) leverages genAI to generate new product backgrounds, remove image background, and upscale image resolution.\n - [Checkout on Merchant](https://developers.google.com/merchant/api/reference/rest/accounts_v1/accounts.programs.checkoutSettings) in Accounts API provides the ability to create, update, delete, and get your checkout settings.\n - [Online Return Policy](https://developers.google.com/merchant/api/reference/rest/accounts_v1/accounts.onlineReturnPolicies) in Accounts API has been migrated, with user functionality remaining unchanged. Small technical improvements, such as outdated fields and renaming existing fields have been removed for consistency.\n - `AccountIdAlias` in the [AccountRelationship](https://developers.google.com/merchant/api/reference/rest/accounts_v1/accounts.relationships) resource in Accounts API uses a user-defined alias instead of your internal ID (account ID). This makes it easier to manage complex account structures, such as use of user-defined alias for your marketplace instead of your internal ID.\n- Access to Merchant API is now available for [Apps Script](https://developers.google.com/apps-script/advanced/merchant-api)\n users.\n\n- A new [`AggregateProductStatuses`](https://developers.google.com/merchant/api/reference/rest/issueresolution_v1/accounts.aggregateProductStatuses)\n method is now available in the Issue resolution API to query amalgamated\n statistics about product statuses.\n\nWhat's changed:\n\n- Ability to create standalone accounts for storebuilders and CSSs. Previously merchant accounts were created under a single Multi-Client Account (MCA).\n- Click potential rankings in the [`productView`](https://developers.google.com/merchant/api/reference/rest/reports_v1/accounts.reports#productview)\n table under the [Reporting sub-API](https://developers.google.com/merchant/api/reference/rest/reports_v1/accounts.reports#productview). Now, ranking of products based on `clickPotential` is\n normalized to values between 1 and 1000. Products with low `clickPotentialRank`\n still have the highest `click potential` among the merchant's products that\n fulfill the search query conditions.\n\n | **Note:** This is not a breaking change.\n\nWhat's coming:\n\n- Access through Model Context Protocol (MCP) server (v1alpha).\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nMay 2025\n\n\u003cbr /\u003e\n\nMay 2025\n--------\n\nWhat's new:\n\n- We launched two new sub-APIs.\n - [Order tracking](/merchant/api/release-notes/rest/ordertracking) supports business order tracking history to provide precise and accurate shipping estimates to customers. Its signals also enable enhanced listings with [free and fast shipping](https://support.google.com/merchants/answer/9780562).\n - [Issue resolution](/merchant/api/release-notes/rest/issueresolution) provides access to diagnostic content and support actions in the same way as it's available in the Merchant Center UI.\n- New resources are available in the [Accounts sub-API](https://developers.google.com/merchant/api/release-notes/rest/accounts).\n - [`OmnichannelSettings`](/merchant/api/reference/rest/accounts_v1/accounts.omnichannelSettings) manages the account configuration for omnichannel serving, such as Free Local Listings (FLL) and Local Inventory Ads (LIA).\n - [`LfpProviders`](/merchant/api/reference/rest/accounts_v1/accounts.omnichannelSettings.lfpProviders) connects to Local Feeds Partnership (LFP) partners for inventory data.\n - [`GbpAccounts`](/merchant/api/reference/rest/accounts_v1/accounts.gbpAccounts) connects to Google Business Profile account for local store data.\n - [`OnlineReturnPolicy`](/merchant/api/reference/rest/accounts_v1/accounts.onlineReturnPolicies) provides the ability to create, delete and update your online policies.\n- A new method is available in the [Products sub-API](/merchant/api/reference/rest/products_v1/accounts.productInputs/patch).\n - `ProductsUpdate` lets you update individual products without the need to provide all the fields required for `ProductInput`.\n\nWhat's changed:\n\n- The maximum [`pageSize`](/merchant/api/guides/reports/paging) increased from 250 to 1000 rows per API call.\n- A delay that existed for product insertion, promotions, product reviews, and merchant reviews after [`DataSources`](/merchant/api/release-notes/rest/datasources) creation is fixed.\n\nWhat's coming:\n\n- Deprecation and future removal of the channel field for [`DataSources`](/merchant/api/release-notes/rest/datasources) and products.\n- Launch of an updated definition for `clickPotentialRank` in the [`productView`](/merchant/api/reference/rest/reports_v1/accounts.reports#productview) table under the [Reporting sub-API](/merchant/api/reference/rest/reports_v1/accounts.reports#productview):\n - Ranking of products based on `clickPotential` is normalized to values between 1 and 1000.\n - Products with low `clickPotentialRank` still have the highest click potential among the merchant's products that fulfill the search query conditions. This is a non-breaking change that might be launched on July 1, 2025.\n- The `AccountIdAlias` in the [`AccountRelationship`](/merchant/api/reference/rest/accounts_v1/accounts.relationships) resource, makes it possible to better manage complex account structures. For example, marketplaces use a user-defined alias instead of the merchant's internal ID, such as account ID.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nApril 2025\n----------\n\n\u003cbr /\u003e\n\nApril 2025\n\n\u003cbr /\u003e\n\nWhat's new:\n\n- We launched a new sub-API.\n - [Product Studio (ALPHA)](https://developers.google.com/merchant/api/release-notes/rest/product-studio) leverages genAI to generate and optimize product titles and descriptions. You need to sign this form to [request access](https://docs.google.com/forms/d/e/1FAIpQLScODIkMC48Zfm1L5-110Qcq_OIEnCtmB_hYez6xUhnygGFGAg/viewform).\n- New resources are available in the Accounts sub-API.\n - [`AutomaticImprovements`](https://developers.google.com/merchant/api/reference/rest/accounts_v1/accounts.automaticImprovements) manages the opt-in to three automatic update features provided by the Google Merchant Center platform:\n - [Automatic item updates](https://support.google.com/merchants/answer/12157888?visit_id=638814365177534603-3273330231&rd=1)\n - [Automatic image improvements](https://support.google.com/merchants/answer/12724659?visit_id=638814365177534603-3273330231&rd=1)\n - [Automatic shipping improvements](https://support.google.com/merchants/answer/10027038)\n - [`AccountService`](https://developers.google.com/merchant/api/reference/rest/accounts_v1/accounts.services) and [`AccountRelationship`](https://developers.google.com/merchant/api/reference/rest/accounts_v1/accounts.relationships) resources manage relationships and establish services to service providers.\n- We launched three fields for [`AutomatedDiscounts`](https://developers.google.com/merchant/api/reference/rest/products_v1/accounts.products#AutomatedDiscounts) in the [Products sub-API](https://developers.google.com/merchant/api/reference/rest/products_v1/accounts.products?sjid=1758643364882920043-NA) to retrieve real-time prices for products opted into [Google Automated Discounts (GAD)](https://support.google.com/merchants/answer/15010391?hl=en-IE&sjid=16937598938794048439-EU#).\n\nWhat's changed:\n\n- We now support destinations, known as marketing methods in Merchant Center for the [DataSources sub-API](https://developers.google.com/merchant/api/release-notes/rest/datasources).\n- We made multiple adjustments to the resource and recommend to review the [Accounts release notes](https://developers.google.com/merchant/api/release-notes/rest/accounts) for more details.\n- The fields `taxes` and `tax_category` in the [Products sub-API](https://developers.google.com/merchant/api/reference/rest/products_v1/accounts.products?sjid=1758643364882920043-NA) are deprecated in line with the deprecation of `accounttax` in the Content API.\n\nWhat's coming:\n\n- We've taken your feedback into consideration and are working on several areas to improve API developer documentation.\n- Stay tuned and check back in more frequently, and feel free to [give us more feedback](/merchant/api/support/give-feedback)."]]