Google Ads Developer Blog: content

Merchant API is coming to Google Ads scripts starting April 22, 2026

neljapäev, 9. aprill 2026

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:

Omnichannel Support: Designed with Omnichannel in mind, though it provides backward compatibility for legacy separate online/local offer structures using the legacy_local flag.

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.

- Dora Sun - Google Ads API Team

Announcing the Merchant API Beta, the new version of the Content API for Shopping

teisipäev, 2. juuli 2024

redesignContent API for ShoppingGoogle's API improvement proposalslaunch statusHighlightsGRPCRESTcompatibility guides

Sub APIs with new features at launch: We are excited to announce an initial set of sub apis which comes with new features:

Data Sources: Allows multiple API feed creation and management, improved management of supplemental feeds via creation with linking to primary feeds, and support for other shopping feeds such as promotions.
Notifications: Receive push notifications for changes to a given account and product data.
Products: Unifying Product & ProductStatuses resources to streamline your workflow, new functionality to support inserting products into non API data sources.
Inventory: Improved management with the ability to remove in-store or regional inventories for your products.
Accounts: New terms of signing (ToS) functionality via the API and accessing account issues with multi-language support.
Local Feeds Partnership: For Point-of-sale data providers, more granular inventory management with availability status submissions and feed labels for inventory.
Promotions: Simplified promotion statuses with improved details and support for custom promotion attributes for faster iterations on new features.
Quota: Additional fields such as version, sub-api, and adjustments visible through the API to manage your quotas more efficiently.
Reports: A new NonProductPerformanceView table which provides insights into non-product performance data such as data on links leading to merchants’ homepage.

Merchant API is the future. Going forward, we will start launching new features primarily for the Merchant API which will have the newest Merchant Center features. We recommend you start using the Merchant API and would love to hear your feedback to help shape the future.

More features are on the way! Today's release contains many new improvements. Currently, there isn’t feature completeness between the Content API and Merchant API. We will have more features upcoming which are based on establishing parity, your feedback, and completely new features such as creation of file feeds with the Data source Merchant API.

Learn more and check out the following resources:

Access our Merchant API developer website to discover the Merchant API.

Review our Quickstart guide and Compatibility guides: to ramp up your understanding with how to start your integration with the Merchant API.

Learn more with our Merchant API release notes in the GRPC/REST reference sections to view our launched and future new features.

Check out our new Client Libraries and Samples to help speed up your implementations.

Contact our API support team for any issues or questions.

Help shape the future by providing feedback: Submit any feedback or suggestions.

Benji Rothman, on behalf of the Content API for Shopping Team

Changes to how you contact “Content API for Shopping” Support

esmaspäev, 10. juuni 2024

What's Happening? As we continue to improve our support experience, we are making changes to how you contact the Content API for Shopping support team. What's Changing? How you contact “Content API for Shopping” Support:

Shutting down current support path: Effective June 10, 2024, the support email address (shopping-api-support) and the Developer Forum will no longer accept support questions.

New support paths:

To reach our “Content API for Shopping” support team, please use our new Contact Us Form: link here
To reach our "Comparison Shopping Services API" support team, please use this Contact Us Form: link here
Going forward, these will be the only support paths available.

This change will help us better understand user needs and provide quicker solutions. We appreciate your partnership. In the meantime, please reference the following sites for integration/API information:

Content API for Shopping

Google Ads API

Comparison Shopping Services API

Your Content API for Shopping Team

Content API for Shopping: Automatic Quota

teisipäev, 2. aprill 2024

The Content API for Shopping now automatically increases your products and accounts quotas as your account grows. Because your API quota now changes dynamically, we have removed the static chart from our published limits guide. To check your current daily quota and usage, and current per minute quota, you can call the quotas.list service. The following errors are not API quota errors and can’t be resolved by automatic quota increases. They require you to request a quota increase.

too_many_items: Merchant quota exceeded

too_many_subaccounts: Maximum number of subaccounts reached

Automatic quota only applies to the products and accounts services. If you need an increased API quota for any other service, or if you’re hitting your daily API quota for the products or accounts services or need a temporary increase for the accounts or products services, contact us with the following information:

Your Merchant Center ID

Which methods you’ve reached your quota limits on

An estimation of how many calls per day you need for those methods

The reason why you need an increased quota

Note that our general quota policy is you should not update your products more than twice per day, and that you should check your accounts and account statuses not more than once per day. If you have any questions or concerns, please don't hesitate to contact us via the forum.

Benji Rothman, Content API for Shopping Team

Deprecating Content API Easy Onboarding In Merchant Center

kolmapäev, 13. detsember 2023

The Content API for Shopping easy onboarding authentication method and tab, which create a service account for you, will not be available in Merchant Center Next. Easy onboarding is still available in Merchant Center Classic. You can still use existing service accounts that you created using Merchant Center Classic. To set up a service account without using easy onboarding in Merchant Center Classic, follow these steps:

Ensure you have an existing cloud project or create a new one in the Google Cloud Console.

Generate or access your service account credentials.

Download the JSON private key from Google API Console. This JSON private key can be used in the same way as the one downloaded from Merchant Center previously.

Add the new service account as a user to your Merchant Center account. If you’re a third-party developer (and don’t have access to the Merchant Center UI for the account), your client will need to complete this step for you.

For more details, see the API documentation. If you have any questions or concerns, please don't hesitate to contact us via the forum.

Benji Rothman, Content API for Shopping Team

Buy on Google For Search and Shopping Deprecation

kolmapäev, 20. september 2023

Buy on Google for Search and Shopping will no longer be available starting September 26, 2023. All Merchant and Consumer support will end for Buy on Google on Search on November 25, 2023. The only exception is that the orders.get and orders.list methods will remain available for Search and Shopping until October 30, 2024, so that merchants can download their historical order data. See below for the specific timeline of when Buy on Google methods will no longer be available for the Search and Shopping program. June 28, 2023 onwards:

buyongoogleprograms.requestreview

buyongoogleprograms.onboard

buyongoogleprograms.activate

buyongoogleprograms.pause

September 30, 2023:

buyongoogleprograms.get

buyongoogleprograms.patch

October 31, 2023: All the orders related resources (orders, orderinvoices, orderreports, orderreturns, ordertrackingsignals) and all their underlying methods. The only exception is that the orders.get and orders.list methods will remain available for Search and Shopping until October 30, 2024, so that merchants can download their historical order data. If you are currently using the Buy on Google endpoints for Search and Shopping via the Content API, you will need to stop using these services for Search and Shopping before the dates listed above, as your requests will start to fail after that date. If you have any questions or concerns, please don't hesitate to contact us via the forum.

Benji Rothman, Content API for Shopping Team

Planned Content API maintenance from 15:00 UTC to 17:00 UTC on September 28, 2023

neljapäev, 14. september 2023

The Content API for Shopping will undergo planned maintenance on September 28, 2023, from 15:00 to 17:00 UTC.forum

Benji Rothman, Content API for Shopping Team

Launching the Merchant Support Service

neljapäev, 24. august 2023

Content API for ShoppingMerchantSupportdeveloper guide

Render account issues: provides UI elements with text in the language you select to display account issues to your merchants and redirect link to Merchant Center for merchants to request a re-review or perform other actions

Render product issues: provides UI elements with text in the language you select to display product issues to your merchants and redirect link to Merchant Center for merchants to request a re-review or perform other actions

MerchantSupportMerchantSupportMerchantSupportforum

Benji Rothman, Content API for Shopping Team

New Merchant IDs are now 64-bit in Content API for Shopping

esmaspäev, 24. aprill 2023

Content API for Shoppinginformed you last JuneforumBenji Rothman, Content API for Shopping Team

Issues from all destinations to be included in Productstatuses Service by default in the Content API for Shopping

kolmapäev, 19. aprill 2023

April 24, 2023productstatuses.listproductstatuses.getproductstatuses.listproductstatuses.getNo action is needed from youContent API for Shoppingproductstatuses.listproductstatuses.getdestinations[]productstatuses methodsProduct statuses documentationforumBenji Rothman, Content API for Shopping Team

Request Account Reviews with the Content API

kolmapäev, 7. detsember 2022

In the Content API for Shopping, your Merchant Center account and the products in it might be disapproved for various reasons. Historically, you have been able to see the status of your merchant center account for free listings and Shopping ads with the accountstatuses service. In Q1 2022 we introduced the freelistingsprogram and shoppingadsprogram services to provide more granular detail. You can now use the requestreview method on the freelistingsprogram and shoppingadsprogram services to request your account to be re-reviewed after making changes to fix your product and account data. For an in-depth explanation of how to use the freelistingsprogram and shoppingadsprogram services, please refer to the Free listings and Shopping ads guides. If you have any questions or concerns, please don't hesitate to contact us via the forum.

Benji Rothman, Content API for Shopping Team

Feed label support added to datafeeds service in Content API for Shopping

neljapäev, 10. november 2022

changes to country targeting for shopping productsfeedLabelfeedLabel

Country targeting update for products in Content API for Shopping and Google Ads API.

Feed label replaces target country in Content API for Shopping.

Country targeting in Shopping Ads campaigns is changing in August 2022.

What’s newMerchant Center & Content APIfeedLabeldatafeedsfeedLabel

products

datafeeds

DatafeedStatus

datafeedtargetfeedLabelcountrydatafeedtargettargetCountriesdatafeedsdatafeedsshippingproductsNotedatafeedsBehavior changesfeedLabelInsert and updateProducts.insertProducts.updatefeedLabelWINTERPRODUCTSfeedLabeltargetCountryfeedLabeltargetCountryUse feed labels to advertise products from specific feedsfeedLabelTargetingtargetCountryproductsshippingproductstargetCountriesdatafeedsOpt out of receiving products and datafeeds without a countryFeed label replaces target country in the Content API for Shopping - temporary exemptionfeedLabelContent API for Shopping forum

Ian Ballantyne, Content API for Shopping Team

Country targeting update for products in Content API for Shopping and Google Ads API

neljapäev, 22. september 2022

On August 10, 2022, we announced a change to country targeting for shopping products with the introduction of the feedLabel field.

See Feed label replaces target country in Content API for Shopping for the original announcement for the Content API for Shopping.

See Country targeting in Shopping Ads campaigns is changing in August 2022 for the original announcement for the Google Ads API.

What’s already changedGoogle Ads:feed_labelShoppingSettingfeed_labelMerchant Center & Content API:feed labelUse feed labels to advertise products from specific feeds

Products that have only feedLabel, and not targetCountry, if they were added in the Merchant Center UI.

Products with feed labels that aren’t two-letter country codes.

Products.updatefeedLabelofferIdfeedLabelsalePricePATCH https://shoppingcontent.googleapis.com/content/v2.1/{merchantId}/products/online:en:WINTERPRODUCTS:1111111111 { "salePrice": { "value": "17.99", "currency": "USD" } } Behavior summary:feedLabel

Insertion: You can only call Products.insert on products with a matching feedLabel and targetCountry. Currently, Products.insert might return an error if you don’t provide a matching targetCountry. This behavior hasn’t changed if you continue to use only targetCountry.

Targeting: If you set feedLabel to a valid 2-letter CLDR territory code, you must still set the shipping attribute of the products resource to the same country in order to target that country. For example, if you set a new feedLabel to “US”, you must also set the country field in the shipping attribute to “US”. If you don’t set both fields, the product might not be eligible to serve in that country. You can configure targeting for an entire feed in the Merchant Center UI.

Get/List: When you use Products.list or Products.get, you might see products that only have feedLabel (and not targetCountry) set if they were added in the Merchant Center UI.

Product IDs: Once a feedLabel is set for a product it becomes part of the product Id. This means you can’t modify the feedLabel for that product (this is similar to how language works). If you wish to change the feedLabel you will need to create a new product with a different product Id.

What’s coming nextProducts:Products.insertfeedLabeltargetCountryDatafeeds:datafeedsOpt out of receiving products and datafeeds without a countryFeed label replaces target country in the Content API for Shopping - temporary exemptionfeedLabelContent API for Shopping forum

Ian Ballantyne, Content API for Shopping Team

Feed label replaces target country in Content API for Shopping

kolmapäev, 10. august 2022

On August 23, 2022 we will gradually start updating the way country targeting works for shopping products.targetCountrycountryContent API for ShoppingtargetCountrycountryfeedLabelshippingIf you're accessing accounts whose product data you don’t have total control over and you are unsure whether the products or datafeeds will have ONLY a feedLabel field beginning in late August, we recommend you update your code to support the feedLabel field.productstargetCountrydatafeedscountryCountry targeting in Shopping Ads campaigns is changing in August 2022What’s already changedAugust 8, 2022Content API for ShoppingfeedLabelfeedLabelCLDR territory codestargetCountryfeedLabelfeedLabeltargetCountrythe idREST IDfeedLabeltargetCountryhereThis change to product identifier is backwards compatible, so existing REST IDs for existing products will continue to work without change.ImportantfeedLabelfeedLabeltargetCountryshippingWhat’s coming nextAugust 23, 2022feedLabeltargetCountryfeedLabeltargetCountrycountryfeedLabeltargetCountrycountryHow you’re impactedProductstargetCountryfeedLabelproductstargetCountryfeedLabelfeedLabelstargetCountryAll products inserted with a feedLabel instead of targetCountry, even if the feedLabel is a CLDR territory code, will not automatically target that country. You must explicitly set the countries you want to target via the shipping field.Datafeedsfeed labelcountry of salefeedLabelcountryfeedLabelfeedLabelscountryRecommendation for third party integrationstargetCountrycountryfeedLabelproducts.listtargetCountryfeedLabelcountrydatafeeds.listcountry

Make a request to products.list.

Filter your products to search for products where the targetCountry field does not exist on the product.

If any products appear, you have offers without a country in your Merchant Center.

Detailed ChangeshereDatafeeds ServicedatafeedsfeedLabelcountrydatafeeddatafeedscountryfeedLabelOpt out of receiving products and datafeeds without a countryFeed label replaces target country in the Content API for Shopping - temporary exemptionforum

Benji Rothman, Content API for Shopping Team

Merchant IDs as 64-bit in Content API for Shopping

teisipäev, 21. juuni 2022

Content API for Shoppingforum

Benji Rothman, Content API for Shopping Team

Upcoming enforcement of custom batch limits in Content API for Shopping

esmaspäev, 4. aprill 2022

custom batch

Maximum entries per request: 10,000

Maximum transfer size per request: 32Mb (The payload received from the client)

accounts.custombatch

accountstatuses.custombatch

accounttax.custombatch

datafeeds.custombatch

datafeedstatuses.custombatch

liasettings.custombatch

localinventory.custombatch

pos.custombatch

products.custombatch

productstatuses.custombatch

regionalinventory.custombatch

returnaddress.custombatch

returnpolicy.custombatch

shippingsettings.custombatch

request_too_large

batching guide1,000 entries per requestContent API for Shopping forum

Ian Ballantyne, Content API for Shopping Team

Introducing the new Merchant Center Status Dashboard

kolmapäev, 2. veebruar 2022

Merchant Center Status DashboardCheck the status of a serviceDashboardMerchant Center Status DashboardMerchant Center Help CenterSubscribe to the Status Dashboard RSS or JSON feeds

Go to the Status Dashboard.

At the bottom, click RSS Feed and copy the feed URL.

In your RSS reader, paste the URL to add the Status Dashboard feed.

If you want programmatic access to the Status Dashboard, for example to integrate it into your monitoring system, at the bottom, click JSON History.

Learn moreMerchant Center Help Centerpageforum

Ian Ballantyne, Content API for Shopping Team

Apache Log4j vulnerability

pühapäev, 12. detsember 2021

Apache Log4jWhat do you need to do?Apache Log4j Security Vulnerabilitiesforum--Stan Grinberg, Ads Developer Relations

Ads API apps must complete OAuth verification

neljapäev, 28. oktoober 2021

were classified as sensitiveverification process

Google Ads API & AdWords API

https://www.googleapis.com/auth/adwords

Content API for Shopping

https://www.googleapis.com/auth/content

DoubleClick Bid Manager API

https://www.googleapis.com/auth/doubleclickbidmanager

OAuth clients using the above scopes that remain unverified may have their existing credentials revoked and lose access to the above APIsexceptions for app verification

Google Ads API & AdWords API: googleadsapi-support@google.com

Content API for Shopping: support forum

DoubleClick Bid Manager API: support contact form

Adam Ohren, Google Ads API Team

Reminder of upcoming Content API for Shopping v2.0 sunset date

teisipäev, 31. august 2021

announcedbeginning September 30, 2021, we will end support for the legacy v2.0 of the Content API for Shoppingless than 1 month until support for v2.0 will end on September 30, 2021To avoid disruption we strongly encourage you to migrate to v2.1 imminently.What do I need to know?

Using a Merchant Center ID

Using a Cloud Project ID

multi-client account (MCA)September 30, 2021Where do I get support?migration guidenew features available in v2.1Inventory.setrelease of partial product updatesupdate of the default runtime to v2.1Content API for Shopping forum

Ian Ballantyne, Content API for Shopping Team

Ads Developer Blog

Merchant API is coming to Google Ads scripts starting April 22, 2026

Announcing the Merchant API Beta, the new version of the Content API for Shopping

Changes to how you contact “Content API for Shopping” Support

Content API for Shopping: Automatic Quota

Deprecating Content API Easy Onboarding In Merchant Center

Buy on Google For Search and Shopping Deprecation

Planned Content API maintenance from 15:00 UTC to 17:00 UTC on September 28, 2023

Launching the Merchant Support Service

New Merchant IDs are now 64-bit in Content API for Shopping

Issues from all destinations to be included in Productstatuses Service by default in the Content API for Shopping

Request Account Reviews with the Content API

Feed label support added to datafeeds service in Content API for Shopping

Country targeting update for products in Content API for Shopping and Google Ads API

Feed label replaces target country in Content API for Shopping

Merchant IDs as 64-bit in Content API for Shopping

Upcoming enforcement of custom batch limits in Content API for Shopping

Introducing the new Merchant Center Status Dashboard

Apache Log4j vulnerability

Ads API apps must complete OAuth verification

Reminder of upcoming Content API for Shopping v2.0 sunset date

Sildid

Archive