Backwards Incompatible V2 API Changes

In accordance with the removal of the Attention Tracking feature in Zoom, we have made the following breaking changes to the V2 REST API effective upon the release April 3rd, 2020:

1. Deprecating “attentiveness_score” field in Meeting, Webinar Participants Report APIs. The API Responses to your requests on the following APIs will always return an empty value for the (“attentiveness_score”) field.

• GET /v2/report/meetings/{meetingId}/participants
• GET /v2/report/webinars/{webinarId}/participants

2. Deprecating “attention_tracking” field in User, Group, and Account APIs. The API Responses to your GET requests on the following APIs will always return a “false” value.

• GET /v2/accounts/{accountId}/settings
• PATCH /v2/accounts/{accountId}/settings
• GET /v2/accounts/{accountId}/lock_settings
• PATCH /v2/accounts/{accountId}/lock_settings
• GET /v2/groups/{groupId}/settings
• PATCH /v2/groups/{groupId}/settings
• GET /v2/groups/{groupId}/lock_settings
• PATCH /v2/groups/{groupId}/lock_settings
• GET /v2/users/{userId}/settings
• PATCH /v2/users/{userId}/settings

We will continue to present the fields listed above in the API responses for the time being, but responses for these fields will return either an empty value or “false”, as indicated above.

In a TBD future release, we will remove these two fields entirely.

3. Beginning April 12th, 2020, password-related settings can no longer be modified (immutable, always returning TRUE) for K-12 Education accounts that are Free or Pro (single host).

These password-related settings are enabled by default, and can be changed by the owner/admin on: free accounts, or Pro accounts (with only one single host license).
NOTE: Free Accounts with CC are permitted to adjust this setting.

The above changes are relevant for the following fields of the given APIs:

The “require_password_for_scheduling_new_meetings” field,
“require_password_for_instant_meetings” field, and
”require_password_for_pmi_meetings”) field on these APIs:

• GET /v2/accounts/{accountId}/settings
• PATCH /v2/accounts/{accountId}/settings
• GET /v2/accounts/{accountId}/lock_settings
• PATCH /v2/accounts/{accountId}/lock_settings
• GET /v2/groups/{groupId}/settings
• PATCH /v2/groups/{groupId}/settings
• GET /v2/groups/{groupId}/lock_settings
• PATCH /v2/groups/{groupId}/lock_settings
• GET /v2/users/{userId}/settings
• PATCH /v2/users/{userId}/settings

The “pstn_password_protected” field on these APIs:

• GET /v2/groups/{groupId}/settings
• PATCH /v2/groups/{groupId}/settings
• GET /v2/groups/{groupId}/lock_settings
• PATCH /v2/groups/{groupId}/lock_settings
• GET /v2/users/{userId}/settings
• PATCH /v2/users/{userId}/settings

The “pmi_password” field on these APIs:

• GET /v2/users/{userId}/settings
• PATCH /v2/users/{userId}/settings

To view, or subscribe, to any additional changes on the Zoom Developer Platform, please use this developer forum post: https://devforum.zoom.us/t/developer-impacting-changes-during-covid-19/8930