The Google Content API for Shopping reaches end-of-life today — catalogs must sync through the Merchant API now

A quiet monitored night — 56 sources fetched clean, nothing new in the feeds and no fresh discovery chatter — but a date on the board comes due. Today, 18 August 2026, is Google's stated end-of-life for the Content API for Shopping (v2.1), the programmatic pipe that pushes product listings, inventory, prices, and promotions into Google Merchant Center. Integrations still calling the old endpoints stop working; the required successor is the Merchant API. We re-verified the date against Google's own page today before moving the entry to passed, and re-checked every other sub-30-day entry against its primary source.

A quiet monitored night: 56 sources fetched clean, no new items in the feeds, and no fresh discovery chatter. But the board doesn’t stop for a quiet night, and today a significant date comes due.

The Google Content API for Shopping reaches end-of-life today, 18 August 2026. This is the long-standing programmatic interface to Google Merchant Center — the pipe that pushes product listings, inventory, prices, and promotions, and reads back account and product status. It sits underneath Google Shopping and the free product listings, which makes it the kind of integration a store never thinks about until it stops syncing. We re-verified the date against Google’s own developer documentation today: it still states the 18 August 2026 sunset, so the entry moves to passed. After today, calls to the old Content API (v2.1) endpoints stop functioning, and for a merchant that shows up as the catalog quietly going stale or disappearing from Shopping results.

The replacement is the Merchant API, and the shape of the change matters if you’re only starting now: Google split the single Content API surface into several resource-specific sub-APIs — products, inventories, accounts, reporting, and others — so the port is an endpoint-by-endpoint remapping plus a full re-test of the feed-sync flow, not a version bump. Google does run an extension-request process for teams that need more runway past today’s date, so if you’re caught out, that’s the first place to look rather than assuming an immediate hard cutoff for everyone.

Every entry with a sunset date inside 30 days was re-checked against its primary source first — twelve entries, all confirmed unchanged. (The Microsoft Sentinel SAP connector’s 14 September date was again re-confirmed against Microsoft’s release-communications API, since its Azure Updates page renders the date in JavaScript and our fetcher can’t see it.)

Still counting down

OpenAI Assistants API — 26 August, removed from the API in favor of the Responses API.
Convictional — 27 August, platform access ends.
OCI DevOps OL7 build runners — 28 August.
GitHub Spark, Flowise, the New Relic drop-filter-rules API, and the Power Automate mobile app — all 31 August.

Further out: OpenSSL 3.0 (7 September), the GitHub Copilot MAI-Code-1-Flash deprecation (10 September), the Relay paid shutdown and the Microsoft Sentinel SAP agent retirement (both 14 September), the OpenAI Sora 2 video API (24 September), the Azure Automation runtime cut-off (30 September), the new EWS in Exchange Online block (1 October), the Cloudflare Workers KV legacy API (15 October), the Azure Databricks Runtime 10.4 LTS end of life (1 November), and the Azure Blueprints retirement (31 January 2027). The full board, with countdowns, is on the calendar.

Want this in your own repo instead of your inbox? The lastcall CLI — npx lastcall.dev check — scans a project and tells you which of your dependencies has an announced end date, reading the same public dataset this site is built on.