PATCH method to update a setting meeting_authentication

I’m catch a webhook on meeting creation. Taking only those from specific groups.
Next I need to update a meeting_authentication and set it to the true value.
For some reason that method just doesn’t works.
I’m not getting any error, it just pass me back all the details about the meeting.
Using Oauth2, content-Type - application/json, example body:
{
“settings”: {
“meeting_authentication”: true
}
}
example URL https://api.zoom.us/v2/meetings/{meetingID}

Please, help…

Hey @artem.hryhorian,

Thanks for reaching out about this—can you please share the full request URL and response body as well? This will help me to take a closer look.

Thanks,
Will

Hi @will.zoom,

Sure, an input:
{
“url”: “https://api.zoom.us/v2/meetings/98550719201”,
“body”: “{\n “settings”: {\n “meeting_authentication”: true\n }\n}”,
“method”: “PATCH”,
“headers”: [{
“name”: “Authorization”,
“value”: “Bearer {{$.steps.zoom-4.access_token}}”
}, {
“name”: “Content-Type”,
“value”: “application/json”
}],
“timeout”: 0,
“ssl_verification”: “No”,
“parse_response_body”: “json”
}

an output:
{
“body”: {
“id”: 98550719201,
“type”: 2,
“uuid”: “AP9VZS80RNGdE8BPkxyGzg==”,
“topic”: “My Meeting”,
“agenda”: “”,
“status”: “waiting”,
“host_id”: “HRAiaf4LRG6LGeb3UnppXw”,
“duration”: 60,
“join_url”: “https://idealscorp.zoom.us/j/98550719201”,
“settings”: {
“audio”: “both”,
“use_pmi”: false,
“watermark”: false,
“cn_meeting”: false,
“host_video”: true,
“in_meeting”: false,
“waiting_room”: true,
“approval_type”: 2,
“enforce_login”: false,
“auto_recording”: “cloud”,
“mute_upon_entry”: false,
“join_before_host”: false,
“alternative_hosts”: “”,
“participant_video”: true,
“close_registration”: false,
“enforce_login_domains”: “”,
“global_dial_in_numbers”: [{
“type”: “toll”,
“number”: “+1 4388097799”,
“country”: “CA”,
“country_name”: “Canada”
}, {
“type”: “toll”,
“number”: “+1 5873281099”,
“country”: “CA”,
“country_name”: “Canada”
}, {
“type”: “toll”,
“number”: “+1 6473744685”,
“country”: “CA”,
“country_name”: “Canada”
}, {
“type”: “toll”,
“number”: “+1 6475580588”,
“country”: “CA”,
“country_name”: “Canada”
}, {
“type”: “toll”,
“number”: “+1 7789072071”,
“country”: “CA”,
“country_name”: “Canada”
}, {
“type”: “toll”,
“number”: “+1 2042727920”,
“country”: “CA”,
“country_name”: “Canada”
}, {
“type”: “tollfree”,
“number”: “+1 8557038985”,
“country”: “CA”,
“country_name”: “Canada”
}, {
“type”: “toll”,
“number”: “+1 3017158592”,
“country”: “US”,
“country_name”: “US”
}, {
“type”: “toll”,
“number”: “+1 3126266799”,
“country”: “US”,
“country_name”: “US”
}, {
“type”: “toll”,
“number”: “+1 3462487799”,
“country”: “US”,
“country_name”: “US”
}, {
“type”: “toll”,
“number”: “+1 6465588656”,
“country”: “US”,
“country_name”: “US”
}, {
“type”: “toll”,
“number”: “+1 6699006833”,
“country”: “US”,
“country_name”: “US”
}, {
“type”: “toll”,
“number”: “+1 2532158782”,
“country”: “US”,
“country_name”: “US”
}, {
“type”: “tollfree”,
“number”: “+1 8887880099”,
“country”: “US”,
“country_name”: “US”
}, {
“type”: “toll”,
“number”: “+44 2039017895”,
“country”: “GB”,
“country_name”: “United Kingdom”
}, {
“type”: “toll”,
“number”: “+44 2080806591”,
“country”: “GB”,
“country_name”: “United Kingdom”
}, {
“type”: “toll”,
“number”: “+44 2080806592”,
“country”: “GB”,
“country_name”: “United Kingdom”
}, {
“type”: “toll”,
“number”: “+44 3300885830”,
“country”: “GB”,
“country_name”: “United Kingdom”
}, {
“type”: “toll”,
“number”: “+44 1314601196”,
“country”: “GB”,
“country_name”: “United Kingdom”
}, {
“type”: “toll”,
“number”: “+44 2034815237”,
“country”: “GB”,
“country_name”: “United Kingdom”
}, {
“type”: “toll”,
“number”: “+44 2034815240”,
“country”: “GB”,
“country_name”: “United Kingdom”
}, {
“type”: “tollfree”,
“number”: “+44 8000315717”,
“country”: “GB”,
“country_name”: “United Kingdom”
}],
“meeting_authentication”: false,
“global_dial_in_countries”: [“GB”, “CA”, “US”],
“registrants_confirmation_email”: true,
“registrants_email_notification”: true,
“request_permission_to_unmute_participants”: false
},
“timezone”: “Europe/Kiev”,
“start_url”: “123”,
“created_at”: “2020-09-28T13:46:54Z”,
“host_email”: “123”,
“start_time”: “2020-09-28T14:00:00Z”,
“assistant_id”: “”
},
“code”: 200,
“info”: {
“total_time”: 0.430272,
“request_url”: “https://api.zoom.us/v2/meetings/98550719201”,
“content_type”: “application/json;charset=UTF-8”,
“redirect_url”: “”,
“request_body”: “{\n “settings”: {\n “meeting_authentication”: true\n }\n}”,
“request_size”: 775,
“size_download”: 3342,
“request_method”: “GET”,
“ssl_verify_result”: 19,
“download_content_length”: 3342
},
“request_headers”: ["Authorization: Bearer 123”, “Content-Type: application/json”],
“response_headers”: {
“Date”: “Mon, 28 Sep 2020 13:47:24 GMT”,
“Vary”: “Access-Control-Request-Headers”,
“Pragma”: “no-cache”,
“Server”: “ZOOM”,
“Expires”: “Thu, 01 Jan 1970 00:00:00 GMT”,
“http_code”: “HTTP/1.1 200 “,
“Connection”: “keep-alive”,
“Set-Cookie”: “_zm_chtaid=””; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly”,
“Content-Type”: “application/json;charset=UTF-8”,
“Cache-Control”: “no-cache, no-store, must-revalidate, no-transform”,
“Content-Length”: “3342”,
“Referrer-Policy”: “strict-origin-when-cross-origin”,
“x-zm-trackingid”: “WEB_a5d6df69e996a50ac75673016658dbcf”,
“X-XSS-Protection”: “1; mode=block”,
“X-RateLimit-Category”: “Light”,
“X-Content-Type-Options”: “nosniff”,
“Strict-Transport-Security”: “max-age=31536000; includeSubDomains”
}
}

Hey @artem.hryhorian,

Thanks for providing that! As a next step, can you ensure that there aren’t any account-wide settings that might be overriding your PATCH request? Please check your Authentication Profiles to ensure this setting is selected as you wish:

After you’ve checked this, can you try sending the following request in Postman and let me know if you’re having the same issue? So far I’m not able to replicate this—I’ve been able to update the meeting_authentication field within the settings object without an issue. Note that you should get a 204 successful response, and nothing will be returned in the response body, but the update should be reflected when you do a subsequent GET request.

curl --location --request PATCH 'https://api.zoom.us/v2/meetings/{meetingId}' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer {token}' \
--header 'Cookie: _zm_lang=en-US; _zm_mtk_guid=85b1581b57884cae8199dc6228eace1e; _zm_date_format=mm/dd/yy; _zm_page_auth=us04_c_1q7rjCX8TKSEl14w6WpJgA; _zm_ssid=us04_c_jNZDcPneT6qLZDeTIeoQWg; cred=DCCC7D87DDB88FC88C741F51282FFEEB' \
--data-raw '{
  "settings": {
    "meeting_authentication": true
  }
}'

Thanks—please let me know how it goes!

Best,
Will

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.