How to obtain the root call log id?

Phone
1

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?

1 Like
2

@ojus.zoom ? @elisa.zoom ?

3

Hi @jose ,

Can you please link the documentation for this endpoint? I only see this one: Zoom Phone API

GET /phone/call_logs/{callLogId}

5

If you are asking for the documentation for this endpoint: https://api.zoom.us/v2/phone/call_logs/7322148181435023686/recordings
is this:

6

I updated the last post

7

Hi @jose ,

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

Can you please share that documentation?

8

Here:
Understand Zoom Phone call history

and here:

Zoom Phone call log deprecation

9

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

10

Hi @jose ,

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

11

Waiting to hear back.

12

Thanks, let me know, I am waiting the update

13

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

14

I am having the same issue.

1 Like
15

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

Please review this doc again in detail: Understand Zoom Phone call history

16

/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.

1 Like
17

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.

18

Hi @sam8 @jose ,

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

19

Followed up internally on this.

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!

2 Likes
21

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

1 Like