# Call History (Call Path) API Not Working - Call Log Does Not Exist

**URL:** <https://devforum.zoom.us/t/call-history-call-path-api-not-working-call-log-does-not-exist/108686>\
**Category:** Phone\
**Tags:** phone, api\
**Created:** [April 25, 2024, 7:37pm UTC](https://devforum.zoom.us/t/call-history-call-path-api-not-working-call-log-does-not-exist/108686 "2024-04-25T19:37:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![joeyharrington](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@joeyharrington](https://devforum.zoom.us/u/joeyharrington)\
**Post date:** [April 25, 2024, 7:37pm UTC](https://devforum.zoom.us/t/call-history-call-path-api-not-working-call-log-does-not-exist/108686/1 "2024-04-25T19:37:01Z")

</div>

Through call recording completed webhooks, I get data on call records, including call log ID.

I want to get the call path using 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

GET /phone/call\_history/{callLogId}

I have tried with call ID or call log ID, call queue calls and non-call queue calls. Every time I get:  
{“code”:404,“message”:“Call Log does not exist: yirJUrWSRLSDr2Z\_aPII2A”}

As an example:  
call\_id = ‘7361866866473764345’  
call\_log\_id = ‘44f54a03-24a7-4922-9c90-afec6bdb3cbd’

x-zm-trackingid: WEB\_b35c8013e513d506d7ec28a3d1b9260d

I confirmed I have phone:read:call\_log:admin within my granular scopes.

My issue seems similar to the topic below, but there is no resolution included and it is marked as closed.

> [@Get call path returning code 404 "Call log does not exist: "](https://devforum.zoom.us/t/get-call-path-returning-code-404-call-log-does-not-exist/100578):
>
> I’m trying to get call path information for a call log. When calling… [https://api.zoom.us/v2/phone/call\_history/{callLogId}](https://api.zoom.us/v2/phone/call_history/%7BcallLogId%7D) with a valid call log id that I get from [https://api.zoom.us/v2/phone/call\_logs](https://api.zoom.us/v2/phone/call_logs) I get the following error. { “code”: 404, “message”: "Call Log does not exist: " }

---

<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:** [May 8, 2024, 2:40pm UTC](https://devforum.zoom.us/t/call-history-call-path-api-not-working-call-log-does-not-exist/108686/2 "2024-05-08T14:40:17Z")

</div>

Hi @joeyharrington ,

Are you looking for the root call log? Is it pertaining to behavior described here?

> [@How to obtain the root call log id?](https://devforum.zoom.us/t/how-to-obtain-the-root-call-log-id/101525/20):
>
> 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:** ![joeyharrington](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@joeyharrington](https://devforum.zoom.us/u/joeyharrington)\
**Post date:** [May 8, 2024, 3:51pm UTC](https://devforum.zoom.us/t/call-history-call-path-api-not-working-call-log-does-not-exist/108686/4 "2024-05-08T15:51:20Z")

</div>

Hi @gianni.zoom, yes it is similar. I don’t see resolution on that forum post either, is that correct?

---

<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:** [May 8, 2024, 5:25pm UTC](https://devforum.zoom.us/t/call-history-call-path-api-not-working-call-log-does-not-exist/108686/5 "2024-05-08T17:25:49Z")

</div>

@joeyharrington , in that thread you’ll see I initiated a feature request to the platform product manager to get the root call id.

---

<div class="post-metadata">

**Author:** ![preston.baxter](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/preston.baxter/32/59822_2.png) [@preston.baxter](https://devforum.zoom.us/u/preston.baxter)\
**Post date:** [May 17, 2024, 4:05pm UTC](https://devforum.zoom.us/t/call-history-call-path-api-not-working-call-log-does-not-exist/108686/6 "2024-05-17T16:05:44Z")

</div>

The problem is the 404 is had on both the UUID and the numerical ID @gianni.zoom . I too have the same problem.

```auto
curl -X GET "https://api.zoom.us/v2/phone/call_history/4ea6ca0b-20f4-429f-a083-6bb311125c87" -H "Authorization: bearer $TOKEN"
{"code":404,"message":"Call Log does not exist: ZNsKBjCGRF6K5BnpOy84yg"}

```

Using the endpoint as intended also does not work

---

<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:** [May 21, 2024, 7:15pm UTC](https://devforum.zoom.us/t/call-history-call-path-api-not-working-call-log-does-not-exist/108686/7 "2024-05-21T19:15:32Z")

</div>

Hi @preston.baxter this sounds like a bug, can you please submit a support ticket for a bug?