The Web API docs use a Zoned date time format, e.g. “2019-08-24T14:15:22Z” (note the Z at the end) seemingly for everything, which would imply UTC instant.
However, it seems that the actual date time is stored as local date time in America/Denver time zone and is returned as e.g. “2022-09-30T16:59:59” (note no Z at the end).
Could you please confirm this and whether it is intended bvehaviour and just a bug in the docs?
I don’t really mind either way, just want to make sure my code won’t break if you decide to fix it and start returning zoned format.
Also noticed that the web GUI (https://app.cryptlex.com/licenses) displays the date time in my local time zone.
So, if I set a license to expire on 2022 Sep 9, 23:59:59, and the API indeed returns the license with
"expiresAt": "2022-09-30T23:59:59", the web GUI at https://app.cryptlex.com/licenses will show this expiration date time as:
Oct 1, 2022 12:59 AM
Might be a good idea to also print the time zone in the web GUI when showing date time…
We store all the date time data in utc and our web api endpoints return the date time in utc.
Right. It is indeed.
What confused me was that your web interface uses 12 AM to show time between 00 and 01 hours.