# Call History Logs - Duplicate call\_id

**URL:** <https://devforum.zoom.us/t/call-history-logs-duplicate-call-id/135565>\
**Category:** Phone\
**Tags:** api\
**Created:** [July 22, 2025, 3:01pm UTC](https://devforum.zoom.us/t/call-history-logs-duplicate-call-id/135565 "2025-07-22T15:01:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kuhnm](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kuhnm/32/69799_2.png) [@kuhnm](https://devforum.zoom.us/u/kuhnm)\
**Post date:** [July 22, 2025, 3:01pm UTC](https://devforum.zoom.us/t/call-history-logs-duplicate-call-id/135565/1 "2025-07-22T15:01:10Z")

</div>

**/phone/call\_history**  
[_Link to the API endpoint documentation._](https://developers.zoom.us/docs/api/phone/#tag/call-logs/get/phone/call_history)

**Description**  
We are trying to understand the circumstances that produce call\_history records with the same call\_id. We have 70,317 out of 308,907 call\_history records where the call\_id appears more than once. The documentation for call\_id indicates that it might contain multiple “call log ID”, but we don’t understand the why this would be conceptually. Could you please provide an explanation for this behavior?

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1. Get account call history with a sufficiently large date range._  
_2. Parse the response to find examples where multiple records share the same call\_id_

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [July 25, 2025, 3:30pm UTC](https://devforum.zoom.us/t/call-history-logs-duplicate-call-id/135565/3 "2025-07-25T15:30:55Z")

</div>

Hi @kuhnm , this is a great question. This happens because there are different [call flow types](https://developers.zoom.us/docs/phone/understanding-call-logs/#get-accounts-call-logs)  
depending on how calls are routed. This means there can be a parent `call_id` with subsequent `callLogId` for the different routing paths.

The specific path or portion can be seen via get call path [Phone APIs](https://developers.zoom.us/docs/api/phone/#tag/call-logs/get/phone/call_history/%7BcallLogId%7D) :  
`/phone/call_history/{callLogId}` .

This endpoint is where you pass the `id` aka callLogId portion retrieved from `/phone/call_history`:

 ![Screenshot 2025-07-25 at 11.27.03 AM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/a/7/a7950af98fa20e9871ad0f185b7b2d563a15d933.png)

---

<div class="post-metadata">

**Author:** ![kuhnm](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kuhnm/32/69799_2.png) [@kuhnm](https://devforum.zoom.us/u/kuhnm)\
**Post date:** [July 25, 2025, 6:20pm UTC](https://devforum.zoom.us/t/call-history-logs-duplicate-call-id/135565/4 "2025-07-25T18:20:22Z")

</div>

Hi Gianni,

Thanks for the reply. I’m still not understanding why there are duplicate `call_id`s from the call\_history endpoint. Hopefully, this example from our data might help.

We have four objects in the `call_logs` array returned by the Get account’s call history endpoint that have the same `call_id`. The `callee_ext_type` and `caller_ext_type` is “user” for all four objects. The objects appear to be in pairs; each pair has the same `start_time`, caller, callee, and one of the pair has the `direction` of “inbound” while the other has the `direction of` outbound. We pass the `id` of each object to the Get call path endpoint. As shown in the summary below, these calls are not connected by this endpoint as we’d expect:

- First Pair
  - Outbound
    - One call path: result = connected

  - Inbound
    - One call path: result = answered

- Second Pair
  - Outbound
    - Two call paths: result for both = connected

  - Inbound
    - One call path: result = answered

This does not appear to match any of the documented flows. We would expect, if these calls are connected, that there would be one object from the call history endpoint and that they would be connected in the call path endpoint. However, these records are only connected by `call_id`, and we do not understand why or in what circumstances this occurs.

---

<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:** [July 31, 2025, 5:24pm UTC](https://devforum.zoom.us/t/call-history-logs-duplicate-call-id/135565/5 "2025-07-31T17:24:01Z")

</div>

Looking into this @kuhnm

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [September 16, 2025, 5:17pm UTC](https://devforum.zoom.us/t/call-history-logs-duplicate-call-id/135565/6 "2025-09-16T17:17:41Z")

</div>

@kuhnm just wanted to provide a quick update–we’re working on a bunch of updates for call history so we are reviewing if this is being accounted for.
