# How to obtain the root call log id?

**URL:** <https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525>\
**Category:** Phone\
**Created:** [January 9, 2024, 11:59pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525 "2024-01-09T23:59:40Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jose](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose/32/52765_2.png) [@jose](https://devforum.zoom.us/u/jose)\
**Post date:** [January 9, 2024, 11:59pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/1 "2024-01-09T23:59:40Z")

</div>

I use the following events to know when the call finishes: `phone.callee_call_log_completed` and` phone.caller_call_log_completed`, but these contain only the log ids for either the caller or callee.

I need to download the call details/path to analyze the whole call. With this endpoint: `/phone/call_logs/{callId}` I can use the call id in order to get the call details, but the documentation says it will be deprecated in 2025, in favor of this endpoint: `/phone/call_history/{callLogId}`, but with this one, I cannot use the call id, neither the log id coming in any of these events, I have to use the root log id.

How do I get it if there is no general event (like `phone.call_log_completed`) with that information?

---

<div class="post-metadata">

**Author:** ![jose](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose/32/52765_2.png) [@jose](https://devforum.zoom.us/u/jose)\
**Post date:** [January 10, 2024, 7:37pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/2 "2024-01-10T19:37:13Z")

</div>

@ojus.zoom ? @elisa.zoom ?

---

<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:** [January 10, 2024, 9:54pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/3 "2024-01-10T21:54:20Z")

</div>

> [@jose](#):
>
> I need to download the call details/path to analyze the whole call. With this endpoint: `/phone/call_logs/{callId}` I can use the call id in order to get the call details, but the documentation says it will be deprecated in 2025,

Hi @jose ,

Can you please link the documentation for this endpoint? I only see this one: [Zoom Phone API](https://developers.zoom.us/docs/api/rest/reference/phone/methods/#operation/getCallLogDetails)

`GET /phone/call_logs/{callLogId}`

---

<div class="post-metadata">

**Author:** ![jose](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose/32/52765_2.png) [@jose](https://devforum.zoom.us/u/jose)\
**Post date:** [January 10, 2024, 10:08pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/5 "2024-01-10T22:08:50Z")

</div>

If you are asking for the documentation for this endpoint: [https://api.zoom.us/v2/phone/call\_logs/7322148181435023686/recordings](https://api.zoom.us/v2/phone/call_logs/7322148181435023686/recordings)  
is this:

> **[Zoom Phone API](https://developers.zoom.us/docs/api/rest/reference/phone/methods/#operation/getCallPath)**
>
> API Reference for /docs/api/rest/reference/phone/methods

---

<div class="post-metadata">

**Author:** ![jose](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose/32/52765_2.png) [@jose](https://devforum.zoom.us/u/jose)\
**Post date:** [January 10, 2024, 10:11pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/6 "2024-01-10T22:11:34Z")

</div>

I updated the last post

---

<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:** [January 10, 2024, 10:17pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/7 "2024-01-10T22:17:37Z")

</div>

Hi @jose ,

Nevermind, I misread. Where did you see it say this will be deprecated in 2025:

> **[Zoom Phone API](https://developers.zoom.us/docs/api/rest/reference/phone/methods/#operation/getCallLogDetails)**
>
> API Reference for /docs/api/rest/reference/phone/methods

Can you please share that documentation?

---

<div class="post-metadata">

**Author:** ![jose](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose/32/52765_2.png) [@jose](https://devforum.zoom.us/u/jose)\
**Post date:** [January 10, 2024, 10:21pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/8 "2024-01-10T22:21:09Z")

</div>

Here:  
[Understand Zoom Phone call history](https://developers.zoom.us/docs/zoom-phone/understanding-call-history/)

and here:

[Zoom Phone call log deprecation](https://developers.zoom.us/changelog/zoom-phone/december-19-2023/)

---

<div class="post-metadata">

**Author:** ![jose](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose/32/52765_2.png) [@jose](https://devforum.zoom.us/u/jose)\
**Post date:** [January 10, 2024, 10:24pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/9 "2024-01-10T22:24:28Z")

</div>

If Zoom will deprecate some functionality, we expect the new one will have the same features, at least.

---

<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:** [January 10, 2024, 10:25pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/10 "2024-01-10T22:25:29Z")

</div>

Hi @jose ,

Thanks for sharing this! I will inquire further and get back to you.

---

<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:** [January 12, 2024, 9:37pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/11 "2024-01-12T21:37:58Z")

</div>

Waiting to hear back.

---

<div class="post-metadata">

**Author:** ![jose](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose/32/52765_2.png) [@jose](https://devforum.zoom.us/u/jose)\
**Post date:** [January 12, 2024, 10:36pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/12 "2024-01-12T22:36:45Z")

</div>

Thanks, let me know, I am waiting the update

---

<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:** [January 16, 2024, 6:39pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/13 "2024-01-16T18:39:17Z")

</div>

Still haven’t heard back, but just followed up.

---

<div class="post-metadata">

**Author:** ![sam8](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sam8/32/63400_2.png) [@sam8](https://devforum.zoom.us/u/sam8)\
**Post date:** [January 19, 2024, 3:42pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/14 "2024-01-19T15:42:28Z")

</div>

I am having the same issue.

---

<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:** [January 19, 2024, 4:43pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/15 "2024-01-19T16:43:14Z")

</div>

Hi @sam8 @jose, ae you able to verify if call path shows multiple call ids including the root call id?

> **[Zoom Phone API](https://developers.zoom.us/docs/api/rest/reference/phone/methods/#operation/getCallPath)**
>
> API Reference for /docs/api/rest/reference/phone/methods

Please review this doc again in detail: [Understand Zoom Phone call history](https://developers.zoom.us/docs/zoom-phone/understanding-call-history/)

---

<div class="post-metadata">

**Author:** ![sam8](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sam8/32/63400_2.png) [@sam8](https://devforum.zoom.us/u/sam8)\
**Post date:** [January 19, 2024, 8:52pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/16 "2024-01-19T20:52:27Z")

</div>

/phone/call\_logs/{callId} works fine when the callId input is taken from phone.caller\_call\_log\_completed or phone.callee\_call\_log\_completed.

/phone/call\_history/{callLogId} gets 400 error when the input ‘id’ (e.g. 4a4ed8ec-6be4-4e42-96e6-352a4396204d) is taken from those hooks. So there’s no way to see the callpath payload.

---

<div class="post-metadata">

**Author:** ![jose](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jose/32/52765_2.png) [@jose](https://devforum.zoom.us/u/jose)\
**Post date:** [January 19, 2024, 11:05pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/17 "2024-01-19T23:05:17Z")

</div>

That is correct. We cannot use the `callId` to get the call history using this endpoint:

`/phone/call_history/{callLogId}`

which is being promoted instead of this one:

`/phone/call_logs/{callId}`

Also, the `call-id` is more useful than the call log IDs. There is one `call-log-id` per call leg and one per root call. The `call-id` can at least be used up to a point to get all info about the call, and I said up to a point because you have to do some magic (events out of order, info missing in the call log details, etc.) in order to link one call to the other.

---

<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:** [January 22, 2024, 3:57pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/18 "2024-01-22T15:57:43Z")

</div>

Hi @sam8 @jose ,

Ahh I see. I have shared your thoughts with the phone API development team.

---

<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:** [March 6, 2024, 6:46pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/19 "2024-03-06T18:46:23Z")

</div>

Followed up internally on this.

---

<div class="post-metadata">

**Author:** ![ddesimone](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ddesimone/32/58457_2.png) [@ddesimone](https://devforum.zoom.us/u/ddesimone)\
**Post date:** [April 8, 2024, 6:35pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/20 "2024-04-08T18:35:25Z")

</div>

Hi - I just wanted to **+1** this issue as we have implemented the same type of workflow Jose has mentioned above and are experiencing the same problem.

It appears the only ID this endpoint accepts is the one returned in the results of  
the batch `/phone/call_history` call (“get account’s call history”). We really need the `/phone/call_history/{callLogId}` endpoint to accept the long, numerical **call\_id** like the now-deprecated endpoint did in order to migrate over.

Thanks!

---

<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:** [April 15, 2024, 8:00pm UTC](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/21 "2024-04-15T20:00:48Z")

</div>

Thank you @ddesimone , I am escalating this further and will share an internal reference number for me to track progress on this.

[Next page](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525.md?page=2)
