Content API for Shopping is dying August 2026: migrate now

Google announced the Content API for Shopping will be fully sunset on August 18, 2026. The v1beta of the replacement Merchant API already shut down on February 28, 2026. If your feed management tools or custom integrations still reference the Content API, you need to migrate to the Merchant API v1 now.

This isn't optional. After August 18, API calls to the Content API endpoint will return errors. Your automated feed syncs will break. Products will stop updating in Merchant Center.

What changed

The new Merchant API v1 splits functionality into sub-APIs. Everything you used to do through one endpoint now lives in separate services.

Migration checklist

Walk through each step. Skip nothing.

1. Update your API endpoint from content.googleapis.com to merchantapi.googleapis.com
2. Replace Content API resource paths with the new sub-API patterns (Products, Accounts, Reports, Promotions)
3. Update authentication scopes if your OAuth consent screen uses Content API scopes
4. Test with v1 endpoints (not v1beta, which is already dead)
5. Update response parsing logic for the new JSON structure
6. Run your integration tests against the v1 sandbox before switching production

Example: old vs. new endpoint

// Old (Content API - dies August 18)
GET https://content.googleapis.com/content/v2.1/{merchantId}/products

// New (Merchant API v1)
GET https://merchantapi.googleapis.com/products/v1beta/{parent=accounts/*}/products

Tools affected

If you use DataFeedWatch, Channable, GoDataFeed, or custom scripts that call the Content API, check with your vendor for their migration timeline.

Most major feed tools have already migrated. Custom integrations built in-house are the biggest risk. If your dev team built a feed sync script 2 years ago, it almost certainly uses the Content API. Find it and update it before August.