Connect Merchant Center
Connects a Merchant Center account to a property that already has a Google Ads connection.
POST /properties/{propertyId}/merchant-center/connection
Scope setup · Access Changes data · Operation id merchant_center.create_connection
Try it
productmetrics runs after productmetrics login; curl needs PM_TOKEN (see Authentication). Set $PROPERTY_ID first.
productmetrics merchant-center create-connection \
--property-id $PROPERTY_ID \
--merchant-id 987654321 \
--jsonResponse
API response (200):
{
"data": {
"propertyId": "8c1f4d2e-7a3b-4c5d-9e6f-0a1b2c3d4e5f",
"merchantId": "987654321",
"accountName": "Example Store",
"status": "active",
"verifiedAt": "2026-11-02T09:30:00.000Z"
},
"request_id": "req_01JWVTRPYHJ23WK3Y41V2RN7EY"
}CLI output: productmetrics merchant-center create-connection --json prints { "ok": true, "data": …, "request_id": "…" } with the same data.
Before you call
merchant_id must be linked to that Google Ads account in Google (a Merchant Center product link); otherwise the call answers 409 no_merchant_center_links. Needs company admin. Next: set up the supplemental feed with merchant_center.inspect_auto_setup.
Path parameters
| Name | Type | Description |
|---|---|---|
propertyId | string (uuid) | The property id, from productmetrics whoami or properties.list (property_id). |
Body
| Name | Type | Required | Description |
|---|---|---|---|
merchant_id | string | Yes | The Merchant Center account 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 setup scope; connect again and allow it.",
"details": {
"required_scope": "setup"
}
},
"request_id": "req_01J4EKCVAG07QP1TKYSC1HF8J1"
}| 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. |
| 409 | no_merchant_center_links | merchant_id must be linked to that Google Ads account in Google (a Merchant Center product link); otherwise the call answers 409 no_merchant_center_links. |
| 429 | rate_limited | More than 600 requests a minute for this person: wait the Retry-After seconds (60) and retry. |