The Content API for Shopping will sunset on August 18, 2026, to be replaced by the Merchant API. This migration provides a shift toward more robust, scalable, and feature-rich integrations. For Google Ads scripts users, the Google Ads scripts editor will begin rolling out Merchant API support on April 22, 2026. While the Content API for Shopping will remain available until its sunset, here’s what to expect from the Merchant API.
Understanding the Merchant API
The Merchant API offers important changes and improvements over the Content API for Shopping:
-
Modular Design: The Merchant API is broken down into
sub-APIs. This allows for:
- Faster access to new features and updates.
- Easier versioning and maintenance.
- Reduced disruption, as changes in one sub-API are less likely to impact others.
-
New Features & Capabilities:
- Google Product Studio API: Leverage generative AI features.
- Reviews APIs: Upload and manage product and store reviews.
- Notifications API: Enable notifications for changes.
- Expanded Data Source Management: Create and manage various data source types, including:
-
Omnichannel Support: Designed with Omnichannel in mind,
though it provides backward compatibility for legacy separate online/local
offer structures using the
legacy_localflag.
Take a look at the Merchant API migration guide for more detail on the changes between APIs.
How to get started
The Merchant API will be available as an Advanced API in the Google Ads scripts editor, just as the Content API is.
If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.
