Phone call not in expected result when using time_type parameter

API and Webhooks
,
1

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):

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! :slight_smile: