I’m still trying to hunt down the error described in this thread with the In-Meeting recording controls API.
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:
%{"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.