We’re building a custom client wrapper around the Web Messaging Guest API for a specific internal tool, and I’m hitting a wall with the typing indicators. The documentation for the Guest API v2 suggests that sending a typing event should be as simple as a POST to /api/v2/conversations/messaging/{conversationId}/typing.
Here is the payload I’m sending:
{
"typing": true
}
I’ve got the JWT generated correctly from the createGuest endpoint, and I’m including it in the Authorization header. The conversation ID is definitely valid because I can fetch the messages without issue using the same token.
The response I get back is consistently a 405 Method Not Allowed. I’ve double-checked the method (POST), the content-type (application/json), and the endpoint path. I’ve also tried adding the x-correlation-id header just in case, but no luck.
Interestingly, if I try to send a read receipt to /conversations/messaging/{conversationId}/read, that works fine with a 204 No Content. It’s just the typing endpoint that refuses the POST.
Has anyone else seen this behavior? Is the typing endpoint actually disabled for Guest API tokens, or is there a specific header I’m missing that allows this action? I’ve been staring at the docs for an hour and it looks correct to me.
POST /api/v2/conversations/messaging/CONV-ID-123/typing HTTP/1.1
Host: mycompany.genesyscloud.com
Content-Type: application/json
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
{
"typing": true
}
Response:
HTTP/1.1 405 Method Not Allowed
Content-Type: application/json
{
"code": "badRequest",
"message": "Method Not Allowed"
}