Esta guía está disponible en inglés.

Detect Duplicate Business Listings via API

Read the duplicate queue across a client with the Synup API, sort by confidence, and know why the match score beats the individual match flags.

Detection runs on its own. Synup scans each publisher for listings that look like the business and scores them, and your job is to read the queue it builds. GET /api/v1/listings/duplicates/rollup returns a summary plus a paginated queue across every location of a client, newest and highest-confidence first when you ask for it.

curl "https://ai.synup.com/api/v1/listings/duplicates/rollup?clientId=CLIENT_ID&filter=potential&band=high&sort=confidence&perPage=100" \
  -H "Authorization: Bearer $SYNUP_API_KEY"

Each candidate carries a matchScore from 0 to 1, a confidence band of high, med or low, and three flags for which fields line up: businessNameMatches, addressMatches, phoneMatches. The summary tells you how many potential duplicates exist, how many locations they hit, and which publishers are the worst offenders.

Start with the high band. Those are almost always real. And trust the score over the three flags: a row can score 1.0 and still report businessNameMatches: false because the duplicate abbreviated the name. The flags are for showing a reviewer why, not for deciding on their own.

For a single location's detail view, GET /api/v1/listings/duplicates groups that location's duplicates by publisher and returns counts for every status. The cheapest signal of all is the duplicates column on GET /api/v1/listings/summary, which flags the locations that need a look without pulling the full queue.

Once you have decided what is real, flagging it for removal is one more call: suppress a duplicate listing. The full duplicates guide covers the lifecycle, the scoped-key rules, and sweeping a publisher in one pass.