# Phone call not in expected result when using time\_type parameter

**URL:** <https://devforum.zoom.us/t/phone-call-not-in-expected-result-when-using-time-type-parameter/138226>\
**Category:** API and Webhooks\
**Tags:** phone, api\
**Created:** [October 23, 2025, 2:50pm UTC](https://devforum.zoom.us/t/phone-call-not-in-expected-result-when-using-time-type-parameter/138226 "2025-10-23T14:50:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tom\_mf](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tom_mf/32/71887_2.png) [@tom\_mf](https://devforum.zoom.us/u/tom_mf)\
**Post date:** [October 23, 2025, 2:50pm UTC](https://devforum.zoom.us/t/phone-call-not-in-expected-result-when-using-time-type-parameter/138226/1 "2025-10-23T14:50:11Z")

</div>

Hey there! I had a question about a phone call I’m trying to retrieve, specifically around the use of the `time_type` parameter.

**API Endpoint(s) and/or Zoom API Event(s)**  
I’m using `https://api.zoom.us/v2/phone/call_logs`

Below is a curl (minus tokens/etc. for security):

```auto
curl --request GET \
  --url 'https://api.zoom.us/v2/phone/call_logs?from=2025-08-25T14%3A10%3A00Z&to=2025-08-25T15%3A00%3A00Z&page_size=100&time_type=endTime' \
  --header 'Authorization: Bearer <removed_for_security>' \
  --cookie 'cred=<removed>; _zm_mtk_guid=<removed>'

```

**Description**  
I’m hoping to receive a particular call using the `time_type=end_time` parameter. The reason this parameter is important is because my app requests all calls ended in the last 5 minutes, every 5 minutes.

Using call start time will mean that if a call is still in progress, it won’t be returned in the result and hence will be missed by my 5-min requests.

This particular call isn’t being returned with the `time_type` parameter set on the expected date. Here’s the information on the call:

- without `time_type=end_time`: The reported call time is `2025-08-25T14:18:13Z`
- the call’s duration is 1504 seconds. Logically this means the call end time should be roughly `14:42:16`
- adding the parameter and searching even for 5 minutes around this timestamp (using the curl above), the call isn’t returned.

My question is - is there something else at play that could prevent a call from appearing in the result? I’m ensuring I’m not hitting a 100 page limit, and if I check a date range of a couple of hours around this timestamp using the `time_type`, I still don’t get this call.

The person who logged this call is in an AEST timezone - I’m wondering if this may have something to do with the issue.

Any insight would be appreciated. Thanks! 🙂

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [October 27, 2025, 4:51pm UTC](https://devforum.zoom.us/t/phone-call-not-in-expected-result-when-using-time-type-parameter/138226/2 "2025-10-27T16:51:14Z")

</div>

Hi @tom_mf  
Thanks for reaching out to us! I am happy to help here.  
Could you please try using the Get account’s call history endpoint here: [Phone APIs](https://developers.zoom.us/docs/api/phone/#tag/call-logs/get/phone/call_history)

By your request URL, it seems like you are using the deprecated [Get account’s call logs](https://developers.zoom.us/docs/api/phone/#tag/call-logs/get/phone/call_logs) endpoint.

I would suggest you to use the Get account’s call history endpoint and try again. This is a newer endpoint and offers more details and granularity into the data you are receiving.  
Could you please try again and let me know if this endpoint retunrs the data you are looking to receive?

Thanks

---

<div class="post-metadata">

**Author:** ![tom\_mf](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tom_mf/32/71887_2.png) [@tom\_mf](https://devforum.zoom.us/u/tom_mf)\
**Post date:** [October 29, 2025, 10:39am UTC](https://devforum.zoom.us/t/phone-call-not-in-expected-result-when-using-time-type-parameter/138226/3 "2025-10-29T10:39:28Z")

</div>

Hey Elisa!

Thanks so much for the info. I was able to find the call in question by end time using the modern endpoint. I’ll see about updating my app to use this instead!

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [October 29, 2025, 3:30pm UTC](https://devforum.zoom.us/t/phone-call-not-in-expected-result-when-using-time-type-parameter/138226/4 "2025-10-29T15:30:32Z")

</div>

Amazing news @tom_mf  
Please make sure to use the call\_history endpoints and the call\_history object returned in that response.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [November 2, 2026, 11:10am UTC](https://devforum.zoom.us/t/phone-call-not-in-expected-result-when-using-time-type-parameter/138226/6 "2026-11-02T11:10:02Z")

</div>

Closed on November 2, 2026, 11:10am UTC

This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.