Building a custom chat UI with the Guest API. Connection establishes fine, but sending the first guest_message event causes an immediate WebSocket close with code 1000. Here’s the payload:
{"event":"guest_message", "data":{"text":"hi"}}
No error logs on the server side. Just drops. Am I missing a specific header or sequence?
The issue isn’t the header. It’s the payload structure. You’re sending a raw JSON object, but the WebSocket expects a specific string format with metadata. The Guest API docs are notoriously sparse on this, but the schema requires a timestamp and usually a correlationId if you want to track it.
Here’s what actually works in our .NET integration:
var message = new {
event = "guest_message",
data = new {
text = "hi",
timestamp = DateTimeOffset.UtcNow.ToString("o") // ISO 8601
}
};
var json = JsonConvert.SerializeObject(message);
await webSocket.SendAsync(json, WebSocketMessageType.Text, true);
Also, check if you’re hitting a rate limit immediately. Genesys throttles guest connections hard if they don’t send the initial guest_ready event first. The sequence matters. You need to send guest_ready after the handshake, wait for the server’s guest_welcome, and then send guest_message. Skipping that step causes the 1000 close because the server thinks the client is broken.
From the docs: “Clients must acknowledge the welcome message before sending data.”
If you’re using System.Net.WebSockets, make sure you’re not buffering incorrectly. The send needs to be complete. We had this exact issue in an Azure Function until we switched to a proper async wait on the send operation.
Try adding the guest_ready step first. It usually fixes the immediate disconnect.