Content API for Shopping

Name: Content API for Shopping API
Brand: Content API for Shopping
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontoauth2135 EndpointsREST

For Agents

Upload product feeds, monitor disapprovals, and manage Google Shopping accounts so an agent can keep a merchant's catalogue and ads configuration in sync.

Quickstart

Get started with Content API for Shopping in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"upload a product to google shopping"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Content API for Shopping API.

Upload and update product listings individually or in batched feeds

Track product status, disapprovals, and item-level issues across Google surfaces

Manage Merchant Center accounts, sub-accounts, and account-level tax and shipping settings

Maintain datafeeds and inspect their fetch status for scheduled imports

GET STARTED

Start building with Content API for Shopping API

Explore with Jentic

View OpenAPI Document

Use for: I need to upload a new product listing to Google Shopping, List all products with disapproval issues, Update inventory for a specific store code, Retrieve the status of our datafeed

Not supported: Does not handle on-site checkout, payment processing, or order fulfilment beyond Buy on Google order metadata — use for Merchant Center catalogue, feed, and promotion management only.

Google Content API for Shopping lets merchants programmatically manage the product listings, accounts, datafeeds, and shopping ads configuration that surface across Google Shopping, Free Listings, and Buy on Google. Retailers can upload product data in batches, monitor product status and disapprovals, manage local inventory and store codes, and configure shipping and tax settings. The API supports multi-account hierarchies for agencies and large retailers, and includes endpoints for orders, returns, and promotions on supported markets.

Use Cases

Patterns agents use Content API for Shopping API for, with concrete tasks.

★ Daily Catalogue Sync

An e-commerce platform pushes its full product catalogue to Google Merchant Center every night. The Content API for Shopping supports batched product uploads of up to 1,000 entries per call, returning per-item status so the integration can retry only the failures. Sync time for a 50,000-SKU catalogue is typically under 30 minutes.

Submit a custombatch with 500 product upserts targeting merchantId 1234567 and return the count of successful and failed entries.

Disapproval Triage

A retail ops dashboard polls product statuses and surfaces every disapproved item with its issue code, region, and resolution hint. The Content API for Shopping returns destination-level statuses so the dashboard can show which surface (Shopping ads, Free listings, Buy on Google) is affected. Merchants resolve the highest-impact disapprovals first.

List productstatuses for merchantId 1234567 filtered to itemLevelIssues and return the top 20 issues by affected product count.

Local Inventory Updates

An omnichannel retailer pushes near-real-time stock counts per store via the localinventory feed. The Content API for Shopping accepts store-level availability and price updates so storefront listings reflect what is on the shelf. Updates propagate to Local Inventory Ads in minutes.

Upload a localinventory entry for product 'sku-9921' at store code '0421' with availability=in stock and price=29.99 USD.

Promotion Launch

A merchandising team launches a free-shipping promotion across all eligible products via the promotions endpoint. The Content API for Shopping handles eligibility, schedule, and product applicability rules. Promotions appear on listings within a few hours of approval.

Create a promotion with promotionType FREE_SHIPPING_STANDARD, productApplicability ALL_PRODUCTS, valid from 2026-06-15 to 2026-06-22 in target country US.

AI Agent Catalogue Maintenance

A merchandising AI agent receives a request to fix all disapproved products containing 'restricted_term' in the title. The agent asks Jentic for the products.list and products.update operations, makes the corrections, and re-uploads, all without raw access to the merchant's OAuth tokens. Jentic handles credential rotation and per-call scoping.

Find every disapproved product whose title contains 'restricted_term', strip the term, and update each product, returning a summary of how many succeeded.

Key Endpoints

135 endpoints — google content api for shopping lets merchants programmatically manage the product listings, accounts, datafeeds, and shopping ads configuration that surface across google shopping, free listings, and buy on google.

METHOD

PATH

DESCRIPTION

GET

/{merchantId}/products

List products in a merchant account

POST

/products/batch

Submit batched product upserts and deletes

GET

/{merchantId}/productstatuses

List per-product statuses and issues

POST

/{merchantId}/localinventory/batch

Update local inventory in bulk

POST

/accounts/batch

Manage Merchant Center accounts in bulk

GET

/{merchantId}/products

List products in a merchant account

POST

/products/batch

Submit batched product upserts and deletes

GET

/{merchantId}/productstatuses

List per-product statuses and issues

POST

/{merchantId}/localinventory/batch

Update local inventory in bulk

POST

/accounts/batch

Manage Merchant Center accounts in bulk

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Merchant OAuth client secrets and refresh tokens are stored encrypted in the Jentic vault. Agents calling shoppingcontent.googleapis.com receive only short-lived access tokens scoped to the content OAuth scope.

Intent-based discovery

Agents search Jentic for intents like 'upload product to google shopping' and Jentic returns the products.insert and products.custombatch operations with their full request schemas, including price, availability, and identifiers.

Time to first call

Direct integration: 3-5 days to handle OAuth, multi-client account hierarchies, custombatch error retry, and feed scheduling. Through Jentic: under 2 hours by composing search, load, and execute on the products and productstatuses collections.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify Admin API

Storefront and catalogue management for retailers running on Shopify

Choose Shopify when the storefront itself is on Shopify; choose Content API when the goal is to surface listings on Google Shopping

Complementary

Google Search Console API

Provides organic search performance for the same product pages

Pair with Content API to compare paid Shopping performance against organic Search visibility

Alternative

eBay API

Listing management on a different marketplace

Choose eBay API when listing on the eBay marketplace; choose Content API for Google Shopping surfaces

FAQs

Specific to using Content API for Shopping API through Jentic.

What authentication does the Content API for Shopping use?

The Content API uses Google OAuth 2.0 with the content scope. Through Jentic the merchant OAuth client and refresh tokens are kept encrypted in the Jentic vault and the agent receives scoped access tokens per call.

Can I upload thousands of products in a single call with the Content API?

Yes, in batches. Use products.custombatch to submit up to 1,000 entries per request, each scoped to a merchantId and product ID. The response returns a per-entry status so you can retry only the entries that failed.

What are the rate limits for the Content API for Shopping?

Google Merchant Center applies per-account daily and per-minute quotas: roughly 200,000 product mutations per day for standard accounts, with stricter limits during initial onboarding. Check the Merchant Center quotas page for your account's exact ceilings.

How do I list disapproved products through Jentic?

Run pip install jentic, search Jentic for 'list disapproved google shopping products', load the schema for productstatuses.list on shoppingcontent.googleapis.com, and execute it with your merchantId and a filter on itemLevelIssues.

Does the Content API for Shopping handle storefront checkout or payment?

No. It manages catalogue, account, inventory, and promotions metadata that drive Shopping listings. Checkout flow on Buy on Google or your own site is handled separately by Google Pay, Stripe, or another payment processor.