# Get Meeting Reports - wrong scope

**URL:** <https://devforum.zoom.us/t/get-meeting-reports-wrong-scope/71053>\
**Category:** API and Webhooks\
**Created:** [June 24, 2022, 9:59am UTC](https://devforum.zoom.us/t/get-meeting-reports-wrong-scope/71053 "2022-06-24T09:59:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![stanimir.varbanov](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@stanimir.varbanov](https://devforum.zoom.us/u/stanimir.varbanov)\
**Post date:** [June 24, 2022, 9:59am UTC](https://devforum.zoom.us/t/get-meeting-reports-wrong-scope/71053/1 "2022-06-24T09:59:54Z")

</div>

I am using Server-to-server Oauth app.

I am trying the endpoint with proper accountId and userId  
[https://api.zoom.us/v2/accounts/{accountId}/report/users/{userId}/meetings](https://api.zoom.us/v2/accounts/%7BaccountId%7D/report/users/%7BuserId%7D/meetings)

The response I get is  
{"code":4700,"message":"Invalid access token, does not contain scopes: [report:master, report:read:master]."}"

In my app I have added the report:read:admin, which is the one menioned in the documentation:

> **[Zoom Meeting Master Account API](https://marketplace.zoom.us/docs/api-reference/zoom-api/ma/#operation/reportMeetings)**
>
> The Zoom Meeting Master Account (MA)....

So the application has report:read:admin, but the endpoint expects report:read:master -  
could this be a bug ?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [June 24, 2022, 2:05pm UTC](https://devforum.zoom.us/t/get-meeting-reports-wrong-scope/71053/2 "2022-06-24T14:05:25Z")

</div>

Hi @stanimir.varbanov  
Thank you for bringing this up to our attention.  
I am doing some debugging on my end and I will come back to you with an update shortly.

Cheers,  
Elisa

---

<div class="post-metadata">

**Author:** ![stanimir.varbanov](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@stanimir.varbanov](https://devforum.zoom.us/u/stanimir.varbanov)\
**Post date:** [June 28, 2022, 11:29am UTC](https://devforum.zoom.us/t/get-meeting-reports-wrong-scope/71053/3 "2022-06-28T11:29:25Z")

</div>

Hi Elisa, any news on this topic ?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [June 28, 2022, 1:32pm UTC](https://devforum.zoom.us/t/get-meeting-reports-wrong-scope/71053/4 "2022-06-28T13:32:38Z")

</div>

Hey @stanimir.varbanov  
Thanks for reaching out back to us.  
I am double checking with the team if this is a Documentation issue or a bug on our end.  
I will reach out to your with an update soon (ZSEE-56190)  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [June 29, 2022, 4:48pm UTC](https://devforum.zoom.us/t/get-meeting-reports-wrong-scope/71053/5 "2022-06-29T16:48:06Z")

</div>

Hi @stanimir.varbanov

Thank you for your patience while I investigated this issue further.  
I just heard back from our Engineering team and I was told that this might be an issue with our Documentation and not a bug per se.  
Could you please make sure to add the scope report:master to your Server to Server Oauth app and try again?  
I was able to call the endpoint once I added the “report:master” endpoint

Please let me know if you need anything else from me  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [July 30, 2022, 2:49am UTC](https://devforum.zoom.us/t/get-meeting-reports-wrong-scope/71053/6 "2022-07-30T02:49:06Z")

</div>

Closed on July 30, 2022, 2:49am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
