# Invalid scope: meeting:read as system can't support! (4,700)

**URL:** <https://devforum.zoom.us/t/invalid-scope-meeting-read-as-system-cant-support-4-700/5857>\
**Category:** API and Webhooks\
**Created:** [September 11, 2019, 8:34pm UTC](https://devforum.zoom.us/t/invalid-scope-meeting-read-as-system-cant-support-4-700/5857 "2019-09-11T20:34:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![brad](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/brad/32/927_2.png) [@brad](https://devforum.zoom.us/u/brad)\
**Post date:** [September 11, 2019, 8:34pm UTC](https://devforum.zoom.us/t/invalid-scope-meeting-read-as-system-cant-support-4-700/5857/1 "2019-09-11T20:34:00Z")

</div>

I’ve been working off of a Zoom OAuth application under my own Zoom account, but as we’re about to submit our application for review, I asked my client to create an OAuth app under his own Zoom account, which we then configured to match my own.

I then adjusted our (Rails) application to use the new keys, but now when I try to OAuth, I get the following error:

```auto
Invalid scope: meeting:read as system can't support! (4,700)

```

I’ve double-checked that the new OAuth app is `user-managed` and has the `meeting:read` scope, so I can’t quite make sense of this error message. Any help would be greatly appreciated!

## App Info

The public IDs for the two apps:

```auto
Old Client ID: 9aAi9nDOSBWDjAvW7e6uRw
New Client ID: s0fCHWtQTyegiWoaLuT6ZA

```

And here’s our list of scopes:

```auto
meeting:read
meeting:write
recording:read
recording:write
user:read
user:write

```

(… which all show as `Saved` for the new Zoom OAuth app.)

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [September 11, 2019, 9:06pm UTC](https://devforum.zoom.us/t/invalid-scope-meeting-read-as-system-cant-support-4-700/5857/2 "2019-09-11T21:06:21Z")

</div>

Hey @brad, thanks for the detailed post.

Where in the OAuth flow is this happening? After Authorizing the App, requesting an access\_token, or refreshing an access\_token?

Also are you using the local test url or publishable url when getting this error? (I am assuming publishable).

Can you share the request url, headers, and body that is throwing this error so I can try to debug. (leaving out api credentials)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![brad](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/brad/32/927_2.png) [@brad](https://devforum.zoom.us/u/brad)\
**Post date:** [September 12, 2019, 12:14am UTC](https://devforum.zoom.us/t/invalid-scope-meeting-read-as-system-cant-support-4-700/5857/3 "2019-09-12T00:14:34Z")

</div>

Thanks for such a quick reply!

Apologies for not mentioning where I was running into the issue; I’m getting the error when going through the authorization flow, in-browser, before what would normally be the Zoom prompt asking if I want to authorize the app for the given scopes.

Here’s a specific example of a request (in-browser) that’s giving me the error:

```auto
https://zoom.us/oauth/authorize?client_id=s0fCHWtQTyegiWoaLuT6ZA&redirect_uri=https%3A%2F%2Fapp.anatomy.one%2Fusers%2Fauth%2Fzoom%2Fcallback&response_type=code&scope=meeting%3Aread%2Cmeeting%3Awrite%2Crecording%3Aread%2Crecording%3Awrite%2Cuser%3Aread%2Cuser%3Awrite&state=0b61d22af4ee5fc9c5365efab2e9e661fd55e64c32d4f5d3

```

Which, URI decoded, is:

```auto
https://zoom.us/oauth/authorize?client_id=s0fCHWtQTyegiWoaLuT6ZA&redirect_uri=https://app.anatomy.one/users/auth/zoom/callback&response_type=code&scope=meeting:read,meeting:write,recording:read,recording:write,user:read,user:write&state=0b61d22af4ee5fc9c5365efab2e9e661fd55e64c32d4f5d3

```

And it’s just a `GET` from the browser, so I imagine the headers aren’t of much interest, but here’s what I see in the `Network` tab in Firefox, just in case:

```auto
Accept : text/html,application/xhtml+xm…plication/xml;q=0.9,*/*;q=0.8
Accept-Encoding : gzip, deflate, br
Accept-Language : en-US,en;q=0.5
Cache-Control : no-cache
Connection : keep-alive
Cookie : cred=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX; __zlcmid=XXXXXXXXXXXXXX
Host : zoom.us
Pragma : no-cache
Upgrade-Insecure-Requests : 1
User-Agent : Mozilla/5.0 (X11; Ubuntu; Linu…) Gecko/20100101 Firefox/69.0

```

And to your publishable URL question: I’m using [OmniAuth](https://github.com/omniauth/omniauth) inside of Rails to handle OAuth, so it’s responsible for building / redirecting to this URL. This was functioning just fine before though, and I’m pretty sure the keys are the only thing that have changed. I guess that and the fact that the OAuth app is now not tied to _my_ Zoom account (which I’m attempting to authorize with), but even then, my client (who does own the new app) is getting the same error code (`4,700`), just with a slightly different message:

```auto
Empty scope (either the client or the user is not allowed the requested scopes) (4,700)

```

Thanks so much for your help! Please let me know if I can provide any more detail!

---

<div class="post-metadata">

**Author:** ![brad](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/brad/32/927_2.png) [@brad](https://devforum.zoom.us/u/brad)\
**Post date:** [September 12, 2019, 1:15am UTC](https://devforum.zoom.us/t/invalid-scope-meeting-read-as-system-cant-support-4-700/5857/4 "2019-09-12T01:15:59Z")

</div>

So my client generated a publishable URL and I noticed the only difference was the `scope` param in the OmniAuth URL, so I removed the call in my config that passed the scopes into OmniAuth, and it worked!

The reason I was doing that in the first place was that another OAuth provider (I forget who, but I believe it was Google) was giving me trouble if I didn’t specify them on authorization, so I just added them explicitly to all my OAuth provider configs to avoid issues in the future. (… the irony is not lost on me.)

I’m really not sure why it was working before and just started breaking now though. And honestly, I’d prefer to uniformly pass scopes in for all OAuth providers, so if you happen to notice the issue (maybe it should be space-separated instead of comma-?), I’d appreciate you letting me know.

Either way, thanks so much for your help! Have a good one!

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [September 12, 2019, 6:56pm UTC](https://devforum.zoom.us/t/invalid-scope-meeting-read-as-system-cant-support-4-700/5857/5 "2019-09-12T18:56:22Z")

</div>

Hey @brad, thanks for all the details!

Glad your issue was resolved 🙂 Yes with Zoom OAuth you do not have to add the scopes to the URL, because they are configured in the App Marketplace Dashboard.

You can however add them, but they must be separated by `+` instead of `,`.

```auto
https://zoom.us/oauth/authorize?client_id=s0fCHWtQTyegiWoaLuT6ZA&redirect_uri=https://app.anatomy.one/users/auth/zoom/callback&response_type=code&scope=meeting:read+meeting:write+recording:read+recording:write+user:read+user:write&state=0b61d22af4ee5fc9c5365efab2e9e661fd55e64c32d4f5d3

```

Check out the `scope` query param details here in the table:

> **[OAuth with Zoom - OAuth - Authorization - Documentation](https://marketplace.zoom.us/docs/guides/authorization/oauth/oauth-with-zoom#authorization-code)**
>
> OAuth with Zoom
> 
> 
> 
> Below are examples of how to send requests for Access Tokens and handle responses for OAuth app authentication and authorization with...

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 6:41pm UTC](https://devforum.zoom.us/t/invalid-scope-meeting-read-as-system-cant-support-4-700/5857/6 "2020-08-21T18:41:52Z")

</div>

Closed on August 21, 2020, 6:41pm UTC


