# Undocumented Zoom Phone API changes strike yet again

**URL:** <https://devforum.zoom.us/t/undocumented-zoom-phone-api-changes-strike-yet-again/144467>\
**Category:** Phone\
**Created:** [June 26, 2026, 2:15pm UTC](https://devforum.zoom.us/t/undocumented-zoom-phone-api-changes-strike-yet-again/144467 "2026-06-26T14:15:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![paul.woltman](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/paul.woltman/32/62117_2.png) [@paul.woltman](https://devforum.zoom.us/u/paul.woltman)\
**Post date:** [June 26, 2026, 2:15pm UTC](https://devforum.zoom.us/t/undocumented-zoom-phone-api-changes-strike-yet-again/144467/1 "2026-06-26T14:15:13Z")

</div>

We spent many months deciphering the completely random nature of the Zoom Phone call logs retrieved via API, and dealt with at least 3 times the structure of the phone logs changed without warning.

We have discovered that, starting on May 18th 2026, Zoom has once again changed the logging format.

Prior to 5/18/2026, “direct\_transfer” was a possible event log, indicating a direct\_transfer had happened. This was typically followed by a “incoming” log for the person receiving the direct transfer. In the same way, “warm\_transfer” was a possible event (which itself is a small nightmare to figure out, as documented in this dev forum in other posts), but has been replaced by “warm\_transfer\_incoming” and “warm\_transfer\_outgoing”.

The official documentation for the /v2/phone/call\_history API endpoint is linked here - as you can see, over a month later, and the documentation team either has no idea that the group working on the API even made a change, or they just can’t be bothered to keep the documentation current.

I’m still baffled as to the structure of the development team at Zoom - it really feels like the left hand doesn’t know what the right hand is doing when it comes to any of their APIs, webhooks, or documentation.

> **[Phone APIs - API - Zoom Developer Docs](https://developers.zoom.us/docs/api/phone/#tag/call-logs/get/phone/call_history/%7BcallHistoryUuid%7D)**
>
> You can access information from Zoom with Zoom Phone APIs to build private services or public applications on the Zoom App Marketplace.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [October 9, 2026, 5:56pm UTC](https://devforum.zoom.us/t/undocumented-zoom-phone-api-changes-strike-yet-again/144467/2 "2026-10-09T17:56:19Z")

</div>

Hi @paul.woltman  
Thanks a lot for your patience, for reaching out to us.

I completely understand your frustration and I agree with how this experience has not been ideal for customers. We are again working on improving with a new team to make sure this issue does not happen again.

I will be reaching out to you soon with an invite to meet with the PM and Engineering team so we can coordinate a call

Thanks again