Why does this setting fail? I am sending a typing indicator via the Guest API. docs state “the payload must include the conversationId and eventType.”
I use this JSON: {“conversationId”: “123”, “eventType”: “typing”}. It returns 400 Bad Request with “Invalid payload structure”.
The code is simple. I copy-paste from the guide. Why is it broken? I need to fix the read receipt logic now.
Take a look at at the required agentId field; typing indicators require the specific agent context, not just the conversation ID.
{
"conversationId": "123",
"eventType": "typing",
"agentId": "agent-uuid-here"
}You might want to check at the agentId field. The suggestion above is correct, but ensure the UUID matches the active session. In my Django pipelines, missing context triggers 400s. Use platformClient.webMessaging.getGuestsGuestIdTypingIndicator(...) with the full payload. Check logs for mismatched IDs.
curl -X POST https://api.mypurecloud.com/api/v2/webmessaging/guests/{guestId}/typing-indicator \
-H "Authorization: Bearer $TOKEN" \
-d '{"conversationId": "123", "eventType": "typing", "agentId": "uuid"}'
If I remember correctly, the 400 error stems from missing the agentId. The suggestion above highlights this, but ensure your OAuth scope includes webmessaging:guest:write. Without it, the payload validation fails immediately.
You should probably look at at the structural completeness of your payload, as the agentId is mandatory for server-side validation in this endpoint. The suggestion above is correct, but ensure the UUID matches the active session to prevent 400s.
{
"conversationId": "123",
"eventType": "typing",
"agentId": "agent-uuid-here"
}