Driftwatch

Zoom / Zoom Meetings API /

Breakingdirection flip: their tools call this safe

creation_source can now return "zoom_scheduler"

What changed

Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.

Affects creation_source on GET /meetings/{meetingId}.

New value: zoom_scheduler.

can now return "zoom_scheduler"

Who is affected

Code that reads GET /meetings/{meetingId} (creation_source).

Before and after

WhereBeforeAfter
GET /meetings/{meetingId} · creation_source"open_api", "other", "web_portal""open_api", "other", "web_portal", "zoom_scheduler"
POST /users/{userId}/meetings · creation_source"open_api", "other", "web_portal""open_api", "other", "web_portal", "zoom_scheduler"

Code that breaks

switch (response.creation_source) {
  // existing branches …
  // no branch for "zoom_scheduler"
  default:
    throw new Error("unexpected creation_source");
}

Based on Zoom’s published API specification. How severity is decided.