Google Is Retiring the Content API for Shopping

Google has announced that the Content API for Shopping will be permanently shut down on 18 August 2026. Any retailer, ecommerce platform, feed management tool, or custom integration currently relying on the Content API must migrate to the new Merchant API before this date to avoid disruptions to product listings, inventory updates, and Google Shopping campaigns.

If your products are submitted to Google Merchant Center via an API connection, now is the time to start planning your migration.

What is the Content API for Shopping?

The Content API for Shopping has been Google’s primary method for programmatically managing Merchant Center accounts for many years.

It allows businesses and developers to:

• Upload product data to Google Merchant Center
• Update prices and inventory automatically
• Manage promotions
• Retrieve product performance information
• Link product data with Google Ads campaigns

The API has been widely used by ecommerce platforms, feed management tools, ERP systems, and custom-built integrations.

What is the Merchant API?

The Merchant API is Google’s next-generation replacement for the Content API.

Rather than using a single, monolithic API structure, Merchant API introduces a more modular architecture with dedicated APIs for:

• Products
• Inventories
• Accounts
• Data Sources
• Reports
• Promotions

This approach provides improved scalability, better performance, and easier future expansion. Google describes the Merchant API as a simplified and more robust way to manage Merchant Center accounts and product data across Google Shopping, Free Listings, and Google Ads.

Key Improvements

Benefits of Merchant API include:

• Modern API architecture
• Improved reporting capabilities
• Better scalability for large catalogues
• Enhanced inventory management
• Simplified resource structure
• Future-proof support from Google

Who Needs to Upgrade?

You need to migrate if you are:

Ecommerce Businesses Using Custom Integrations

If your website or platform directly communicates with Google Merchant Center using the Content API, migration is mandatory.

Feed Management Platforms

Businesses using third-party feed tools should check with their provider to confirm their migration plans.

Agencies and Developers

Any agency or developer maintaining custom Merchant Center integrations must update their applications before the shutdown date.

Multi-Channel Retailers

Retailers synchronising inventory, pricing, and product information across multiple channels through the Content API will need to migrate.

How to Check if You’re Using Content API

In Google Merchant Center:

1. Go to Settings
2. Select Data Sources
3. Review the Source column

If the source shows Content API, your integration requires migration.

Who May Not Need to Take Action?

Some ecommerce platforms handle API integrations automatically.

For example, merchants using platform-managed integrations may find their provider completes the migration on their behalf. However, it is still advisable to verify this directly with your platform or extension provider.

Important Migration Deadlines

Content API Users

All Content API users must complete migration by:

18 August 2026

After this date, Content API requests will no longer function.

How to Migrate from Content API to Merchant API

Step 1: Audit Your Current Integration

Identify:

• Which Content API services are being used
• Product feeds being managed
• Inventory updates
• Reporting integrations
• Promotional feeds

Document every API endpoint currently in use.

Step 2: Review Google’s Compatibility Documentation

Google has published migration guidance showing how Content API resources map to Merchant API resources.

Pay particular attention to:

• Resource naming changes
• Endpoint changes
• Authentication requirements
• Batch request handling

Step 3: Update API Endpoints

Merchant API uses a different URL structure.

Old Content API endpoints:

shoppingcontent.googleapis.com/content/v2.1/

New Merchant API endpoints:

merchantapi.googleapis.com/

Google recommends migrating services individually where possible.

Step 4: Update Resource References

One of the biggest changes is that Merchant API uses resource names instead of many of the numeric identifiers used within Content API.

Developers should review all code that references:

• Products
• Accounts
• Inventories
• Data sources

to ensure compatibility.

Step 5: Review Pricing Fields

Merchant API introduces changes to price formatting.

Many price fields now use:

• amountMicros
• currencyCode

instead of the previous pricing structure.

This often requires updates to custom integrations and data processing logic.

Step 6: Test in Parallel

Google recommends running Merchant API alongside your existing Content API implementation during testing.

This allows:

• Validation of product data
• Inventory verification
• Feed quality checks
• Reporting comparison

before fully switching production traffic.

Step 7: Complete Migration Well Before August 2026

Do not leave migration until the final weeks.

Large ecommerce sites often require:

• Development work
• QA testing
• Feed validation
• Merchant Center review

Starting early significantly reduces risk.

What Happens if You Don’t Migrate?

Failure to migrate before 18 August 2026 could result in:

• Product feeds stopping completely
• Inventory updates failing
• Pricing updates not being submitted
• Shopping Ads showing outdated information
• Product disapprovals
• Lost visibility in Google Shopping and Free Listings

For many retailers, this could directly impact sales and advertising performance.

Recommended Developer Documentation

Google has published comprehensive migration resources:

Merchant API Documentation

Merchant API Documentation

Migration Guide

Content API to Merchant API Migration Guide

Merchant API Latest Updates

Merchant API Release Updates

Content API Deprecation Notice

Content API Release Notes and Deprecation Information

Final Thoughts

The migration from Content API to Merchant API is not optional. Google has confirmed that the Content API for Shopping will cease operating on 18 August 2026, making migration essential for any business relying on API-based product management.

While the new Merchant API introduces some technical changes, it also delivers a more scalable and future-proof platform for managing products across Google Shopping, Free Listings, and Google Ads.

Businesses using custom integrations should begin auditing and testing now to ensure a smooth transition long before the deadline.

Let’s talk about how Yoma can support your business.