Found some interesting Articles
http://apiux.com/2013/03/20/5-laws-api-dates-and-times/
https://www.moesif.com/blog/technical/timestamp/manage-datetime-timestamp-timezones-in-api/
prefer ISO 8601 (yyyy-MM-dd'T'HH:mm:ssZ) because it’s human readable and has a specified timezone. There is no ambiguity if the epoch is in seconds or milliseconds. ISO 8601 strings are encoded in a way that enable decent string sorting and comparison.
Epoch has benefits over ISO 8601 also. If you’re dealing with high volume sensor data or APIs for IoT devices, you may want epoch since it enables smaller payloads without accounting for compression and more familiar with those coming from an IoT/embedded background
and
https://stackoverflow.com/questions/9581692/recommended-date-format-for-rest-get-api
http://apiux.com/2013/03/20/5-laws-api-dates-and-times/
https://www.moesif.com/blog/technical/timestamp/manage-datetime-timestamp-timezones-in-api/
prefer ISO 8601 (yyyy-MM-dd'T'HH:mm:ssZ) because it’s human readable and has a specified timezone. There is no ambiguity if the epoch is in seconds or milliseconds. ISO 8601 strings are encoded in a way that enable decent string sorting and comparison.
Epoch has benefits over ISO 8601 also. If you’re dealing with high volume sensor data or APIs for IoT devices, you may want epoch since it enables smaller payloads without accounting for compression and more familiar with those coming from an IoT/embedded background
and
https://stackoverflow.com/questions/9581692/recommended-date-format-for-rest-get-api
