Call Log not found

Hi, I am using the call-id (not the log id) to download the call log once I receive any of the call log completed events.
Sometimes, after receiving the event and using the call log API to request the call log details, I receive a 400/404 (not found) with the following message: Call log information was not found. Even after a few minutes, the log is not found.
To verify, I searched for the same call-id in the admin site, and I can see it. Why is this happening?

Here is a real example of what I mean, A thing note, The response code should be 404, not 400.

http GET authorization:'Bearer ...'

HTTP/1.1 400 Bad Request
CF-Cache-Status: DYNAMIC
CF-RAY: 827ab6fb4a35feb6-IAH
Connection: keep-alive
Content-Length: 60
Content-Type: application/json
Date: Fri, 17 Nov 2023 20:27:30 GMT
NEL: {"success_fraction":0.01,"report_to":"cf-nel","max_age":604800}
Report-To: {"endpoints":[{"url":"https:\/\/\/report\/v3?s=40Xu8BS0sHIDgTK%2F40TLyn1dccFv9UR5cSk5%2Byw%2Bo5TxbDOMn5pE5wk2B7oVv1ajPu3y7%2BAGYvfGGDyc0dfrZuqsiFpMi826iSlUmNeBVJu%2FtWYYKu8Hq1LC14Y0tcD0DasUX5p02gmA"}],"group":"cf-nel","max_age":604800}
Server: cloudflare
Set-Cookie: __cf_bm=8lNJaRIwgGUfmM6fHqdUIej39F6oUPAERXMfxNzqxvA-1700252850-0-AS/s1d7VSIrxIFkhAbn1YlM3M5cHsBKboxOpmgRHsfIIA9Z1QWsopYVb/PRZc8EGTLEbg7kVqc42RpwDYN9KhxA=; path=/; expires=Fri, 17-Nov-23 20:57:30 GMT;; HttpOnly; Secure; SameSite=None
alt-svc: h3=":443"; ma=86400
strict-transport-security: max-age=31536000; includeSubDomains, max-age=31536000; includeSubDomains
vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers
x-frame-options: deny
x-zm-region: VA2
x-zm-trackingid: WEB_46cf02bd153512f1a3ad9088eddbb584

    "code": 404,
    "message": "Call log information was not found."

Is there anyone from support here? @elisa.zoom ?

Hey @jose
Thanks for reaching out
This is a known bug in our end and we are planning on fixing this in our December release.

I have done some testing on my end what I did is that I subscribes to the event recording.completed and you will be getting a call_log_id field in the payload that then you can potentially use to make your API call.

Yes, but I cannot rely on this. What about the cases where the call was not recorded?

PS: Is there any way I can send a private message to dev/support?

You can reach out to support here: Home - Zoom Support

Any update on this, this is kind of unacceptable, here is another example of a request for a call log using a call id (7312560981205600300_1) and I am still getting a 400 error. When you search for that call in the log reports, it is there!

and here the content:

  "message":"Call Log does not exist: 7312560981205600300_1"

I will go ahead and send you a private message for more information about your account and will create a support ticket on your behalf @jose please reply in the DM

What was the resolution here @elisa.zoom ? I’m also facing Call Log does not exist 404 errors for verified call IDs/call log IDs

My issue accessing phone call history seems similar to:

But there is no resolution there either.


@jose do you recall the resolution here?

No, definitely no; it’s not always happening, but it is still happening. The last time I saw this issue was on 2024-04-26 with this call id: 7362220750303429114 for account id: XXXYYYZZZZ

I have this same exact issue. Whether I am using call_id or the call_log_id. Its incredibly frustrating there appears to be a solution but it is locked behind a private DM / support ticket.

curl -X GET "" -H "Authorization: bearer $TOKEN"
{"code":404,"message":"Call Log does not exist: ZNsKBjCGRF6K5BnpOy84yg"}

curl -X GET "" -H "Authorization: bearer $TOKEN"
{"code":404,"message":"Call Log does not exist: ZNsKBjCGRF6K5BnpOy84yg"}

I tried to open a support ticket and it promptly got closed and I was told to come to the dev forums.

@elisa.zoom Is there a known solution to this problem? If so what is it?

Hi @preston.baxter
Hope you are doing great! I am coming back from a leave that I took.
I am wondering if you are still having this issue.
I am happy to look further into this