Google Content API for Shopping removal
Stopped workingSubscribe to Google Content API for ShoppingShare
Google Content API for Shopping endpoints stopped working on September 1, 2026. Calls to /content/* now fail, returning HTTP 410 Gone status codes intermittently for clients lacking an active extension.
Calls it hits
/content/*
What to use instead of these calls
Migrate to the Merchant API v1 (merchantapi.googleapis.com) following the Merchant API migration guide. Because the Merchant API is a different API with its own resources and sub-APIs, moving over requires rewriting the integration or requesting an extension from Google.
The Merchant API is a different API with its own resources and sub-APIs: moving over is a rewrite of the integration, or an extension request to Google.
In Google Content API for Shopping's words
Starting September 1, 2026 , requests sent to Google Content API for Shopping endpoints by clients without an active extension will intermittently fail with an HTTP 410 Gone status code.
Facts
- API
- Google Content API for Shopping
shoppingcontent.googleapis.com - Kind
- Removal
- Takes effect
- September 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Google Content API for Shopping's own pages
Questions
When does this change take effect?
Calls to /content/* on Google Content API for Shopping stopped working on September 1, 2026.
What happens to calls after September 1, 2026?
They have failed since September 1, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.