# In-Meeting Recording Controls API error Round 2 **URL:** \ **Category:** API and Webhooks\ **Created:** [March 3, 2021, 11:10pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810 "2021-03-03T23:10:48Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![ryan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ryan/32/37137_2.png) [@ryan](https://devforum.zoom.us/u/ryan)\ **Post date:** [March 3, 2021, 11:10pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/1 "2021-03-03T23:10:48Z")
I’m still trying to hunt down the error described in [this thread](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error/27589) with the [In-Meeting recording controls API](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/inmeetingrecordingcontrol). In our user OAuth app, _some_ users are able to make the API call, but some users always get back a 400 error with the body: ```auto %{"code" => 200, "message" => "No permission."} ``` These users have the same set of OAuth scopes (`meeting:write` in particular) and have Zoom Pro licenses. And yes, these users are the host of the meeting they are making the call on. ---
**Author:** ![ryan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ryan/32/37137_2.png) [@ryan](https://devforum.zoom.us/u/ryan)\ **Post date:** [March 3, 2021, 11:17pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/2 "2021-03-03T23:17:45Z")
Looks like ZOOM-190194 is the ticket number in question. ---
**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\ **Post date:** [March 4, 2021, 4:16pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/3 "2021-03-04T16:16:55Z")
Hey @ryan, Thanks for reaching back out about this. Can you confirm that these users have the `user:write` scope as well? Thanks, Will ---
**Author:** ![ryan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ryan/32/37137_2.png) [@ryan](https://devforum.zoom.us/u/ryan)\ **Post date:** [March 4, 2021, 4:40pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/4 "2021-03-04T16:40:42Z")
Yes, both users have these same scopes: ```auto {meeting:read,meeting:write,recording:read,user:read,user:write} ``` ---
**Author:** ![ryan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ryan/32/37137_2.png) [@ryan](https://devforum.zoom.us/u/ryan)\ **Post date:** [March 4, 2021, 4:43pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/5 "2021-03-04T16:43:06Z")
Also of note, for this group of users I am testing with, all are in the same Zoom account. One of them users can make the call, the other three cannot. I tried applying the `developer` role to all users on a whim since that was one clear difference, but to no avail. ---
**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\ **Post date:** [March 5, 2021, 5:00pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/6 "2021-03-05T17:00:35Z")
Hey @ryan, Thanks for confirming. Can you share the details of the users (id or email), the full request URL, and any other additional details you have with me at [developersupport@zoom.us](mailto:developersupport@zoom.us)? Please reference this thread and I’ll be happy to look into this for you. Thanks, Will ---
**Author:** ![ryan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ryan/32/37137_2.png) [@ryan](https://devforum.zoom.us/u/ryan)\ **Post date:** [March 5, 2021, 9:24pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/7 "2021-03-05T21:24:01Z")
Ok, I’ve sent the email! Request [#10076184](https://support.zoom.us/hc/requests/10076184) ---
**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\ **Post date:** [March 5, 2021, 10:20pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/8 "2021-03-05T22:20:18Z")
Thanks, @ryan! Confirming I’ve received the email and will follow up there. Best, Will ---
**Author:** ![ryan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ryan/32/37137_2.png) [@ryan](https://devforum.zoom.us/u/ryan)\ **Post date:** [March 9, 2021, 5:39pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/9 "2021-03-09T17:39:03Z")
For those following along, Will confirmed that access to these APIs is controlled by user roles as opposed to OAuth scopes like other APIs (and that the documentation will be updated to reflect that). ---
**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\ **Post date:** [March 9, 2021, 9:10pm UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/10 "2021-03-09T21:10:49Z")
Thanks for sharing this here @ryan! 🙂 ---
**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:** [April 9, 2021, 7:10am UTC](https://devforum.zoom.us/t/in-meeting-recording-controls-api-error-round-2/44810/11 "2021-04-09T07:10:50Z")
Closed on April 9, 2021, 7:10am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.