Hey everyone,
I’m seeing a weird issue with the Web Messaging Guest API. I’ve got a custom frontend built with React that talks directly to Genesys Cloud, skipping the standard SDK for this specific flow to handle some legacy data mapping.
Everything works fine for sending actual messages, but the typing indicators and read receipts are ghosting me. The API calls return a 200 OK status, so Genesys thinks everything is fine, but the agent console shows nothing. No “User is typing…” bubble, nothing.
Here’s the JSON payload I’m sending to /api/v2/conversations/messaging/messages/{messageId}/typing-indicator:
{
"action": "start",
"source": {
"id": "guest-session-12345",
"type": "guest"
}
}
I’ve verified the messageId matches the current conversation context. I even tried switching action to stop just to see if that triggers anything, but same result. The docs say this endpoint pushes updates via WebSocket, but I don’t have a WebSocket connection established from this custom frontend-only REST calls.
Is the WebSocket connection mandatory for the indicator to render on the agent side, or am I missing a header? The SDK handles this automatically, but since I’m bypassing it, I feel like I’m missing a handshake step.
Thanks.