Genesys Cloud
Deprecation of current External Contacts Merge Endpoint
| Announced on | Effective date | Aha! idea |
|---|---|---|
| 2025-07-21 | 2025-11-17 | - |
On the effective date, Genesys Cloud will deprecate the following components in the External Contacts API:
- The current merge endpoint: POST /api/v2/externalcontacts/merge/contacts
- The mergeOperation in the contact object.
Genesys Cloud will replace these endpoints with a new Merge Endpoint: POST /api/v2/externalcontacts/contacts/merge. The new Merge Endpoint enables developers and administrators to perform these tasks:
- Merge up to 25 contacts (N-way merging), an increase over the previous ability to merge only two contacts.
- Merged contacts can be of any type instead of restricting the merge operation to only certain types, such as ephemeral and identified.
- Requests can contain a valueOverride to set fields in the resulting contact after merge.
FAQs
Am I affected?
If you use the existing Merge Endpoint to merge contacts, you are affected by this deprecation.
What do I need to do before the removal date?
Genesys recommends reviewing the new Merge Endpoint: POST /api/v2/externalcontacts/contacts/merge to take advantage of the enhanced features and future support.
How can I prepare for this deprecation?
Review your current integrations and begin transitioning to the new Merge API. Plan your migration to ensure continued functionality and access to the latest improvements.
What if I need help or have questions?
Contact your Genesys account team. You can also visit My Support for additional assistance.
