Enhancements

  • Added a new field(“meeting_authentication”) in the payload of User Settings Updated webhook.

    • user.settings_updated
  • Added new response fields(“audio_device_from_crc","audio_device_to_crc","video_device_from_crc","video_device_to_crc","as_device_from_crc","as_device_to_crc”) in the Dashboard Participants QoS APIs.

    • GET /v2/metrics/meetings/{meetingId}/participants/{participantId}/qos
    • GET /v2/metrics/webinars/{webinarId}/participants/{participantId}/qos
    • GET /v2/metrics/meetings/{meetingId}/participants/qos
    • GET /v2/metrics/webinars/{webinarId}/participants/qos
  • Added a new response field(“email”) in the List Meeting Participants API.

    • GET /v2/metrics/meetings/{meetingId}/participants
  • Added a new response field(“location_id”) in the List Zoom Rooms API.

    • GET /v2/rooms
  • Added a new response field(“pmi”) in the List User Schedulers API.List Schedulers API.

    • GET /v2/users/{userId}/schedulers
  • Added a new response field(“custom_attributes”) in the Get User Details API.

    • GET /v2/users/{userId}
  • Added a new request field(“custom_attributes”) in the Update a User API.

    • PATCH /v2/users/{userId}
  • Added a new response field(“custom_attributes”) in Get Active Host Reports API.

    • GET /v2/report/users
  • Deprecated the “page_number” field and replaced it with “next_page_token” in the Batch List APIs. Please refer to our Batch List APIs guide for details

    • GET /v2/accounts
    • GET /v2/meetings/{meetingId}/recordings/registrants
    • GET /v2/h323/devices
    • GET /v2/im/groups/{groupId}/members
    • GET /v2/users/{userId}/meetings
    • GET /v2/meetings/{meetingId}/registrants
    • GET /v2/users/{userId}/webinars
    • GET /v2/webinars/{webinarId}/registrants
  • Enabled assistants to retrieve meeting host’s settings by identifying the assistants with their OAuth token.

    • GET /v2/users/{userId}/settings
  • Added support for both User ID and User Email in the following User Level APIs. Developers are no longer required to pass the me keyword for these APIs.

    • GET /v2/users/{userId}/settings
    • PATCH /v2/users/{userId}/settings
    • PUT /v2/users/{userId}/password
    • GET /v2/users/{userId}/assistants
    • POST /v2/users/{userId}/assistants
    • DELETE /v2/users/{userId}/assistants
    • DELETE /v2/users/{userId}/assistants/{assistantId}
    • POST /v2/users/{userId}/picture
    • GET /v2/users/{userId}/token
    • DELETE /v2/users/{userId}/token
    • GET /v2/users/{userId}/permissions
    • GET /v2/users/{userId}/schedulers
    • DELETE /v2/users/{userId}/schedulers
    • DELETE /v2/users/{userId}/schedulers/{schedulerId}
    • PUT /v2/users/{userId}/email
    • GET /v2/users/{userId}/meetings
    • POST /v2/users/{userId}/meetings
    • GET /v2/users/{userId}/webinars
    • POST /v2/users/{userId}/webinars
    • GET /v2/users/{userId}/recordings

Bug Fixes

  • Fixed the bug that caused all available call-out counties to be returned in the response even when an account subscribed to the Phone base plan with only specific call-out countries.

    • POST /v2/accounts/{accountId}/plans
  • Fixed an error where a clear message was not being displayed when users tried to use expired PMI meetings.

    • POST /v2/users/{userId}/meetings
  • Fixed the bug where the value of ‘mute_upon_entry’ in the Create a Meeting API was not being inherited from the Account Settings.

    • POST /v2/users/{userId}/meetings
  • Fixed the bug where the PMI property was still being displayed when a meeting scheduled with PMI was updated to a recurring meeting with the value of “use_pmi” field set to "false".

    • PATCH /v2/meetings/{meetingId}
  • Fixed the bug that caused incorrect values to be displayed for the ‘created_at’ field in the response of the List Users API.

    • GET /v2/users
  • Fixed the bug that prevented chat messages sent by Client from being updated using the Update a Chat Message API.

    • PUT /v2/chat/users/me/messages/{messageId}
  • For the following APIs, we replaced incorrect errors with improved error messages(listed below) that will be displayed in scenarios where an account with the maximum permitted number of users, tries to add another user.

    • POST /v2/users

      • Your request to add a basic user could not be approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} basic users. Please remove existing basic user(s) from your Users list or the Pending Users list before attempting to add another user.

      • Your request to add a new {userType} user could not be approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} paying users. Please purchase additional licenses or contact the Zoom support team to provision additional users in your account.

    • PATCH /v2/users/{userId}

      • Your request to convert the user type of this {userType} user to a basic user was not approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} basic users. Please remove existing basic user(s) from your Users list or the Pending Users list before attempting to convert a paying user to a basic user.

      • Your request to convert the user type of this basic user to a {userType} user was not approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} paying users. Please purchase additional licenses or remove existing paying user(s) from your Users list or the Pending Users list before attempting to convert a basic user to a paying user.

    • PUT /v2/users/{userId}/status

      • Your request to activate the user was not approved at this time because your account has reached the permitted maximum number of {numOfAllowedUsers} basic users. Please remove existing basic user(s) from your Users list or the Pending Users list before attempting to activate this user.