Content API Sunsets August 2026: What To Do Now

Google's Content API for Shopping is the programmatic interface that has powered third-party feed management since 2014. As of August 18, 2026 it stops working. Calls to shoppingcontent.googleapis.com/content/v2.1/* return HTTP 410 Gone after that date, and the replacement is the new Merchant API v1 which we cover in depth in the complete migration guide.

This article is the executive summary: who needs to act, what happens if you do not, and the 5-step plan to migrate in time without breaking production.

What is sunsetting and when

Who is affected (and who is not)

Affected:

• Custom integrations that call the Content API directly
• Older third-party feed tools that have not migrated yet (check with your vendor)
• Internal scripts that pull reports, sync inventory, or manage products via the API
• BigQuery export pipelines using the legacy Content API → BigQuery connector

Not affected (probably):

• Shopify stores using the Google & YouTube sales channel (Shopify handles the migration)
• WooCommerce stores using the Google Listings & Ads plugin (Google handles it)
• Stores using major feed-management platforms (DataFeedWatch, Channable, Feedonomics) — but confirm the vendor has migrated

If you are unsure whether you are affected, run an audit on your traffic logs: search for outbound calls to shoppingcontent.googleapis.com. Any hits mean you have code that needs migration.

Consequences of doing nothing

At 00:01 UTC on August 18, 2026, every call to the Content API starts failing. The cascade for an unmigrated store:

1. Product sync stops. New products do not appear in Shopping. Edited products do not update.
2. Inventory sync stops. Out-of-stock items keep showing as in-stock. Sales continue on products that have no stock.
3. Reports break. Performance dashboards return errors. Decisions get made on stale data.
4. Eventually, Google disables the Shopping campaigns because the feed is more than 7 days stale. Revenue goes to zero.

Recovery requires the same migration work as doing it on time, but with revenue actively bleeding while you scramble.

The 5-step migration plan

Step 1: Inventory your Content API usage

Grep your codebase for shoppingcontent.googleapis.com, "ShoppingContent", or your client library import (e.g., googleapis/shopping). Document every endpoint called. Note: third-party tools that pass through your auth token also use the API, so check vendor docs too.

Step 2: Install Merchant API client library

Install alongside the existing Content API client. The two can coexist. For Node: npm install @google-cloud/merchant-products. For Python: pip install google-shopping-merchant-products-v1beta. Other languages: see the client library page [4].

Step 3: Mirror reads, then mirror writes

For 1-2 weeks, run both APIs in parallel. Compare responses for parity. Fix discrepancies. Once reads match, start mirror-writing: every Content API call also writes to the new API. Validate that the new API reflects the changes correctly.

Step 4: Cutover

Switch all production reads to the new API. Keep mirror writes on for 1 more week as a rollback insurance. Monitor error rates closely.

Step 5: Decommission Content API

Disable Content API writes. Remove the old client library. Update documentation. Migration complete.

Common migration pitfalls

• Custombatch is gone. The bulk endpoint that handled mixed operations does not exist in the new API. Refactor to per-resource batch calls.
• Status enums changed case. "approved" → "APPROVED". Any string-compare logic breaks silently.
• Reports query language is new. Old reports queries are syntactically invalid in the new API.
• Pagination tokens are not transferable. Reset persisted page tokens at cutover.
• OAuth scopes need updating. Re-request user consent with new scopes before cutover.

Bottom line

Content API sunset is real, fixed, and 3 months away. Stores using managed platforms are fine. Custom integrations need to migrate. The full migration playbook is in our Merchant API migration guide; this article is the executive summary to decide whether you need to act.