200 No Permission

API and Webhooks Reports and Dashboards
1

Hello,

I am trying to make the below api call
https://api.zoom.us/v2/report/users/{userId}/meetings with parameter “type:pastJoined”.
to get a list of meeting for a user. I am using jwt token to authenticate the request.
But getting ‘{“code”:200,“message”:“No permission”}’ error.
I tried initially using Python code using requests library and then using postman and got the same error.
Any help here?
Since JWT token is common across the account and I am sure the account is a paid one(Business Plan). So not sure why I get this error.

Also note that I dont get an error and get a 200 response when I dont pass the parameter “type:pastJoined”.

2

Hi there @puneeth.ranganath

Thanks for reaching out to the Zoom Developer Forum and welcome to our community! I am happy to help here!

This message that you are getting is expected. Right now this feature is still on Beta but allow me some time to ask for an ETA on the GA release.

Best,
Elisa

3

@elisa.zoom Thanks for your response.

Can you please elaborate why this error is expected? I thought with JWT token we should be able to call all endpoints?
Also what should I be doing to avoid this? Will OAUTH app help here?

4

Hi @puneeth.ranganath

This is not about an issue with the JWT at all.
What I meant is that the query parameter type: pastJoined is part of a Beta testing project and its not available yet, that is why you are getting that No permission error

5

@elisa.zoom Ah got it thanks!

1 Like
6

@elisa.zoom Also I have a question regarding the rate limits. Lets say I am accessing the Zoom api to fetch the meeting details etc of my customers(irrespective JWT/OAUTH) - the api rate limits will be applied to the account of my customers right and not to my account? Or is there any limit applied to our service which calls the api on our customer’s behalf?

7

Hey @puneeth.ranganath
You are right, the api rate limits will be applied to the account that is the owner of their JWT/Oauth authorization!
:slight_smile:

8

@elisa.zoom Thanks a lot for confirming.

1 Like
9

Hi,
I was wasting a lot of time searching for MY fault. Why do you list a parameter in the documentation without marking it as “beta”?
We planned to build a feature which needs that parameter and I had no clue, that it would not work after reading the documentation.
It is good to see, what will be available soon, but it should be marked as that.
Could you please write into the documentation if a feature is not yet available?

10

Hi @Florentine
I totally understand how you are feeling about this issue and I will make sure to communicate with the docs team to add a note to our existing documentation that this features is not available yet.
Best.
Elisa