[Special Report] Google Merchant API Architecture Guide: Replacing Content API for Shopping, August 18, 2026 Sunset Timeline & Modular v1 Upgrade

Executive Summary & Research Scope

Comprehensive engineering breakdown of Google’s next-generation Merchant API replacing Content API for Shopping v2.1: official August 18, 2026 sunset and September 1, 2026 HTTP 410 Gone (content_api_sunset) progressive outages, independently versioned sub-APIs, AIP-122 resource names with ~ delimiters and unpadded RFC 4648 base64url encoding, Price amountMicros, gRPC + REST support, Merchant API MCP Server, and UCP agentic performance reports.

1. Sunset Countdown (Aug 18, 2026) & Official 4-Part Migration Series Navigation

Merchant API is Google's next-generation Merchant Center account and product management system, engineered to fully replace Content API for Shopping (v2.1).

Note for Shopify Merchants: If you sync catalog data strictly through the official Shopify Google & YouTube app (or managed 3P connectors like Feedonomics), the provider handles the backend migration automatically. Custom scripts calling shoppingcontent.googleapis.com must be refactored by your engineering team.

Figure 1: [Special Report] Google Merchant API Architecture Guide: Replacing Content API for Shopping, August 18, 2026 Sunset Timeline & Modular v1 Upgrade — Primary Source Visual Evidence & Architectural Diagram (1)

2. Modular Sub-APIs, ~ Composite Keys & Unpadded RFC 4648 base64url Encoding

Instead of coupling every capability under a monolithic v2.1 namespace, Merchant API decouples capabilities into independently versioned sub-APIs (accounts, datasources, products, inventories, reports, promotions, notifications, quota, lfp, issueresolution, ordertracking, and reviews) under https://merchantapi.googleapis.com/{SUB_API}/{VERSION}/{RESOURCE_NAME}:{METHOD}.

Use the interactive translator below to compare v2.1 vs. v1 endpoints, amountMicros payloads, and automatic base64url resource encoding:

POST https://shoppingcontent.googleapis.com/content/v2.1/4321009/products
Content-Type: application/json

{
  "offerId": "SKU-2026-PRO",
  "contentLanguage": "en",
  "targetCountry": "US",
  "channel": "online",
  "title": "Flagship Wireless Earbuds",
  "price": {
    "value": "33.45",
    "currency": "USD"
  }
}

POST https://merchantapi.googleapis.com/products/v1/accounts/4321009/productInputs:insert?dataSource=accounts/4321009/dataSources/987654
Content-Type: application/json

{
  "offerId": "SKU-2026-PRO",
  "contentLanguage": "en",
  "feedLabel": "US",
  "productAttributes": {
    "title": "Flagship Wireless Earbuds",
    "price": {
      "amountMicros": "33450000",
      "currencyCode": "USD"
    }
  }
}

• Removal of channel & ~ Delimiters: Legacy 4-part IDs (online:en:US:SKU-9001) become 3-part keys (en~US~SKU-9001, formatted as {contentLanguage}~{feedLabel}~{offerId}).
• Mandatory Unpadded base64url Encoding: Whenever contentLanguage~feedLabel~offerId contains reserved characters (% . + / : , ( * ! ) & ? = @ # $ or multiple ~ characters), you must encode the entire contentLanguage~feedLabel~offerId string using RFC 4648 Section 5 base64url without = padding.
• Micros Pricing & 4x Larger Pagination: Price switches from decimal strings to amountMicros (1 USD = 1,000,000 micros) + currencyCode; pageSize expands from 250 to 1,000; and clickPotentialRank is normalized to 1–1000.

3. Agentic Commerce Exclusives: Official MCP Server & UCP Performance View

Google builds all next-generation AI shopping capabilities exclusively on Merchant API:

• Merchant API MCP Server (https://merchantapi.googleapis.com/mcp, Alpha): Connect AI coding and ops agents (Gemini CLI, Claude Code) directly to GMC via Model Context Protocol to diagnose disapprovals (pair with our Google Ads Product Diagnostics Playbook and AI SEO/GEO Audit Playbook).
• UCP Agentic Performance Reports (ucp_agentic_performance_view): Query impressions and clicks generated across conversational AI shopping surfaces and Universal Commerce Protocol integrations (see Google UCP & Shopify Agentic Checkout and Ads in AI Overviews & AI Mode).

Actionable Implementation Checklist & Strategic Takeaways

1. Action Item #1: Audit every internal service calling shoppingcontent.googleapis.com and complete full Merchant API cutover well ahead of the August 18, 2026 sunset and September 1, 2026 HTTP 410 Gone rollout.
2. Action Item #2: Update composite product key builders to {contentLanguage}{feedLabel}{offerId} and apply unpadded RFC 4648 base64url encoding across the full key whenever special characters appear.
3. Action Item #3: Convert price fields to integer amountMicros, adopt push notifications via notifications/v1, and monitor AI shopping visibility with ucp_agentic_performance_view.

Cross-Channel Growth & AI Citation Matrix