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

Trigger location matches

Fetches the Google and Facebook profiles for connected accounts and matches them against your listingsAPI locations.

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

Parameters

Body

NameTypeRequiredDescription
connectedAccountIdsarray of stringsoptionalUUIDs of the connected accounts to trigger matches for. Omit to trigger for all connected accounts on the API key's account.

Responses

200Match run accepted. `success` is `true` when the fetch-and-match job was queued.
{
  "data": {
    "connectedAccountsTriggerMatches": {
      "success": true
    }
  }
}
401Unauthenticated — missing or invalid API key.

Kicks off the asynchronous job that pulls every Google Business Profile and Facebook profile the specified connected accounts can access and matches them against your listingsAPI locations. A success: true response means the job was queued — the matching itself runs in the background.

Pass the accounts you care about in connectedAccountIds. Omitting the field triggers matches for all connected accounts on the API key's account.

Use case — refresh suggestions after connecting a new account. Immediately after a customer completes the Google connect flow, call trigger-matches with that account's connectedAccountId. This populates the suggested location matches so your onboarding UI can show "we found N of your listings" without the customer waiting on a scheduled sync.

Use case — re-run matching after adding locations. When you bulk-create new listingsAPI locations for an existing connected account, trigger a fresh match run so the new locations get paired with their existing Google/Facebook listings.

Because the work is asynchronous, do not treat the 200 as "matching finished." Poll the connected-account details endpoint and wait for requestMatchesStatus to reach MATCH_COMPLETED, then read the results from the connection-suggestions endpoint before calling confirm-matches or connect-listing.

This endpoint queues a live fetch against Google/Facebook. The request shape and sample response above are documented from the API specification; the call is not executed against production data.

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