# Acceptable Timezones for API missing Toronto

**URL:** <https://devforum.zoom.us/t/acceptable-timezones-for-api-missing-toronto/39096>\
**Category:** API and Webhooks\
**Created:** [December 23, 2020, 6:40pm UTC](https://devforum.zoom.us/t/acceptable-timezones-for-api-missing-toronto/39096 "2020-12-23T18:40:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![reg.charney\_zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/reg.charney_zoom/32/20581_2.png) [@reg.charney\_zoom](https://devforum.zoom.us/u/reg.charney_zoom)\
**Post date:** [December 23, 2020, 6:40pm UTC](https://devforum.zoom.us/t/acceptable-timezones-for-api-missing-toronto/39096/1 "2020-12-23T18:40:02Z")

</div>

**Description**  
When using the API or Zoom Website to set a User’s or Meetings Timezone there is no entry that matches Toronto. There are though entries for Winnipeg, Vancouver & Saskatchewan.

Since my client application is getting its User Timezone from the devices timezone selection I am forced to maintain a lookup reference to cover these anomalies. If I may ask what was the rational for maintaining a non-standard list of Timezone ID’s?

**Error**  
Cannot select America/Toronto as timezone

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
ALL

**Which Endpoint/s?**  
ALL

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [December 28, 2020, 5:52pm UTC](https://devforum.zoom.us/t/acceptable-timezones-for-api-missing-toronto/39096/2 "2020-12-28T17:52:39Z")

</div>

Hi @reg.charney_zoom,

Thank you for pointing this out, and you raise a great point. Our team will consider adding this—in the meantime, you might also consider using the GMT offset to designate the appropriate time as well. See this post here:

> [@Timezone list with GMT offset](https://devforum.zoom.us/t/timezone-list-with-gmt-offset/7539/4):
>
> Hey @adamwang, Thanks for your feedback. We will consider adding this. In the meantime you can calculate the offset on your end if the Z is including in the [start\_time for example](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate). That means it is in GMT time. Then you can use a method like [JavaScripts getTimezoneOffset()](https://www.w3schools.com/jsref/jsref_gettimezoneoffset.asp). Thanks, Tommy

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [January 28, 2021, 3:52am UTC](https://devforum.zoom.us/t/acceptable-timezones-for-api-missing-toronto/39096/3 "2021-01-28T03:52:45Z")

</div>

Closed on January 28, 2021, 3:52am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.