# Backwards Incompatible V2 API Changes

DevFeed: [Backwards Incompatible V2 API Changes](<https://devfeed.tech/articles/backwards-incompatible-v2-api-changes-24759.md>)

Original publisher: [Read original article](<https://medium.com/zoom-developer-blog/backwards-incompatible-v2-api-changes-a0a97df9c306?source=rss----4a85731adaff---4>)

Author: Benjamin Dean

Published: 2020-04-03T00:20:55Z

Content type: release

Language: en

Sources: [Zoom Developer Blog - Medium](<https://devfeed.tech/sources/zoom-developer-blog-medium.md>)

Topics: [REST API](<https://devfeed.tech/topics/rest-api.md>), [zoom](<https://devfeed.tech/topics/zoom.md>), [API](<https://devfeed.tech/topics/api.md>), [passwords](<https://devfeed.tech/topics/passwords.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [developer](<https://devfeed.tech/tags/developer.md>), [marketplaces](<https://devfeed.tech/tags/marketplaces.md>), [password](<https://devfeed.tech/tags/password.md>), [release](<https://devfeed.tech/tags/release.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [zoom](<https://devfeed.tech/tags/zoom.md>)

## AI overview

Zoom announces backwards-incompatible V2 REST API changes following the removal of Attention Tracking. The affected fields return empty or false values, and some password-related settings become immutable for certain K-12 Education accounts.

## Source excerpt

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: 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