Migrate a Shopping product feed integration from the Content API for Shopping to the new Google Merchant API before the shutdown deadline

domain: developers.google.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Confirm the timeline: Content API for Shopping access ends August 18, 2026, and the Merchant API's own v1beta version sunsets February 28, 2026
  2. Enable the Merchant API in Google Cloud Console and generate credentials scoped to the new merchantapi.googleapis.com services
  3. Re-map existing Content API resources (products, productstatuses) to the split Merchant API sub-APIs (e.g. Products, Reports, Accounts), since functionality is no longer one monolithic API
  4. Update product submission calls to the new endpoint paths and schemas, since field names and structure changed beyond just the host
  5. Test against a limited account before cutting production feeds over, then monitor the Reports sub-API for post-migration issues

Known gotchas

Related routes

Migrate a product feed from Google Content API for Shopping to the Merchant API v1 before the August 2026 shutdown
developers.google.com · 6 steps · unrated
Sync a product feed to Google via the Merchant API (successor to Content API for Shopping)
merchants.google.com · 6 steps · unrated
Submit and update a product data feed to Google Merchant Center via the Content API for Shopping
google.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans