API · archived
Google will sunset the Content API for Shopping on 18 August 2026, replacing it with the newer Merchant API
left 18 Aug 2026
Quick answers
- Is it true that Google is sunsetting the Content API for Shopping?
- Yes — and the date has already passed (18 Aug 2026). The Content API for Shopping (v2.1) is how merchants and the platforms serving them programmatically manage Google Merchant Center — product listings, inventory, prices, promotions, and account data behind Google Shopping and free product listings.
- When did it take effect?
- 18 Aug 2026 (already passed). Verified against the vendor's own announcement.
- What should I use instead?
- Move to the Merchant API.
What this means for you
The Content API for Shopping (v2.1) is how merchants and the platforms serving them programmatically manage Google Merchant Center — product listings, inventory, prices, promotions, and account data behind Google Shopping and free product listings. Google will sunset it on 18 August 2026 in favor of the new Merchant API. After the sunset, integrations that still call the old Content API endpoints stop functioning, which for a store means its catalog stops syncing to Merchant Center — a directly revenue-affecting outage. E-commerce platforms, feed-management and product-data tools, and any custom catalog-sync integration are affected.
Where to go
Move to the Merchant API. Google restructured the single Content API surface into several resource-specific sub-APIs (products, inventories, accounts, reporting, and more), so migration is an endpoint-by-endpoint remapping of your calls plus a re-test of the full feed-sync flow, rather than a one-line change. Google offers an extension-request process for teams that need additional time past the sunset date. Because a broken catalog sync stops products from appearing on Google Shopping, start the port well before 18 August 2026 and validate against live Merchant Center data.
- Google Merchant API — the official successor Google directs Content API users to
If you run a store on Google Shopping — or build the software that other stores use to get there — the pipe that carries your catalog into Google Merchant Center is being replaced. Google will sunset the Content API for Shopping on 18 August 2026 and move everything to the new Merchant API.
The Content API for Shopping (v2.1) is the long-standing programmatic interface to Merchant Center: it is what pushes product listings, inventory, prices, and promotions, and what reads back account and product status. It sits underneath Google Shopping and the free product listings, which means it is the kind of integration a store never thinks about until it stops working. After 18 August 2026, calls to the old endpoints stop functioning, and for a merchant that shows up as the catalog quietly ceasing to sync — products going stale or disappearing from Shopping results.
The replacement is the Merchant API, and the shape of the change matters for planning. Google split the single Content API surface into several resource-specific sub-APIs — products, inventories, accounts, reporting, and others — so migrating is a matter of remapping each call to its new home and re-testing the whole feed-sync flow, not flipping a version number. Google does provide an extension-request process for teams that need more runway past the sunset.
Because the failure mode here is a catalog that stops appearing in front of shoppers, this is one to move early rather than late: port the integration, validate it against live Merchant Center data, and retire the old calls well before August. A feed outage is not a developer inconvenience — it is lost sales for every store on the integration.
Entry changelog
- — last reviewed.
- — Entry created from Google's official Content API for Shopping documentation, which states the 18 August 2026 sunset. Surfaced via Layer-2 discovery, written from the primary Google for Developers page.
- — Sunset date reached. Status moved to passed — 18 August 2026 is Google's stated end date for the Content API for Shopping (v2.1). Re-verified against the primary source today: the date still stands on the Google for Developers page. Integrations still calling the old Content API endpoints stop functioning; the required successor is the Merchant API.
Put this countdown in your README
Building on Google? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/google-content-api-shopping-eol)Spot an error or a changed date? Tell us and it’s corrected the same night.