# What Scopes are required to get recordings - Graphql

**URL:** <https://devforum.zoom.us/t/what-scopes-are-required-to-get-recordings-graphql/118705>\
**Category:** GraphQL\
**Tags:** recording, api\
**Created:** [October 7, 2024, 8:38pm UTC](https://devforum.zoom.us/t/what-scopes-are-required-to-get-recordings-graphql/118705 "2024-10-07T20:38:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kristaconlon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kristaconlon/32/63934_2.png) [@kristaconlon](https://devforum.zoom.us/u/kristaconlon)\
**Post date:** [October 7, 2024, 8:38pm UTC](https://devforum.zoom.us/t/what-scopes-are-required-to-get-recordings-graphql/118705/1 "2024-10-07T20:38:34Z")

</div>

Hi,

I have granted just about every scope to my server app, buy I keep getting this error:  
“Invalid access token, meetingRecordings field does not contain required scopes.”,

After adding scopes, I always recreate a new token. Here are the scopes I have granted.

“scope”: “meeting:read:list\_meetings:admin meeting:read:meeting:admin meeting:read:list\_registrants:admin meeting:read:registrant:admin meeting:read:list\_registration\_questions:admin meeting:read:livestream:admin meeting:read:list\_polls:admin meeting:read:poll:admin meeting:read:invitation:admin meeting:read:list\_templates:admin meeting:read:past\_meeting:admin meeting:read:list\_past\_instances:admin meeting:read:list\_past\_participants:admin meeting:read:list\_poll\_results:admin meeting:read:survey:admin meeting:read:participant:admin meeting:read:participant\_feedback:admin meeting:read:participant\_callout:admin meeting:read:alert:admin meeting:read:participant\_sharing:admin meeting:read:device:admin meeting:read:risk\_alert:admin meeting:read:chat\_message:admin meeting:read:local\_archiving\_token:admin meeting:read:live\_streaming\_token:admin meeting:read:list\_upcoming\_meetings:admin meeting:read:past\_qa:admin meeting:read:list\_meetings:master meeting:read:meeting:master meeting:read:summary:master meeting:read:list\_summaries:master cloud\_recording:read:list\_account\_recordings:admin cloud\_recording:write:recording\_registrant:admin cloud\_recording:read:list\_user\_recordings:admin cloud\_recording:update:registration\_questions:admin cloud\_recording:update:recover\_single\_recording:admin cloud\_recording:delete:recording\_file:admin cloud\_recording:update:registrant\_status:admin cloud\_recording:delete:meeting\_recording:admin cloud\_recording:update:recording\_settings:admin cloud\_recording:read:recording\_analytics\_details:admin cloud\_recording:read:recording\_analytics\_summary:admin cloud\_recording:read:recording\_settings:admin cloud\_recording:read:list\_recording\_registrants:admin cloud\_recording:read:list\_recording\_files:admin cloud\_recording:read:registration\_questions:admin cloud\_recording:update:recover\_meeting\_recordings:admin cloud\_recording:write:trimming\_recording:admin cloud\_recording:read:recording:admin cloud\_recording:read:registrant:admin cloud\_recording:read:archive\_files:admin cloud\_recording:read:list\_account\_recordings:master cloud\_recording:write:recording\_registrant:master cloud\_recording:read:list\_user\_recordings:master cloud\_recording:update:registration\_questions:master cloud\_recording:update:recover\_single\_recording:master cloud\_recording:delete:recording\_file:master cloud\_recording:update:registrant\_status:master cloud\_recording:delete:meeting\_recording:master cloud\_recording:update:recording\_settings:master cloud\_recording:read:recording\_analytics\_details:master cloud\_recording:read:recording\_analytics\_summary:master cloud\_recording:read:recording\_settings:master cloud\_recording:read:list\_recording\_registrants:master cloud\_recording:read:list\_recording\_files:master cloud\_recording:read:registration\_questions:master cloud\_recording:update:recover\_meeting\_recordings:master cloud\_recording:read:recording:master cloud\_recording:read:registrant:master archiving:read:list\_archived\_files:admin archiving:update:archived\_file\_auto\_delete\_status:admin archiving:read:archived\_files:admin archiving:delete:archived\_files:admin archiving:read:archived\_file\_statistics:admin archiving:read:archive\_files:admin archiving:read:list\_archived\_files:master archiving:read:archive\_files:master”,

---

<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:** [October 8, 2024, 4:26pm UTC](https://devforum.zoom.us/t/what-scopes-are-required-to-get-recordings-graphql/118705/2 "2024-10-08T16:26:22Z")

</div>

Hi @kristaconlon  
Thanks for reaching out to us, I am sharing a thread with you were I’ve replied to some developers trying to use graphQL with our granular scopes, which is not supported right now

> [@"Invalid access token, userMeetingRecordings field does not contain required scopes."](https://devforum.zoom.us/t/invalid-access-token-usermeetingrecordings-field-does-not-contain-required-scopes/112401/37):
>
> Hi @Radek I wanted to return to this thread and share with you that we care and I apologize if I did not follow up promptly. Granular scopes were introduced earlier this year to allow developers to be more specific about the access granted to third-party apps. By using granular scopes, the permissions an app has to access data are reduced to the least amount necessary to run the app. The issue here is our GraghQL uses our classic scopes and we do not support graphQL with the new granular sc…

Let me know if you have any other questions

---

<div class="post-metadata">

**Author:** ![kristaconlon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kristaconlon/32/63934_2.png) [@kristaconlon](https://devforum.zoom.us/u/kristaconlon)\
**Post date:** [October 8, 2024, 5:29pm UTC](https://devforum.zoom.us/t/what-scopes-are-required-to-get-recordings-graphql/118705/3 "2024-10-08T17:29:24Z")

</div>

Hi,

Well, that doesn’t help at all. Is there a way to update my app to use the broader scopes, so I can move forward with my development? GraphQL enables the code to be simple and flexible as opposed to multiple calls to get the same data.

Please let me know

thanks

---

<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:** [October 10, 2024, 3:45pm UTC](https://devforum.zoom.us/t/what-scopes-are-required-to-get-recordings-graphql/118705/4 "2024-10-10T15:45:43Z")

</div>

Hi @kristaconlon  
If you have an legacy app that you built in the past year, this app will still have Classic scopes

---

<div class="post-metadata">

**Author:** ![kristaconlon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kristaconlon/32/63934_2.png) [@kristaconlon](https://devforum.zoom.us/u/kristaconlon)\
**Post date:** [October 10, 2024, 6:20pm UTC](https://devforum.zoom.us/t/what-scopes-are-required-to-get-recordings-graphql/118705/5 "2024-10-10T18:20:03Z")

</div>

Hi,

Thanks for getting back to me. I just started building an app, so therefore I don’t have a legacy app to leverage. When will this issue be resolved?

thanks
