I’ll share the investigation results where I found that Newgistics time zone has tz database name America/Denver and is MT (MST/MDT).
The tz database names corresponding to Mountain Time are as follows:
Time zone Currently Mountain Daylight Time (MDT), UTC -6 Standard time (Mountain Standard Time (MST), UTC -7) starts November 3, 2019The IANA time zone identifiers for Mountain Time are America/Boise, America/Cambridge_Bay, America/Denver, America/Edmonton, America/Inuvik, America/Ojinaga and America/Yellowknife.
Although not listed above, there are cases like tz database name America/Phoenix where it’s just MST without DST (Daylight Saving Time).
Note that these abbreviations may change depending on the time zone offset. This helps to distinguish offsets between places that may or may not use DST.// Denver observes DST moment.tz([2012, 0], ‘America/Denver’).format(‘Z z’); // -07:00 MST moment.tz([2012, 5], ‘America/Denver’).format(‘Z z’); // -06:00 MDT // Phoenix does not observe DST moment.tz([2012, 0], ‘America/Phoenix’).format(‘Z z’); // -07:00 MST moment.tz([2012, 5], ‘America/Phoenix’).format(‘Z z’); // -07:00 MST
According to rocketsofawesome/newgistics-ruby: Ruby client for the Newgistics API, Newgistics appears to use America/Denver.
Option time_zoneDescription The time zone used by Newgistics. When the API sends timestamps back it doesn’t include a time zone, if it’s not provided, the value of this setting will be used when parsing the timestamps into Time objects. You shouldn’t need to change this setting
Default Value “America/Denver”
That’s all from the Gemba.