Hi,
We are experiencing an issue where responses from the GET /metrics/meetings endpoint suddenly changed string casing, impacting our production integration.
The Issue & Evidence:
Until August 15, the endpoint preserved the original casing for identifiers (e.g., Zoom Room IDs / emails). Starting August 16, the exact same endpoint began returning these identifiers strictly in lowercase.
Example:
Zoom Room ID: aPOecmV0ROCjuZb_drakJQ
On August 15, GET /metrics/meetings returned: rooms_aPOecmV0ROCjuZb_drakJQ@antel.com.uy
On August 16, GET /metrics/meetings returned: rooms_apoecmv0rocjuzb_drakjq@antel.com.uy
Note: In contrast, GET /rooms continues to return the ID preserving the original mixed case (aPOecmV0ROCjuZb_drakJQ).
We reviewed the Zoom Developer Changelog and could not find any published update or announcement regarding this modification.
Our Question:
Is this an unintended regression / bug on Zoom’s side that will be hotfixed back to preserving the original casing, or is this a permanent change to the response schema?
We need to clarify this as soon as possible, as modifying our application logic to force lowercasing could cause another bug later on if Zoom rolls back.
Support Ticket Ref: TS2414554
Thanks in advance for your help!