Use the Merchant API (v1), which is now generally available and the official successor to the Content API for Shopping; the Content API for Shopping is scheduled for shutdown on August 18, 2026.
Authenticate with OAuth 2.0 using a service account or user OAuth flow with the `https://www.googleapis.com/auth/content` scope.
Insert or update products by calling `POST https://merchantapi.googleapis.com/products/v1beta/accounts/{merchantId}/products` (or the v1 equivalent); provide structured product data including GTIN, brand, condition, availability, price, and required attributes for the target country.
For bulk operations, use the Products API batch endpoint or the DataSources API to register a supplemental feed and trigger a fetch from a hosted URL.
Poll the product status via `GET /products/{productId}` and inspect the `productStatuses` to check for disapprovals, warnings, and whether the product is active in Google Shopping.
Monitor feed health in the Merchant Center UI or via the `productstatuses.list` endpoint; address disapproval reasons (missing GTIN, image policy violations, price mismatches) before re-submitting.
Known gotchas
The v1beta sub-API in Merchant API was discontinued on February 28, 2026; all calls must target v1 (or v1alpha for features not yet in v1) — check current endpoint versions in the official documentation.
The Merchant API and Content API for Shopping coexist until August 2026 but are separate API surfaces with different endpoint paths; mixing them in the same integration causes authentication or routing errors.
Product disapprovals due to price mismatch (API price differs from landing page price) are a common silent failure; implement landing page price monitoring to keep the feed in sync.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp