Skip to content

[DO NOT MERGE] Document user-to-user contact merges (Preview) - #613

Draft
adisan19 wants to merge 1 commit into
mainfrom
adisanarula/document-user-to-user-merge-preview
Draft

[DO NOT MERGE] Document user-to-user contact merges (Preview)#613
adisan19 wants to merge 1 commit into
mainfrom
adisanarula/document-user-to-user-merge-preview

Conversation

@adisan19

@adisan19 adisan19 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Do not merge. Draft documenting user-to-user merge support on the Preview (unstable) spec while the behaviour is being rolled out gradually; it will be closed or taken forward separately once rollout timing is decided.

Documents on descriptions/0/api.intercom.io.yaml:

  • POST /contacts/merge: user-to-user merges (both contacts role: user), which require a shared email or phone; skip_duplicate_validation is not supported for them (400 parameter_not_allowed); 422 responses for non-duplicate pairs and for source contacts with WhatsApp data; a user can never be merged into a lead.
  • POST /contacts/merge/preview: same rules, plus the new blocked-reason codes u2u_no_shared_identifier and source_has_whatsapp_data (schema enum + reason table), and the 400 parameter_not_allowed response.

🤖 Generated with Claude Code

Documents user-to-user merge support on POST /contacts/merge and
POST /contacts/merge/preview in the Preview (unstable) spec: shared
email/phone requirement, the skip_duplicate_validation rejection
(400 parameter_not_allowed), the 422 responses, and the new preview
reason codes u2u_no_shared_identifier and source_has_whatsapp_data.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant