[#752] Timezone for email notification

Bug Reports
,
1

Migrated from Redmine #752 | Author: Pavel Merkulov
Status: New | Priority: Normal | Created: 2021-08-05

Our app is using your Rest API (described here API documentation | SimplyBook.me Online Scheduling)
Our company and our client can be in different time zones. When our client make booking we transferm his time zone to time zone of our company. After this our client gets email notification about booking he made. The problem is notification contain booking time in time zone of our company. How can we resolve it? How can we set client time zone?

Our company name is Eurogroup

2

Redmine Admin wrote:

there is no timezone related params in REST API. You can use JSON RPC API API documentation | SimplyBook.me Online Scheduling
API documentation | SimplyBook.me Online Scheduling and specify ‘client_time_offset’ value in $clientData object as difference
between client’s time zone and company’s time zone in minutes
API documentation | SimplyBook.me Online Scheduling this method is to get company TZ offset

3

Pavel Merkulov wrote:

Redmine Admin wrote:

there is no timezone related params in REST API. You can use JSON RPC API API documentation | SimplyBook.me Online Scheduling
API documentation | SimplyBook.me Online Scheduling and specify ‘client_time_offset’ value in $clientData object as difference
between client’s time zone and company’s time zone in minutes
API documentation | SimplyBook.me Online Scheduling this method is to get company TZ offset

JSON RPC API does not support 2FA with google authen. We used RPC API before and when we turned on google authen for our users we got problems. You advised to us to start using Rest API. Do we need to back to RPC Api again? :slight_smile:

4

Redmine Admin wrote:

this is up to you. REST API does not support TZ options. JSON RPC does not support 2fa because this 2 APIs were made for different purposes:
JSON RPC is for client bookings mainly where 2fa is not needed but TZ is needed
REST API is for admin bookings where 2FA is needed but client time offset is not needed