Migrate Zoom Phone Call Log APIs to Call History
In December 2023, Zoom Phone API introduced new endpoints that replace the legacy call logs system, which will be fully deprecated in April 2026.
The Get account's call history API provides comprehensive summaries of all inbound and outbound calls across your account. It's available to administrators through account-level OAuth apps with the required scopes.
For deeper analysis, the Get call path API complements the call history endpoint by returning granular call path logs. Based on developer feedback, Zoom has enhanced these endpoints and introduced improved Call History APIs for greater clarity, consistency, and flexibility.
Recent changes to call history endpoints
Get account's call history
Replaces the existing call_log array with a new call_history array.
The call_history object includes:
call_history_uuidcall_id
The call_log array deprecation occurs November 2026.
Get call history
Replaces the existing call_path array with a new call_elements array.
The Get call path endpoint has been renamed for improved clarity and consistency.
The call_elements object includes:
call_idcall_element_id
The call_path array deprecation occurs November 2026.
Note: If you've already migrated to the Get call path API, you don't need to take any immediate action. We updated the API based on developer feedback to improve clarity and consistency.
Endpoint
GET /phone/call_history/{call_history_uuid}
Response example
{
"call_id": "7018317023722949162",
"call_history_uuid": "20211008-48c1dfd4-91ce-4df5-8495-7c9e33d10869",
"call_elements": [
{
"call_element_id": "48c1dfd4-91ce-4df5-8495-7c9e33d10869",
"call_id": "7018317023722949162"
}
]
}
This endpoint returns detailed call path information, including a call_elements array that lists all components of the call.
Get call element
Replaces the previous Get call history detail endpoint.
Note: If you've already migrated to the Get call history detail API, you don't need to take any action now.
Endpoint
GET /phone/call_element/{call_element_id}
This endpoint returns detailed information about a specific call element or segment, including:
call_element_idcall_idcall_history_uuid
API version mapping
Here is a mapping of previous endpoints to new endpoints.
Action required
- If you're still using Legacy Call Logs (v1), migrate to v3 immediately.
- If you're already using v2, migration is optional but recommended for consistency.
- Legacy Call Logs API (v1, deprecated) will be fully deprecated in April 2026.
| Legacy Call Logs API (v1, deprecated) | Call History API (v2, 2023) | Call History Enhancement (v3, 2025) | Key changes |
|---|---|---|---|
GET /phone/call_logs | GET /phone/call_history | GET /phone/call_history | Introduces call_history object with call_history_uuid (replaces id). |
GET /phone/call_logs/{callLogId} | GET /phone/call_history/{callLogId} | GET /phone/call_history/{call_history_uuid} | Introduces call_elements object to display different elements of a call (replacing call_path). |
| (No legacy equivalent) | GET /phone/call_history_detail/{callHistoryId} | GET /phone/call_element/{call_element_id} | New endpoint for retrieving detailed call element data with improved naming conventions. |
How to migrate
- Identify the legacy Call Logs API endpoints your app uses.
- Match each endpoint to its new replacement.
- Update your request paths and parameters with the new field names (for example,
idtocall_history_uuid). - Map old response fields to the new response structure (for example
call_logstocall_historyobject). - Test the new endpoints in a staging environment before deploying to production.