AABReady Update

Google Content API for Shopping Sunset 2026: What Developers Need to Do Now

Google's Content API for Shopping reached its sunset date on August 18, 2026. From September 1, integrations without an active extension can begin receiving intermittent HTTP 410 Gone errors. Developers maintaining custom Merchant Center integrations should review their migration to the Merchant API now.

Important 2026 migration status

• Content API for Shopping sunset: August 18, 2026
• Progressive intermittent failures began: September 1, 2026
• Requests without an active extension may return HTTP 410 Gone
• Full decommissioning is planned for early 2027

Who is affected?

The biggest risk is for developers, agencies, and merchants that directly maintain custom integrations using the Content API for Shopping. If your application calls legacy Shopping Content API endpoints, you should review the migration path to Merchant API.

Likely affected

• Custom Merchant Center API integrations
• Internal product-feed automation
• Agency-built feed systems
• Direct shoppingcontent.googleapis.com calls
• Integrations already seeing HTTP 410 errors

May not require direct action

Merchants using a third-party technology provider that manages the API integration may not need to migrate the API themselves. The provider may handle the transition.

What changes in Merchant API?

Merchant API is not a simple endpoint rename. Google has changed request structure, resource naming, some data types, batching behavior, and registration requirements.

Area	Content API	Merchant API
Base endpoint	shoppingcontent.googleapis.com	merchantapi.googleapis.com
Price amount	value: string	amountMicros: int64
Currency	currency	currencyCode
customBatch	Supported	Not supported; use parallel or HTTP batching
Developer registration	Legacy setup	Google Cloud project must be linked to Merchant Center

Quick migration checklist

1.Search your codebase for shoppingcontent.googleapis.com and Content API v2.1 calls.

2.Identify which Content API resources and methods your integration uses.

3.Register your Google Cloud project with your Merchant Center account.

4.Map existing methods to Merchant API sub-APIs and resources.

5.Update Price handling from value/currency to amountMicros/currencyCode.

6.Replace customBatch workflows with supported batching or asynchronous requests.

7.Test product, account, data source, inventory, and reporting flows separately.

8.Monitor application logs for HTTP 410 Gone responses during the transition.

Seeing HTTP 410 Gone?

If your Content API integration has started failing intermittently, the first step is to confirm whether the request is still using a deprecated Content API endpoint and whether your project has an active extension.

Do not treat repeated 410 responses as a temporary network problem. They can be part of Google's progressive service degradation process for the retired API.

Need help reviewing your Merchant API migration?

AABReady can help review your current integration, identify legacy Content API usage, and prepare a migration checklist for Merchant API.

Request Migration Review

Note: API requirements and timelines can change. Always confirm current migration requirements using Google's official Merchant API documentation before making production changes.