Timezone api meetings

I’m using the meeting api to do a schedule.
The problem is that i sending

“start_time”: “2020-03-19T17:01:00Z”,
“timezone”: “America/Sao_Paulo”,

the response is

“start_time”: “2020-03-19T17:01:00Z”,
“timezone”: “America/Sao_Paulo”,

but when i access app zoom the time is 2020-03-19 14:00

Endpoint is /users/{userId}/meetings

1 Like

image

image

Hey @comercial, thanks for posting and using Zoom!

When setting the timezone property, do not include the Z in the start_time.

https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate

Try this and let me know if it works:

"start_time": "2020-03-19T17:01:00",
"timezone": "America/Sao_Paulo",

Thanks,
Tommy

3 Likes

Hey @tommy,

the problem change, follow the screenshot:

sorry my english isn’t so good.

Hey @comercial,

The start_time in the response is always in GMT time, which is 3 hours ahead of Sao Paulo time.

Typically all server times are based on GMT, so then you can convert the GMT time to the local timezone on the client browser / device.

Thanks,
Tommy

@tommy why does it always use GMT in responses but includes the timezone that was sent in the request? This is totally confusing, IMHO timezone and the timestamp in one object should always match! You would normally use the timezone property as a baseline for converting the timestamp to local time.

Thanks for the feedback, @Paediko. While I believe the intention is that the start_time is intended to be converted to local time on the frontend, I can understand how including the timezone in the response along with GMT can be a bit confusing—I’ll be happy to share this.

Thanks,
Will