Content API for Shopping sunsets today: migrate now

Today is the date. The Content API for Shopping — the interface that has pushed product data into Google Merchant Center for a decade — reaches its published sunset on August 18, 2026. If a cron job on one of your boxes still POSTs to shoppingcontent/v2.1, today is the day you find out whether anyone remembered.

What actually happened

Google's migration documentation says it flatly: "Content API for Shopping will be sunset on August 18, 2026." The successor, Merchant API v1, went generally available in August 2025. That was a twelve-month overlap, announced well ahead of time, with migration guides for every sub-API.

The shape of the change, per Google's migration guide:

• New endpoint structure: https://merchantapi.googleapis.com/{SUB_API}/{VERSION}/{RESOURCE_NAME}:{METHOD}, with gRPC alongside REST
• name replaces id as the unique resource identifier
• Child resources hang off a parent field instead of being addressed directly
• Price becomes amountMicros (int64) and currencyCode (string)

That last one is the quiet landmine. Price-as-micros is not a rename, it's a type change. Any code handing Google a float dollar amount needs a conversion, and rounding errors in a price feed do not surface as stack traces. They surface as disapproved products and a Shopping tab that quietly stops showing your catalog.

Google also publishes an extended access form for merchants who need more runway. It is an application, not a toggle.

Why the Content API sunset matters for your business

Most stores we audit do not know what talks to Merchant Center. There is the official Shopify or WooCommerce channel app, and then there is the thing somebody built in 2021 to fix a variant mapping problem, running on a VM nobody has SSH'd into since. The app vendor migrated. The 2021 script did not.

So the practical work today is inventory, not code. Pull the last thirty days of Merchant Center API request logs from your Google Cloud project and look at which client IDs and user agents are still hitting shoppingcontent. Every one of them is either a vendor who owes you a status update or a script you own. There is no third category.

Then check what breaks if the feed goes stale rather than errors. A push job that fails loudly gets noticed. A push job that fails silently leaves last week's prices and inventory sitting in Merchant Center, serving Shopping ads for items you no longer stock at prices you no longer charge. That is the expensive failure mode, and it is the one with no alert attached.

The broader pattern: your catalog's connection to Google's ad surfaces is a dependency with a version number and an end-of-life date. Treat it like one. It belongs in the same list as your TLS certs and your payment gateway API version — things that expire on someone else's calendar and take revenue with them.

Sources: Google: Migrate from Content API for Shopping to Merchant API, Google: Start your migration, Google Merchant Center Help: Introducing Merchant API.