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 APIand look at the activity_time field in one of those records to see that there is no timestamp specification.
The Get a meeting activities report endpoint returns activity_time as a string with no timezone/offset (see the activity_time example in the official 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). 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 (the response includes a timezone field per ZoomMeetingAPI-spec.json) and apply that zone when converting activity_time. This keeps output consistent for hosts across multiple timezones
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.