Spent the morning trying to get typing indicators and read receipts working in our custom web chat client. We’re using the Genesys Cloud Web Messaging Guest API directly, not the full SDK, to keep the bundle size down. The initial connection and message sending work fine. I get the 200 OK and the messages appear in the admin UI.
The problem is the auxiliary events. When I send a typing indicator, the API returns a 200, but nothing happens on the agent side. Same with read receipts. I’m sending the payloads exactly as documented.
Here’s the typing indicator POST to /api/v2/conversations/messaging/conversations/{conversationId}/guests/{guestId}/typing:
{
"type": "typing"
}
And for read receipts, I’m POSTing to /api/v2/conversations/messaging/conversations/{conversationId}/guests/{guestId}/read-receipt with:
{
"messageId": "msg-12345-abcde"
}
Both calls return 200. No errors in the logs. I’ve verified the conversationId and guestId are correct by checking the header of a regular message. I even tried adding a timestamp field, thinking maybe that was required, but it didn’t help.
Is there a specific setting in the Admin UI under Web Messaging that enables these features? I’ve checked the channel settings and everything looks default. We’re on the standard configuration. Maybe I’m hitting the wrong endpoint? The docs are a bit sparse on the Guest API specifics compared to the full SDK.
I’ve tried invalidating the token and reconnecting. Still nothing. The agent just sees the message appear, no typing animation, no ‘read’ checkmark. It feels like the events are being swallowed somewhere. Any ideas on what I’m missing?