When I searched in the docs for this, I found this error code explanation - chat.error.not.found chat conversation typing-indicator is not found
But, I'm not able to understand the above statement. Can anyone please clarify what error it is indicating?
A 404 "not found" means that the resource you made a request for was not found. The request you're making contains two path parameters: conversationId and communicationId. One or both of them aren't valid and are causing the 404.
Thanks for the response, but I'm pretty sure both the ids are correct. So, does this API require additional websocket connection provided the chat's websocket connection is already established and I'm just trying to authenticate using oauth API and using that bearer token to hit the send typing on behalf of a user of the conversation?
Interacting with a conversation is usually limited to active participants of the conversation.
That's the case with voice to dial or to answer/hold/resume a call, with chat to send messages, ...
So it means you must use an API access token related to a user context (token obtained using OAuth Token Implicit Grant, OAuth Authorization Code Grant, SAML2 Bearer Grant) and the associated user must be an active participant of the conversation.
If you are trying to send this API request using a user context token (of a user who is not an active participant), or using a server context token (OAuth Client Credentials Grant), this API request will likely fail.
You can try to send this same request using the API Explorer (Developer Tools) of a user who is active in the conversation - if it works, then this will confirm what I wrote above.
Thanks for the clarification on API grant types, I was debating on that too as I've read the docs regarding them. I've tested in developer tools and send typing was working fine so the Oauth API might be the issue as I'm using client credentials grant to get access token.