# Meeting Reports API response specifies no timezone

**URL:** <https://devforum.zoom.us/t/meeting-reports-api-response-specifies-no-timezone/141390>\
**Category:** Meetings\
**Created:** [January 20, 2026, 10:52pm UTC](https://devforum.zoom.us/t/meeting-reports-api-response-specifies-no-timezone/141390 "2026-01-20T22:52:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sai3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sai3/32/49425_2.png) [@Sai3](https://devforum.zoom.us/u/Sai3)\
**Post date:** [January 20, 2026, 10:52pm UTC](https://devforum.zoom.us/t/meeting-reports-api-response-specifies-no-timezone/141390/1 "2026-01-20T22:52:16Z")

</div>

### No timezone on meeting activity record’s timestamp

**API Endpoint(s) and/or Zoom API Event(s)**  
[https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/reportMeetingactivitylogs](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/reportMeetingactivitylogs)

**Description**  
_Currently the records that are returned by the zoom meeting activities report api come in with a timestamp in the `activity_time` field that have no specified timestamp. As so I am not able to determine whether or not to use a local time and what that would be, or if these timestamps are stored in UTC format._

**Error?**  
_Zoom meeting activity records have no timezone specified in their corresponding timestamps._

**How To Reproduce**  
_Simply make a request to the api endpoint described here:_ [Zoom Meeting API](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/reportMeetingactivitylogs) _and look at the `activity_time` field in one of those records to see that there is no timestamp specification._

---

<div class="post-metadata">

**Author:** ![Jer](https://avatars.discourse-cdn.com/v4/letter/j/8baadc/32.png) [@Jer](https://devforum.zoom.us/u/Jer)\
**Post date:** [January 27, 2026, 4:43am UTC](https://devforum.zoom.us/t/meeting-reports-api-response-specifies-no-timezone/141390/2 "2026-01-27T04:43:06Z")

</div>

The [`Get a meeting activities report`](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/reportMeetingactivitylogs) endpoint returns `activity_time` as a string with no timezone/offset (see the `activity_time` example in the official [`ZoomMeetingAPI-spec.json`](https://developers.zoom.us/api-specs/zoom-api/methods/ZoomMeetingAPI-spec.json)). Since it’s not an ISO-8601 `date-time` in the spec, you can’t infer the timezone from the value alone.

Zoom staff have confirmed that meeting **Dashboard/Reports** timestamps are returned in **GMT (UTC)**, so you should interpret `activity_time` as UTC and convert for display as needed ([forum confirmation](https://devforum.zoom.us/t/meeting-timezone-in-reports-dashboard/36921)). Keep the stored value in UTC and apply the viewer’s timezone when rendering.

If you need the meeting’s configured timezone, fetch it via [`List meetings`](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/meetings) (the response includes a `timezone` field per [`ZoomMeetingAPI-spec.json`](https://developers.zoom.us/api-specs/zoom-api/methods/ZoomMeetingAPI-spec.json)) and apply that zone when converting `activity_time`. This keeps output consistent for hosts across multiple timezones

---

<div class="post-metadata">

**Author:** ![Sai3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sai3/32/49425_2.png) [@Sai3](https://devforum.zoom.us/u/Sai3)\
**Post date:** [February 25, 2026, 8:55pm UTC](https://devforum.zoom.us/t/meeting-reports-api-response-specifies-no-timezone/141390/3 "2026-02-25T20:55:52Z")

</div>

Hello was just testing this out again, and it seems that timestamps are not being sent in UTC and are instead being sent in the local time when that meeting was joined. I joined a meeting at 10:22 AM PST today and thats the timestamp that was on the log, now that I assumed it was UTC my logs currently think that I was in a meeting at 2AM (pst to utc time conversion).

Is there any fix around this or do you all think you can provide the timezone on a specific timestamp. There is no way to pull logs incrementally through api, if we don’t have timezones on these timestamps.