Apply Merchant Center auto-setup
Creates or updates Product Metrics' supplemental sources in the property's Merchant Center account and links them to the matching primary sources, as merchant_center.inspect_auto_setup planned.
POST /properties/{propertyId}/merchant-center/auto-setup
Scope setup · Access Changes data · Operation id merchant_center.apply_auto_setup
Try it
productmetrics runs after productmetrics login; curl needs PM_TOKEN (see Authentication). Set $PROPERTY_ID first.
productmetrics merchant-center apply-auto-setup \
--property-id $PROPERTY_ID \
--jsonResponse
API response (200):
{
"data": {
"state": "applied",
"results": [
{
"merchantId": "987654321",
"feedLabel": "NL",
"contentLanguage": "nl",
"outcome": "created",
"reason": "needs_confirmation",
"dataSourceName": "accounts/987654321/dataSources/40",
"linkedPrimaries": 0,
"linkFailures": 0,
"fetchStarted": true
}
]
},
"request_id": "req_01JN5C0CNE2HTSA5PW9VJHP95B"
}CLI output: productmetrics merchant-center apply-auto-setup --json prints { "ok": true, "data": …, "request_id": "…" } with the same data.
Before you call
Sources from other tools are never touched. An empty existing source is reused only when its name is in confirmed_reuse; send only names the person confirmed. Needs company admin. Then check merchant_center.get_auto_setup_status.
Path parameters
| Name | Type | Description |
|---|---|---|
propertyId | string | The property id, from productmetrics whoami or properties.list (property_id). |
Body
| Name | Type | Required | Description |
|---|---|---|---|
confirmed_reuse | array of string | No | An empty existing source is reused only when its name is in confirmed_reuse; send only names the person confirmed. Up to 100 items. Default []. |
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 setup scope; connect again and allow it.",
"details": {
"required_scope": "setup"
}
},
"request_id": "req_01J5C24NJ2XGJJY3CX5HGZV0NZ"
}| 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 setup 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. |