Google Merchant Center Integration

Overview

The Merchant Center integration uses the Merchant API v1 (the newer replacement for the deprecated Content API for Shopping v2.1).

Skills that use this integration:

• int-merchant-center: Product feed management, status issue scanning, shipping/tax, orders

Agents that typically enable this integration:

• Google Ads Manager: for Shopping and PMax campaigns that depend on the product feed

Availability

Prerequisites

• A Wiro API key (see Authentication).
• A deployed agent (see Agent Overview).
• A Merchant Center account the connecting user administers.
• A Google Cloud project with Merchant API enabled.
• Developer Registration: a one-time step to link your GCP project to your primary MC account.
• An HTTPS callback URL.

Own Mode

Step 1: Create GCP project + enable Merchant API

1. console.cloud.google.com → create a project.
2. APIs & Services → Library → enable Merchant API.
3. OAuth consent screen:
   • External user type for multi-tenant use
   • App name, support email
   • Add scope: https://www.googleapis.com/auth/content
   • Publish the app (In production). While it is in Testing, Google expires its refresh tokens after 7 days and the agent loses access.

Step 2: Create OAuth Client

APIs & Services → Credentials → Create Credentials → OAuth client ID:

• Application type: Web application
• Authorized redirect URIs: https://api.wiro.ai/v1/UserAgentOAuth/MCCallback

Copy the client ID and the client secret.

Step 3: Register Developer Registration (REQUIRED, one-time)

Merchant API requires that your GCP project be registered against your primary Merchant Center account before it will answer for any merchant account you authorize:

curl -X POST \
  "https://merchantapi.googleapis.com/accounts/v1/accounts/{YOUR_PRIMARY_MC_ID}/developerRegistration:registerGcp" \
  -H "Authorization: Bearer {ACCESS_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{}'

Where:

• YOUR_PRIMARY_MC_ID: your own Merchant Center ID (you, the developer)
• ACCESS_TOKEN: a fresh access token for your primary MC account

Once registered, your GCP project can call Merchant API on any merchant account that a user authorizes through OAuth.

Step 4: Connect

Save the OAuth client with POST /UserAgent/CredentialUpsert:

curl -X POST "https://api.wiro.ai/v1/UserAgent/CredentialUpsert" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "fields": [
      { "credentialkey": "google-merchant-center", "fieldname": "clientid", "fieldvalue": "123-abc.apps.googleusercontent.com" },
      { "credentialkey": "google-merchant-center", "fieldname": "clientsecret", "fieldvalue": "YOUR_CLIENT_SECRET" },
      { "credentialkey": "google-merchant-center", "fieldname": "authmethod", "fieldvalue": "own" }
    ]
  }'

Then start OAuthConnect in own mode:

curl -X POST "https://api.wiro.ai/v1/UserAgentOAuth/OAuthConnect" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "credentialkey": "google-merchant-center",
    "redirecturl": "https://your-app.com/settings/integrations",
    "authmethod": "own"
  }'

The response returns { result: true, authorizeUrl: "..." }. Redirect the user to authorizeUrl.

Step 5: Save the account selection

After consent the user returns with ?mc_connected=true&mc_accounts=<URL-encoded-JSON>. Each entry is { id, name, websiteUrl }: id is the numeric Merchant Center ID, name is the account name and can be empty, and websiteUrl is always empty. When name is empty, label the account with its ID. Send the user's choice to SetPickerAccounts as { merchantid, accountname } (id becomes merchantid, name becomes accountname):

curl -X POST "https://api.wiro.ai/v1/UserAgentOAuth/SetPickerAccounts" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "credentialkey": "google-merchant-center",
    "accounts": [
      { "merchantid": "1234567890", "accountname": "Acme Store" }
    ]
  }'

This call is required, even when mc_accounts has one entry. Until it runs, OAuthStatus reports connected: false.

Pass multiple { merchantid, accountname } entries to authorize the agent against several merchant accounts at once.

Disconnect

curl -X POST "https://api.wiro.ai/v1/UserAgentOAuth/OAuthDisconnect" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "credentialkey": "google-merchant-center"
  }'

Clears the tokens and the selected accounts in Wiro. Your Client ID and Client Secret are kept. Wiro does not ask Google to revoke the authorization.

Status

curl -X POST "https://api.wiro.ai/v1/UserAgentOAuth/OAuthStatus" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "credentialkey": "google-merchant-center"
  }'

Response:

{
  "result": true,
  "connected": true,
  "accounts": [
    { "id": "1234567890", "name": "Acme Store" }
  ],
  "connectedat": "2026-04-17T12:00:00.000Z",
  "tokenexpiresat": "2026-04-17T13:00:00.000Z",
  "errors": []
}

accounts[] carries one entry per selected merchant (id = merchantid, name = accountname).

Skill reference

• agent-skills.md: custom skill schema and the int-merchant-center key

Troubleshooting

redirect_uri_mismatch on Google's page

The Authorized redirect URIs of your OAuth client don't include https://api.wiro.ai/v1/UserAgentOAuth/MCCallback exactly as written. Google stops on its own error page, so nothing comes back to your redirecturl. Add the URI (Step 2) and connect again.