Unable to update user settings


#1

I am using a sub-account and am having issues with the user settings API.

I make a call to update user setting API - 

PATCH [https://api.zoom.us/v2/users/{userId}/settings](https://api.zoom.us/v2/users/%7BuserId%7D/settings)

I am getting a successful 204 in response, but when I do a subsequent call to get the user settings for that same user -

GET [https://api.zoom.us/v2/users/{userId}/settings](https://api.zoom.us/v2/users/%7BuserId%7D/settings)

the user settings return as if they have not been updated. I don’t believe it be a timing issue as I have tried waiting a few minutes before making the subsequent get settings call.


#2

Hi Dayal, 

Can you send the payload and account ID that you try to update so that we can take a closer look at developersupport@zoom.us? You can take a closer look via logs as well - https://developer.zoom.us/me/call-logs/. 

Thanks


#3

Thanks for the link to the logs. Looks like they match up w/ was sent/received.

 

Account Number: 1164843

Payload sent -

PATCH https://api.zoom.us/v2/users/\<adminUserEmail\>
Authorization: Bearer \<token\>
Accept: application/json, application/xml
Content-Type: application/json

{
 "schedule\_meeting": {
 "host\_video": true
 }
}

#4

Hi Dayal, 

I took a look at the logs and it looks like you called . 

PATCH https://api.zoom.us/v2/users/(user\_id) instead of

PATCH https://api.zoom.us/v2/users/(user\_id)/settings

You will need to call this update user settings to have the user settings updated. 

Thanks


#5

Apologies, looks like that was a mistaken call on my part. Setting of of the “schedule_meeting.host_video” bit works, but not the “recording.auto_recording” bit. It set to “local” I make the call below to set to “cloud” and receive a 204, but a subsequent call to get user settings shows it still set to “local”.

PATCH https://api.zoom.us/v2/users/\<adminUserEmail\>/settings
Authorization: Bearer \<token\>
Accept: application/json, application/xml
Content-Type: application/json

{
 "recording": {
 "auto\_recording": "cloud" 
 } 
}

#6

Hi Dayal, 

I looked at the logs and tried to duplicate the issue but it worked on my end. Can you try to run the Patch API call again and send me the API call log timestamp? 

Thanks