listingsAPIlistingsAPI
Get API keySign in
POST/api/v4/connected-accounts/confirm-matches

Confirm connection matches

Confirms suggested location-to-listing matches returned by the connection suggestions endpoint.

Requires an API key. See Authentication for header format and key rotation.

Parameters

Body

NameTypeRequiredDescription
connectedAccountIdstringrequiredUUID of the connected account whose suggested matches you are confirming.
matchIdsarray of stringsoptionalIDs of the suggested matches to confirm, taken from the records returned by the connection suggestions endpoint. Omit to confirm all outstanding suggestions for the account.

Sample request

Ready-to-paste body. Replace placeholder IDs and values with yours.

{
  "connectedAccountId": "4f712c17-4f95-42dd-90f4-97171a2e67b5",
  "matchIds": [
    "0d5e306f-0da0-46e3-929f-fd3c67ccd8cc"
  ]
}

Responses

200Matches confirmed.
{
  "data": {
    "confirmConnectMatches": {
      "success": true
    }
  }
}
400Bad request — missing connectedAccountId or unknown match IDs.
401Unauthenticated — missing or invalid API key.

Accepts suggested location-to-listing pairings and confirms them, establishing the live connection between listingsAPI locations and their corresponding Google Business Profile or Facebook listings. Once confirmed, the listing begins syncing with the matched listingsAPI location.

The matchIds you pass come from the records returned by GET /connected-accounts/{connectedAccountId}/connection-suggestions. This endpoint is the final step of the bulk-connect workflow: connect the account, run POST /connected-accounts/trigger-matches to generate suggestions, review them, then confirm here.

Use case — bulk-accepting reviewed matches. After an agency imports a client's Google account and reviews the suggested pairings in your own UI, submit the approved match IDs in one call instead of confirming each in the listingsAPI dashboard. Send only the IDs the operator approved so unreviewed or wrong suggestions are left untouched.

Confirming a match does not immediately push data to Google or Facebook; it links the listingsAPI location to the publisher listing so subsequent listing updates flow through. success: true indicates the confirmation was accepted. For manually picking a single listing without going through suggestions, use the connect-listing endpoint instead.

curl -X POST 'https://listingsapi.com/api/v4/connected-accounts/confirm-matches' \
  -H "Authorization: API $LISTINGSAPI_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "connectedAccountId": "<connectedAccountId>",
    "matchIds": "<matchIds>"
  }'
Run in playground