# Meeting Reports API response specifies no timezone **URL:** \ **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:** 1\ **Showing post:** 2
**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")
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 --- _[View the full topic](https://devforum.zoom.us/t/meeting-reports-api-response-specifies-no-timezone/141390)._