report-ai
customer-profiles

Merge Duplicate Cluster

Changed on

Fold a whole cluster into one survivor, one reversible fold per member.

The cluster is re-derived from live pairs before anything is written. A cluster is computed rather than stored, so the set the operator was looking at can have changed between the read and the click — a pair dismissed, a profile merged some other way, a side reclassified as a shared inbox. Acting on the stale set would merge people nobody agreed to merge, which is the same reason auto-merge re-verifies rather than trusting a materialized row.

post/api/v1/report-ai/customer-profiles/duplicate-clusters/merge

Request

  • Base URL: https://api.getanana.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.getanana.com/api/v1/report-ai/customer-profiles/duplicate-clusters/merge
  • Auth: none declared

Request body

profile_idsstring[] required
survivor_profile_idstring uuid required
confidence_tierstring required

Response

Successful Response

merge_idsstring[] required
survivor_profile_idstring uuid required
merged_profile_idsstring[] required

Changes

  • d65b8fefae34Revision changes
    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status