Zoom One - May 23, 2022
import RebrandingAlert from "#content/changelog/_includes/_zoom-one-rebranding-alert.mdx";
Added
-
New Meeting and Webinar webhook events:
-
meeting.participant_role_changed -
webinar.participant_role_changed -
meeting.participant_feedback -
webinar.participant_feedback
-
-
New Chat APIs:
-
POST /chat/users/{userId}/messages/files -
POST /chat/users/{userId}/files
-
-
New Workspace API:
GET /v2/workspaces/usage
Enhancements
-
New virtual_background_id request field in the following Meeting API:
POST /v2/webinars/{webinarId}/panelists
-
New virtual_background_id response field in the following Meeting API:
GET /v2/webinars/{webinarId}/panelists
-
New host_save_video_order request field in the following Meeting APIs:
-
POST /v2/users/{userId}/meetings -
GET /v2/meetings/{meetingId}
-
-
New host_save_video_order response field in the following Meeting APIs:
-
POST /v2/users/{userId}/meetings -
GET /v2/meetings/{meetingId}
-
-
New live answered value in response field answer in the following Webinar API:
GET /v2/report/webinars/{webinarId}/qa
-
New plan_room_connector response field in Plan Usage API:
GET /v2/accounts/{accountId}/plans/usage
-
New
rich_textandfile_idsrequest field in the Send a chat message API.POST /chat/users/{userId}/messages
-
Added support for Zoom United Pro, Business, and Enterprise plans in the Billing APIs:
-
POST /v2/accounts/{accountId}/plans/addons -
PUT /v2/accounts/{accountId}/plans/base -
PUT /v2/accounts/{accountId}/plans/addons -
PATCH /v2/accounts/{accountId}/plans/addons/status -
PATCH /v2/accounts/{accountId}/plans/base/status
-
-
New
remote_supportandnon_verbal_feedbackfields in the following Account APIs:-
GET /v2/accounts/{accountId}/settings -
PATCH /v2/accounts/{accountId}/settings -
GET /v2/accounts/{accountId}/lock_settings -
PATCH /v2/accounts/{accountId}/lock_settings
-
-
New
zoom_whiteboard,post_meeting_feedback, andwhiteboardfields in the following User APIs:-
GET /v2/users/{userId}/settings -
PATCH /v2/users/{userId}/settings
-
-
New
encryption_fingerprintfield in the following **Archiving** APIs & Webhook:-
GET /v2/archive_files -
GET /v2/past_meetings/{meetingUUID}/archive_files -
recording.archive_files_completed
-
-
New
chat_with_direct_message,action_when_archive_failed,notification_when_archiving_starts,play_voice_prompt_when_archiving_starts, andarchive_retentionfields in the following Account and Group APIs:-
GET /v2/accounts/{accountId}/settings -
PATCH /v2/accounts/{accountId}/settings -
GET - /v2/groups/{groupId}/settings
-
-
New
clusterresponse field in the following User API:GET /v2/users/{userId}
-
New
bo_mtg_idresponse field in the following Dashboard API:GET /v2/metrics/meetings/{meetingId}/participants
-
Add error message
12702-Can not access meeting/webinar a year ago.in the following Dashboard, Meeting and Report APIs:-
GET /v2/metrics/meetings/{meetingId} -
GET /v2/metrics/meetings/{meetingId}/participants -
GET /v2/metrics/meetings/{meetingId}/participants/qos -
GET /v2/metrics/meetings/{meetingId}/participants/{participantId}/qos -
GET /v2/metrics/meetings/{meetingId}/participants/qos_summary -
GET /v2/metrics/meetings/{meetingId}/participants/sharing -
GET /v2/metrics/webinars/{webinarId} -
GET /v2/metrics/webinars/{webinarId}/participants -
GET /v2/metrics/webinars/{webinarId}/participants/qos -
GET /v2/metrics/webinars/{webinarId}/participants/{participantId}/qos -
GET /v2/metrics/webinars/{webinarId}/participants/qos_summary -
GET /v2/metrics/webinars/{webinarId}/participants/sharing -
GET /v2/report/meetings/{meetingId}/participants -
GET /v2/report/meetings/{meetingId}/polls -
GET /v2/report/meetings/{meetingId} -
GET /v2/report/webinars/{webinarId}/participants -
GET /v2/report/webinars/{webinarId}/polls -
GET /v2/report/webinars/{webinarId} -
GET /v2/past_meetings/{meetingId} -
GET /v2/past_meetings/{meetingId}/polls -
GET /v2/past_meetings/{meetingId}/participants
-
Bug Fixes
-
Fixed issue where
first_nameandlast_namewere missing when updating a user by activation email in the following event:user.updated
-
Fixed issue where
sip_linkswas incorrect in the response of the following Meeting API:GET /v2/meetings/{meetingId}/invitation