Inconsistent date values

The api documentation reports that date-time values are returned as yyyy-mm-ddThh:nn:ssZ but on some occasions its returned as yyyy-mm-ddThh:nn:ss+00:00

Example Case - See the created_at field

+00:00 is perfectly valid as a date format.

It’s not “broken”

Z is the same as +00:00 it doesn’t matter that the API returns a Z or a Offset which is perfectly fine under the RFC specification for DateTime formats

The values should still be consistent regardless of whether the syntax is actually broken or invalid.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.