Google Manufacturer Center API

Name: Manufacturer Center API
Brand: Manufacturer Center API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontoauth28 EndpointsREST

Install Jentic One Beta

Connect the Manufacturer Center API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Manufacturer Center API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Manufacturer Center API.

Publish authoritative manufacturer-supplied product attributes such as GTIN, MPN, brand, and feature descriptions

Delete a product from the manufacturer account when it is discontinued

List the products currently registered under a manufacturer account

GET STARTED

Start building with Manufacturer Center API

Explore with Jentic

View OpenAPI Document

For Agents

Submit and manage authoritative manufacturer-supplied product attributes and product certifications for a brand's catalog in Google Manufacturer Center.

Use for: List all products registered under our Manufacturer Center account, Delete a discontinued product from our manufacturer account, Retrieve all certifications currently attached to a manufacturer product, Remove an expired product certification from a product

Not supported: Does not handle retailer offers, ads, or pricing - use for manufacturer-supplied product data and product certifications only.

The Manufacturer Center API lets brand manufacturers submit and maintain authoritative product data and product certifications used across Google's shopping surfaces. Brands push canonical attributes such as GTIN, MPN, brand name, image, product detail, and feature descriptions, plus regulatory or industry certifications, so retailers and Google's shopping experiences show accurate manufacturer-supplied content. The API is scoped per Manufacturer Center account and is distinct from Merchant Center, which is used by retailers to upload their own offers.

Use Cases

Patterns agents use Manufacturer Center API for, with concrete tasks.

★ Authoritative product data publication

Brand manufacturers use the API to publish canonical product information such as GTIN, MPN, feature bullets, and product detail attributes so that Google's shopping surfaces and downstream retailers display the manufacturer-approved content. This avoids retailer-by-retailer attribute drift and keeps the brand's voice consistent.

List all products under accounts/12345 and report any whose required brand or gtin attributes are missing

Product certification management

Manage product certifications attached to products in the manufacturer account, including regulatory marks, energy efficiency labels, and industry credentials. The certifications resource lets brands keep documentation current as products are recertified or removed from market.

List productCertifications for product accounts/12345/products/SKU-AB-100 and delete any whose validity period has ended

Catalog hygiene and end-of-life

Run periodic catalog hygiene against Manufacturer Center to delete products that are end-of-life and confirm replacements are in place. Combined with the listing endpoints, this keeps the brand's authoritative catalog current and avoids ghost SKUs surfacing on shopping pages.

For every product in accounts/12345 with a discontinued flag in our internal system, call delete on the matching manufacturer product

Agent integration via Jentic

AI agents responsible for marketplace data quality can use Manufacturer Center through Jentic to audit catalog completeness and remove dead SKUs without holding the brand's OAuth refresh token in their prompt. Jentic also surfaces the certification operations so agents can keep regulatory metadata up to date.

Walk every product in accounts/12345, delete any flagged discontinued in our PIM, and report the deleted SKU list

Key Endpoints

8 endpoints — the manufacturer center api lets brand manufacturers submit and maintain authoritative product data and product certifications used across google's shopping surfaces.

METHOD

PATH

DESCRIPTION

GET

/v1/{+parent}/products

List products in a manufacturer account

DELETE

/v1/{+parent}/products/{+name}

Delete a product from a manufacturer account

GET

/v1/{+parent}/productCertifications

List product certifications

DELETE

/v1/{+name}

Delete a specific resource by name

GET

/v1/{+parent}/products

List products in a manufacturer account

DELETE

/v1/{+parent}/products/{+name}

Delete a product from a manufacturer account

GET

/v1/{+parent}/productCertifications

List product certifications

DELETE

/v1/{+name}

Delete a specific resource by name

Why Jentic?

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

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Manufacturer Center products' or 'remove a product certification', and Jentic returns the matching Manufacturer Center operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Manufacturer Center API through Jentic.

What authentication does the Manufacturer Center API use?

The API uses Google OAuth 2.0 with the https://www.googleapis.com/auth/manufacturercenter scope. Through Jentic, the OAuth credentials are held in the encrypted vault and the agent only sees a short-lived scoped bearer token for each call.

Can I list every product under our manufacturer account through this API?

Yes, the products listing endpoint under accounts/{account_id} returns paginated product entries. Use the page token in the response to walk the full catalog.

What are the rate limits for the Manufacturer Center API?

Quotas are managed per Google Cloud project and per Manufacturer Center account in the Cloud Console quotas page. Default per-day and per-minute request quotas apply, and bulk catalog updates should use exponential backoff on 429 responses.

How do I delete an expired product certification through Jentic?

Search Jentic for delete product certification, load the operation that maps to /v1/{+name}, and execute with the certification resource path. Jentic injects the OAuth bearer so the agent only constructs the request body.

Is the Manufacturer Center API free?

Manufacturer Center itself is free for eligible brand manufacturers and the API does not have separate per-call billing; usage is bounded by quota rather than price.

Is this the same API as Merchant Center?

No. Manufacturer Center is for brand manufacturers publishing authoritative data about their own products. Merchant Center is for retailers uploading the offers they sell, which uses the separate Content API for Shopping or the Merchant API.

Can I limit what my agent is allowed to do with the Manufacturer Center API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Manufacturer Center operations and credentials the agent can use. Since the account and product are named in the URL path (/v1/{+parent}/products and /v1/{+name}), a rule can pin the agent to a single Manufacturer Center account so it only lists products and certifications there and nothing else. You pick the operations it may call, so destructive ones like deleting a product or a certification stay off the list unless you explicitly add them.

Google Manufacturer Center API

Connect the Manufacturer Center API to your agent

Capabilities

Start building with Manufacturer Center API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs