report-ai
customer-profiles

List Duplicate Clusters

Changed on

Open pairs of one tier, closed transitively into review decisions.

One tier per request, never mixed: an exact component and a strong one joined together would be a cluster nobody can act on, because half of it is safe to merge and half needs a person to look.

The closure is computed once and paged in memory. Unlike the pair queue it cannot be paged in SQL — a component is only known once every pair has been walked — so _CLUSTER_COUNT_MAX bounds it and the count says so.

get/api/v1/report-ai/customer-profiles/duplicate-clusters

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
  • Auth: none declared

Query parameters

tierstring
cursorstring nullable

Response

Successful Response

next_cursorstring nullable required
open_countinteger required
last_detected_atstring date-time nullable 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