Thank you so much for the detailed clarification - that completely clears things up!
Original Message:
Sent: 07-01-2025 06:42
From: Jerome Saint-Marc
Subject: Open Messaging Typing Indicator -- Inbound and -- Outbound
Hello,
I think you are possibly confusing the different Open Messaging API endpoints ("agent" side, "open messaging gateway/external user" side).
If you want to notify Genesys Cloud that your external user is typing (and to display a notification in Agent Desktop UI that the external user is typing), you need to use: POST /api/v2/conversations/messages/{integrationId}/inbound/open/event
If you want to "forward/send" a message from your external user to Genesys Cloud, you need to use: POST /api/v2/conversations/messages/{integrationId}/inbound/open/message
If you want to report the delivery status (delivered, failed) of a message received previously from Genesys Cloud, via a receipt, you need to use: POST /api/v2/conversations/messages/{integrationId}/inbound/open/receipt
These 3 API Endpoints are only supported with a token issued via an OAuth Client Credentials Grant flow (using a Client Credentials Grant OAuth Client).
This API endpoint is to be used by a Contact Center Agent (i.e. using a token issued for this user - user context) to let the Open Messaging Gateway/External User know that the Contact Center Agent is typing.
Regards,
------------------------------
Jerome Saint-Marc
Senior Development Support Engineer
Original Message:
Sent: 06-27-2025 08:13
From: Nacho González-Garilleti Ruiz
Subject: Open Messaging Typing Indicator -- Inbound and -- Outbound
Hi Syed,
Thanks for sharing your findings. I'm currently facing the exact same issue.
I'm working on a similar Open Messaging middleware integration and encountered the same behaviour:
Sending a typing event via /api/v2/conversations/messages/{conversationId}/communications/{communicationId}/typing returns a 204 No Content,
But the typing indicator never appears on the agent's side when the user is typing.
Additionally, I observed that the endpoint is not functioning when using the client_credentials grant, despite the Genesys API documentation indicating that this grant type is supported. The response in that case is:
{ "message": "This request requires a user context. Client credentials cannot be used for requests to this resource.", "code": "bad.request"}
I've opened a support ticket with Genesys, and so far, it appears that the functionality to display end-user typing indicators to the agent may not be supported at all, although it's not clearly documented.
Did you manage to get this working, or have you received any official clarification?
I would appreciate any update you can share.
Best regards,
Nacho González
------------------------------
Nacho González-Garilleti Ruiz
Original Message:
Sent: 04-25-2025 20:47
From: Syed Noman Hassan
Subject: Open Messaging Typing Indicator -- Inbound and -- Outbound
I was able to successfully display the Agent Typing indicator on the UI. However, I'm still struggling to show the typing indicator on the Agent's view when a customer is typing from the UI.
I tried using the /api/v2/conversations/messages/{conversationId}/communications/{communicationId}/typing endpoint from the Developer Tools with valid conversationId and communicationId. Although I received a 204 response indicating "Message typing event sent," the typing indicator does not appear on the Agent's screen.
Could someone please assist me in finding a solution?
------------------------------
Syed Noman Hassan
Sr Lead Applications Developer Analyst
Original Message:
Sent: 04-22-2025 09:23
From: Syed Noman Hassan
Subject: Open Messaging Typing Indicator -- Inbound and -- Outbound
I am developing middleware that enables Open Messaging to process message requests originating from the UI. These requests are routed through an API gateway, which then passes them to a function responsible for executing the relevant Open Messaging APIs.
Currently, I have implemented two-way communication: the UI can send inbound requests to Genesys Cloud, which receives these and routes the interaction to an agent. The agent's responses are also displayed on the UI.
I now want to enhance the user experience by displaying a typing indicator on the UI when the agent is typing, and likewise, showing a typing indicator to the agent when the user is typing.
The Open Messaging API provides a POST endpoint at /api/v2/conversations/messages/{conversationId}/communications/{communicationId}/typing
which, as I understand, is used to signal the typing indicator for inbound events (i.e., when the user is typing a reply).
My questions are:
- Which API should be used to notify the UI when the agent is typing, so that the typing indicator appears for the user?
- How does the typing indicator function within the message configuration settings, where I have already enabled the typing indicator?
#MobileMessenger
#PlatformAPI
#WebMessaging
------------------------------
Regards,
Syed Noman Hassan
------------------------------