Unable to get list of members in Channel. GET /chat/users/{userId}/channels/{channelId}/members returns "No permission to access this channel."

Hi,

I am asking whether there is a related update about this? I am using account-level App and never face any issue in order to get list of members in channel using this endpoint: GET /chat/users/{userId}/channels/{channelId}/members. I have also selected all the relevant scopes. Currently, it always returns “No permission to access this channel.”

I’m a bit confused. Are you saying it was working before and now it is not? Or did you mean you are able to get the members from a different endpoint than the one above?

To confirm, the scope you have is team_chat:read:list_members:admin and you’re passing the channel owner’s user Id or me if you are the channel owner?

Thanks!

Yes you are correct, It was working before and now it is not.

This scope team_chat:read:list_members:admin is already selected as well.

I always use me even though I am not the channel owner (before this issue, this is working fine)

I also did test creating a new channel where I am the owner and using me but it also didn’t work

Thanks!

Hi @Steven7 ,

Thanks for confirming. Please send the zm-tracking-id from the response headers and responses for each please.

Another quick question: are you using userId or the user’s email address for the userId url param? We had an issue on another couple of endpoints whereby email address was no longer working, but userId was successful.

Hi @gianni.zoom ,

this is the zm-tracking-id: v=2.0;clid=us02;rid=WEB_8d7c1b8439f987eac07abf920feb47c4

response:

{“code”:403,“message”:“No permission to access this channel.”}

I am using userId for the endpoint

Thanks

Thanks @Steven7 , investigating this.

@Steven7 confirmed this is a bug on our end. Fix should be deployed this weekend. Please try again on Monday and let me know,

Hi @gianni.zoom ,

Okay thanks for your help!

1 Like

Hi @gianni.zoom ,

This bug is already fixed. Thanks for your help!

1 Like

Running into the same issue here was working fine before, and now suddenly getting the same “No permission” error. Permissions and scopes haven’t changed on my end either. Hoping it’s just a bug or recent change in the API behavior.

@Norma the fix went out this weekend. Can you please check again?