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.
Request:
http GET https://api.zoom.us/v2/phone/call_logs/7302523702765436703 authorization:'Bearer ...'
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.
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!
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
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 "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"}
curl -X GET "https://api.zoom.us/v2/phone/call_history/7369726188412440168" -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