Queue merge review
POST/customer360/merge-reviews
Queues a merge review for two suspected duplicate profiles. The primary profile is treated as the canonical record. A match score (0–100) and optional context (matching fields/evidence) can be provided. The review enters 'queued' status for an operator to resolve.
Request
Request body
Content type application/json (required).
| Field | Type | Required | Description |
|---|---|---|---|
primary_profile_id | integer | Yes | ID of the profile to keep as canonical. Must exist in customer360_profiles and differ from secondary_profile_id. |
secondary_profile_id | integer | Yes | ID of the duplicate profile to merge into the primary. Must be different from primary_profile_id. |
match_score | integer, nullable | No | Confidence score (0–100) indicating likelihood of a true duplicate. 100 = certain duplicate. Minimum: 0 · Maximum: 100 |
match_context_json | string, nullable | No | JSON object containing evidence for the match (e.g. matched fields and their values from each profile). |
Example
{
"primary_profile_id": 42,
"secondary_profile_id": 78,
"match_score": 95,
"match_context_json": "{\"email_match\":true,\"phone_match\":true,\"name_similarity\":0.97}"
}Responses
302 Redirect to merge reviews list after queuing
422 Validation error — both profile IDs must exist and must be different
Content type application/json, any.
Example
{
"errors": {
"secondary_profile_id": [
"The secondary profile id and primary profile id must be different."
]
}
}Example request
curl -X POST "https://{tenant}.faciotech.net/api/v1/customer360/merge-reviews" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{"primary_profile_id": 42, "secondary_profile_id": 78, "match_score": 95, "match_context_json": "{\"email_match\":true,\"phone_match\":true,\"name_similarity\":0.97}"}'