Summary
Following our ACD Web Chat v2 Deprecation Announcement, we are announcing removal for all related Chat API v2 resources and Chat Widgets versions (Version 1.1, Version 2 and Third Party widgets). This includes the use of Third-Party Chat Routing.
All existing customers are encouraged to migrate to Web Messaging Guest APIs, and/or our Messenger App which includes both a native messaging UI client and a JavaScript SDKto build a customer client.
More Web Messaging information available here, including migration guide from Web Chat to Web Messaging.
Effective Date
Tuesday, February 3, 2026
Details
We are announcing the removal of ACD Web Chat in order to focus all our efforts and resources on building and expanding Web Messaging, which adds a modern async experience to traditional chat, and better aligned to future expansion on Messenger as a unified framework of digital apps (including Messaging, Knowledge, Co-browse, and more coming soon). This also allows us to leverage modern technology stack for APIs and JavaScript or Mobile SDKs, for improved integration and overall stability & security.
Customer Impact
The following APIs are impacted by this removal announcement:
Impacted Resources
Widgets APIs:
GET /api/v2/widgets/deployments
POST /api/v2/widgets/deployments
DELETE /api/v2/widgets/deployments/{deploymentId}
GET /api/v2/widgets/deployments/{deploymentId}
PUT /api/v2/widgets/deployments/{deploymentId}
Guest Chat APIs:
POST /api/v2/webchat/guest/conversations
GET /api/v2/webchat/guest/conversations/{conversationId}/mediarequests
GET /api/v2/webchat/guest/conversations/{conversationId}/members
DELETE /api/v2/webchat/guest/conversations/{conversationId}/members/{memberId}
GET /api/v2/webchat/guest/conversations/{conversationId}/members/{memberId}
POST /api/v2/webchat/guest/conversations/{conversationId}/members/{memberId}/messages
POST /api/v2/webchat/guest/conversations/{conversationId}/members/{memberId}/typing
GET /api/v2/webchat/guest/conversations/{conversationId}/messages
GET /api/v2/webchat/guest/conversations/{conversationId}/messages/{messageId}
Agent Chat APIs:
GET /api/v2/conversations/chats/{conversationId}/messages
GET /api/v2/conversations/chats/{conversationId}/messages/{messageId}
POST /api/v2/conversations/chats/{conversationId}/communications/{communicationId}/messages
POST /api/v2/conversations/chats/{conversationId}/communications/{communicationId}/typing
GET /api/v2/conversations/chats
POST /api/v2/conversations/chats
GET /api/v2/conversations/chats/{conversationId}
PATCH /api/v2/conversations/chats/{conversationId}
GET /api/v2/conversations/chats/{conversationId}/mediarequests
POST /api/v2/conversations/chats/{conversationId}/mediarequests
DELETE /api/v2/conversations/chats/{conversationId}/mediarequests/{mediaRequestId}
GET /api/v2/conversations/chats/{conversationId}/mediarequests/{mediaRequestId}
PATCH /api/v2/conversations/chats/{conversationId}/participants/{participantId}
PATCH /api/v2/conversations/chats/{conversationId}/participants/{participantId}/attributes
PATCH /api/v2/conversations/chats/{conversationId}/participants/{participantId}/communications/{communicationId}
GET /api/v2/conversations/chats/{conversationId}/participants/{participantId}/communications/{communicationId}/wrapup
POST /api/v2/conversations/chats/{conversationId}/participants/{participantId}/communications/{communicationId}/wrapup
POST /api/v2/conversations/chats/{conversationId}/participants/{participantId}/replace
GET /api/v2/conversations/chats/{conversationId}/participants/{participantId}/wrapup
GET /api/v2/conversations/chats/{conversationId}/participants/{participantId}/wrapupcodes
PUT /api/v2/conversations/chats/{conversationId}/recordingstate
Miscellaneous Chat APIs:
POST /api/v2/conversations/chats/memberauthtoken
GET /api/v2/routing/queues/{queueId}/conversations/chats
GET /api/v2/webchat/settings
DELETE /api/v2/webchat/settings
PUT /api/v2/webchat/settings
Issue References
PURE-5918
DEVENGSD-647
DEVENGSD-819
Contacts
@Chad Hansen Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.