# Nylas get availability payload confusion

**URL:** <https://forums.nylas.com/t/nylas-get-availability-payload-confusion/880>\
**Category:** Question and Answers\
**Tags:** calendar-api\
**Created:** [August 23, 2025, 9:51am UTC](https://forums.nylas.com/t/nylas-get-availability-payload-confusion/880 "2025-08-23T09:51:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lsr2001](https://avatars.discourse-cdn.com/v4/letter/l/f6c823/32.png) [@lsr2001](https://forums.nylas.com/u/lsr2001)\
**Post date:** [August 23, 2025, 9:51am UTC](https://forums.nylas.com/t/nylas-get-availability-payload-confusion/880/1 "2025-08-23T09:51:27Z")

</div>

In Nylas, Get availability API in payload if we set **`participants.open_hours.timezone`** to some other timezone compared to that set in user’s calendar will it cause difference in fetching timeslots?

---

<div class="post-metadata">

**Author:** ![akay](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@akay](https://forums.nylas.com/u/akay)\
**Post date:** [August 26, 2025, 6:41pm UTC](https://forums.nylas.com/t/nylas-get-availability-payload-confusion/880/2 "2025-08-26T18:41:58Z")

</div>

Yes, setting the participants.open\_hours.timezone to a timezone different from the user’s calendar will affect the calculation of available timeslots. The timezone field in open\_hours determines the local time context for the start and end of open hours used in the availability search. If the timezone set here does not match the user’s actual calendar timezone, Nylas will interpret the open hours using the specified timezone, which can result in different timeslots being considered available or unavailable compared to the user’s calendar settings.
