I am trying to use Zoom’s Chat API with an Oauth application as authentication(right now in development stage). The app is “Admin-managed”, as i need to access all users’ data in my account.
Most endpoint work, like Create a channel, meaning its not a problem in the Oauth flow.
When trying to call endpoints such as Get a Channel i get an error telling me that the token i am using doesn’t have the team_chat:read:channel scope. When trying to add to my app this scope i only see the team_chat:read:channel:admin scope. Even with this scope the endpoint refuses to work.
Hey,
thank you for the reply.
i have tried rerunning and recreating everything and still get the same situation mentioned above.
I would greatly appreciate any help as i am really not sure what else i can do.
thanks.
Hi @joe.smithinc12123
I can replicate the error you are getting when calling the Get a Channel endpoint with an OAuth admin-managed app.
So, what I did to Get a channel with an admin-managed app is that I used the endpoint Get users channels endpoint instead.
You get the same data so you should be able to get all your users data with that endpoint
could you please review this and let me know if that works for you
Hey again,
The endpoint you sent works but it serves a different purpose, it lists all channels for a given user. The way i understand it the Get Channel endpoint returns channel information for a given channel ID, which is the functionality i am looking for.
Are there any plans to add the missing scope/scopes in the future? if so i can go over all my findings and provide a full list of scopes i came a cross that are missing.
Thank you for your help.
Hi @joe.smithinc12123
Sorry I missed this, make sure to ping me so I can get a notification
I totally see what you are saying, I have an internal ticket ( ZOOM-774120) about this issue and will come back with an update as soon as I have it
Any updates about the internal ticket?
Went over my finding again and from what i saw, there is a miss-match in the names from zoom chat api docs and in the setup of the applications. For example
in the docs: chat_message:write but in the app scope selection(the only one that is close): team_chat:write:chat_message. I think it might be a good idea to create another ticket the addresses the issue in the documentation.
hi @joe.smithinc12123
I do not have any updates on the ticket I created for this. I will re-engage with our Engineering team.
For example
in the docs: chat_message:write but in the app scope selection(the only one that is close): team_chat:write:chat_message . I think it might be a good idea to create another ticket the addresses the issue in the documentation.
What endpoint are you talking about? For the Get a channel endpoint, I only see the team_chat:read:channel listed in our Docs and I can see the scope in the server to server oauth app
Hey @elisa.zoom,
Are there any updates about the internal ticket?
I wanted to show a more concrete example of what i am talking about. For example in the endpoint for updating channels, the scope requested is team_chat:update:channel.
When trying to add that scope, there is no scope with a name near to the one asked for. Even when adding all logicaly close scopes is still get the following message.
{
"code": 4711,
"message": "Invalid access token, does not contain scopes [team_chat:update:channel]."
}
