If no other TimeZone configuration option is used, aftonApi expects a TimeZone to be specified on each api call.
If no TimeZone is specified on an api call, or an api call sends an invalid TimeZone, an error is thrown and the call is rejected.
Common Pattern API Call Scenarios - TimeZones
POSTing fromDates and thruDates (aftonApi Date) within api calls for scheduling purposes. TimeSpans are required on these data elements.
Query Engine requests for data. A TimeZone (reqTimeZone) must be specified so aftonApi can return the dates using the desired time zone.