Backwards Incompatible V2 API Changes

Summary

Following the removal of Zoom's Attention Tracking feature, backwards-incompatible modifications were introduced to the V2 REST API effective April 3, 2020. Under these deprecations, the attentiveness_score field in meeting and webinar participant reports returns an empty value, while the attention_tracking field across user, group, and account settings endpoints defaults to false. Both attention-tracking fields remain temporarily in API responses before full removal in a future release. Additionally, starting April 12, 2020, password-related configuration fields become immutable and permanently set to true for Free and single-host Pro K-12 Education accounts. These locking measures affect settings such as password requirements for scheduled, instant, or personal meetings, alongside PSTN password protection across account, group, and user endpoints.

Takeaways

1. 1

   Participant report APIs for meetings and webinars return empty values for the attentiveness_score field instead of active tracking data.

2. 2

   Account, group, and user settings endpoints return false for the attention_tracking field until both attention fields are fully removed in a future release.

3. 3

   Password settings, including require_password_for_scheduling_new_meetings, require_password_for_instant_meetings, and pstn_password_protected, are immutable and locked to true for single-host Pro and Free K-12 Education accounts.