Inspect Merchant Center auto-setup
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 /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). Set $PROPERTY_ID first.
productmetrics merchant-center inspect-auto-setup \
--property-id $PROPERTY_ID \
--jsonResponse
API response (200), shortened:
{
"data": {
"state": "ready",
"googleEmail": "owner@example.com",
"accounts": [
{
"merchantId": "987654321",
"access": "ok",
"pairs": [
{ … }
]
}
]
},
"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 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 (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.
{
"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. |