According to a recent email and captured here: Call History API migration
phone.callee_call_history_completed
phone.caller_call_history_completed
are listed under deprecated webhooks.
But until recently, those were the webhooks that were replacing the call log webhooks, see here:
We used call history to replace call log webhooks per the above guidance and now we need to change them again?
Hi @joeyharrington
Thanks for reaching out to us!
Great question — happy to clarify.
You’re correct that the phone.callee_call_history_completed and phone.caller_call_history_completed events were initially introduced to replace the legacy call log webhooks.
Based on developer feedback, we made further improvements to both the events and related endpoints, and more recently introduced phone.callee_call_element_completed and phone.caller_call_element_completed. These newer events now replace both the call log webhooks and the call history webhooks.
If you have already migrated to the call history webhooks, no immediate action is required — we will continue supporting them through the end of next year. However, we strongly recommend migrating to the new call element webhooks to take advantage of the latest improvements.
At this time, the only webhooks being deprecated and sunset are the call log webhooks.
Please let me know if you have any questions or if you’d like help with the migration!
Here is a helpful guide: Migrate Zoom Phone call logs APIs to call history
Thanks for the clarification. The extra 7 months are appreciated.
I forgot to mention @joeyharrington
The webhook payload is pretty much the same, it is just the name what changed and we added one field “call_element_ids”. Other than that the data is the same, so you would only have to update the name of the events in your integration the call_element_ids that replaces the “call_logs_id” in the call_history webhooks, and of course add the new events in your application