We are using the Channel API (https://api.zoom.us/v2/chat/channels) in our integration, and it was working perfectly until last week. However, we are now encountering an issue where the API fails with the following error message:
“Invalid access token, does not contain permissions: [ChatChannel:Read].”
In our code, we are using the scope chat_channel:read:admin for this endpoint. This scope has been working fine until recently, but now the API seems to require the ChatChannel:Read permission instead, causing our implementation to fail.
Could you please help us understand:
Why this change has occurred?
What specific steps we need to take to resolve this issue?
Your assistance in resolving this matter promptly would be highly appreciated.
Thank you!
Best regards,
Rambabu Rachamalla
Contractor
Engineering Department Fivetran
Just ran into this same issue where receiving error referencing ChatChannel:read scope instead of the chat_channel_read scope when attempting to pull shared spaces with a user auth app.
status 400
“code”:200,“message”:“Invalid access token, does not contain permissions:[ChatChannel:Read].”
Here are the scopes granted to the app:
`team_chat:read:list_shared_spaces` — List shared spaces user has access to-`team_chat:read:shared_space` — Get shared space details- `team_chat:read:list_shared_space_channels` — List channels within shared spaces- `team_chat:read:list_shared_space_members` — List members in a shared space
Hi @elisa.zoom - any insight on why what appears to be a reference to an outdated scope is returning in an error message? Any ideas on solution? Thanks
Hi @AdamB
Thanks for reaching out to us!
I am not able to reproduce this on my end.
I can call the Get/chat/spaces endpoint with a token that has the
“team_chat:read:list_shared_spaces:admin” scope in it and also “team_chat:read:list_shared_spaces”
Can you please confirm that you can see the scope in the payload you get back when generating the access toke?
@elisa.zoom Appreciate your response. I’m actually not using the “team_chat:read:list_shared_spaces:admin” scope - only the instance without admin. Maybe that’s the issue? We’ve had concerns around privacy and chosen not to use the admin scopes. Maybe that’s misplaced in the context of a user auth app?
A little more background - this is a user auth app and we have a dedicated user that we’re adding to channels we want to capture messages for. I’m attempting to view the shared spaces to identify which shared spaces channels are/have been a part of. The company creates channels dedicated to projects and moves the project channels around from one shared space to another as part of a work pipeline. I’m successfully pulling the channel messages and channel info, but a tricky part is trying to track this project pipeline based on what shared space the channel is in!!
Thanks for the clarification @AdamB
I can confirm that I also tested with a user level app and able to see the scope and call the endpoint.
I will send you a DM to get more details so I can take a look at your setup