Skip to main content

Our development team is trying to implement Mark Chat as Read and Mark Chat as Unread functionality to ACO Team Messaging chats. We already have calls like getChat and getPost successfully implemented.

When we are testing the markChatAsRead and markChatAsUnread API on the api reference page, we are getting the "In order to call this api endpoint, application needs to have [TeamMessagingInternal] permission" 403 error.

The API reference docs say that the scope is TeamMessagingInternal: https://developers.ringcentral.com/api-reference/Chats/markChatReadNew

But there is no TeamMessagingInternal scope in the list of available scopes for our app.

We have the all these scopes selected:

Edit Messages, Edit Presence, Internal Messages, Read Accounts, Read Contacts, Read Messages, Read Presence, Team Messaging, Webhook Subscriptions


We tried adding almost all other available scopes to circumvent this issue, but to no avail, and as there is no scope named TeamMessagingInternal offered to us, we're unable to execute this request.

We are also not sure what other approach we could take to make the Mark chat as read and Mark chat as unread features work.

Is there a way to avoid the 403 permission error that we are not seeing?







They are new APIs and it seems they are not ready for public. Let me check with the team to see how can we make them fully available.

I got a confirmation from the team that the above mentioned APIs are not meant for public. they are accidentally listed in the public domain and will be withdrew from the list soon.

So, the answer is there is no API to set the read/unread properties of a team messaging chat.

Reply


Terms & ConditionsCookie settings