Genesys Cloud
Deprecation: Current Open Messaging Inbound Endpoint

Announced on Effective date Aha! idea
2024-06-24 2025-01-30 -

Starting January 30, 2025, Genesys will discontinue support of the current Open Messaging Inbound Endpoint. 

The current catch-all endpoint is POST /api/v2/conversations/messages/inbound/open. Once Genesys makes the change, you cannot use the current API endpoint to deliver messages.

As part of the ongoing Open Messaging channel improvements, Genesys has developed the following new API endpoints that extend the existing functionality: 

  • POST /api/v2/conversations/messages/{integrationId}/inbound/open/event – for events 
  • POST /api/v2/conversations/messages/{integrationId}/inbound/open/message – for messages 
  • POST /api/v2/conversations/messages/{integrationId}/inbound/open/receipt – for receipts 

Am I affected?

If you use Genesys Cloud Open Messaging, then you are impacted. 

    How can I prepare for this deprecation?

    Update the middleware to adopt the new endpoints before the deprecation date.

    What if I need help or have questions?

    Reply to the deprecation announcement post in the Developer Forum.