> ## Documentation Index
> Fetch the complete documentation index at: https://996f455-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://996f455-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://996f455-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://996f455-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Inspect Merchant Center auto-setup (/docs/api/merchant-center/inspect-auto-setup)

<!-- agent-signals: reading_time_min: 2 · est_tokens: 1224 · updated: 2026-11-16 -->
Related: [Apply Merchant Center auto-setup](/docs/api/merchant-center/apply-auto-setup.md), [Connect Merchant Center](/docs/api/merchant-center/create-connection.md), [Disconnect Merchant Center](/docs/api/merchant-center/delete-connection.md), [Get Merchant Center auto-setup status](/docs/api/merchant-center/get-auto-setup-status.md), [Recheck a Merchant Center connection](/docs/api/merchant-center/recheck-connection.md)

> Plans the Merchant Center supplemental feed setup for a property without changing anything: per feed label and language, whether Product Metrics' supplemental source exists, would be created or updated, needs the person to confirm reusing an empty source, or is blocked (with the reason).

`GET https://prod-backend.productmetrics.io/api/public/v1/properties/{propertyId}/merchant-center/auto-setup`

**Scope** `read` · **Access** Read only · **Operation id** `merchant_center.inspect_auto_setup`

## Try it

`productmetrics` runs after `productmetrics login`; curl needs `PM_TOKEN` (see [Authentication](/docs/api/overview#authentication)). Set `$PROPERTY_ID` first.



**productmetrics CLI:**

```bash
productmetrics merchant-center inspect-auto-setup \
  --property-id $PROPERTY_ID \
  --json
```

**curl:**

```bash
curl "https://prod-backend.productmetrics.io/api/public/v1/properties/$PROPERTY_ID/merchant-center/auto-setup" \
  -H "Authorization: Bearer $PM_TOKEN"
```

## Response



API response (200):

```json
{
  "data": {
    "state": "ready",
    "googleEmail": "owner@example.com",
    "accounts": [
      {
        "merchantId": "987654321",
        "access": "ok",
        "pairs": [
          {
            "feedLabel": "NL",
            "contentLanguage": "nl",
            "primaries": [
              {
                "name": "accounts/987654321/dataSources/12",
                "displayName": "Online products NL",
                "fetchUri": "https://example-store.com/feeds/google-nl.xml"
              }
            ],
            "feedId": "6f1c2a7e-3b4d-4e8f-9a01-2c3d4e5f6a7b",
            "feedUrl": "https://feeds.example.com/supplemental/nl.xml",
            "blockedReason": "language_split_off",
            "classification": "ours",
            "existing": {
              "name": "accounts/987654321/dataSources/40",
              "displayName": "Product Metrics segments NL",
              "fetchUri": "https://feeds.example.com/supplemental/nl.xml"
            },
            "action": "keep",
            "linked": true,
            "upload": {
              "processingState": "PROCESSING_STATE_UNSPECIFIED",
              "itemsTotal": 42,
              "itemsCreated": 0,
              "itemsUpdated": 0,
              "errorCount": 42,
              "warningCount": 42,
              "uploadTime": "2026-11-02T09:30:00.000Z"
            }
          }
        ]
      }
    ]
  },
  "request_id": "req_01JSKECHVBKB26HCY0NBF8875Z"
}
```

**CLI output:** `productmetrics merchant-center inspect-auto-setup --json` prints `{ "ok": true, "data": …, "request_id": "…" }` with the same `data`.

## Before you call

Call it before [`merchant_center.apply_auto_setup`](/docs/api/merchant-center/apply-auto-setup) and show the person any `confirm_reuse` source names.

## Path parameters

| Name         | Type   | Description                                                                                                         |
| ------------ | ------ | ------------------------------------------------------------------------------------------------------------------- |
| `propertyId` | string | The property id, from `productmetrics whoami` or [`properties.list`](/docs/api/account/properties-list) (`property_id`). |

## Errors

A failure answers with its HTTP status and `{ error: { code, message, details? }, request_id }`. Branch on `code` (stable, lower_snake); show `message` to the person. The CLI prints the same `error` with `"ok": false`.

```json
{
  "error": {
    "code": "insufficient_scope",
    "message": "This operation needs the read scope; connect again and allow it.",
    "details": {
      "required_scope": "read"
    }
  },
  "request_id": "req_01JX26GW2W33AY3S75HT0HNJ5J"
}
```

| Status | Code                 | When                                                                                                                      |
| ------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| 400    | `invalid_request`    | A path, query or body value does not match this page. `details.issues` lists each `location`, `path` and `message`.       |
| 401    | `invalid_token`      | The token is missing, expired or revoked: sign in again (`productmetrics login`). The `WWW-Authenticate` header says why. |
| 403    | `insufficient_scope` | The token lacks the `read` scope (`details.required_scope`): sign in again and allow it.                                  |
| 404    | `not_found`          | An id in the path does not exist, or the signed-in person cannot open it.                                                 |
| 429    | `rate_limited`       | More than 600 requests a minute for this person: wait the `Retry-After` seconds (60) and retry.                           |

[All Merchant Center operations](/docs/api/merchant-center)
