Dates are formatted according to ISO 8601 and reported only in UTC time.
For example when providing a pickup_at with value "2017-03-19T09:00:00+01:00" when using the Create a Job endpoint, it will request a Job to be started at 9:00 on the 19th of March, Paris time.
Please note that when looking at job history in your dashboard, the time is always shown as your local time depending on your current geographical location.
Hi Paul,
Could you please explain why this differs from RFC 3339 ?
According to that document time ā2017-03-19T09:00:00+01:00ā will be 9:00 Paris time and 8:00 UTC, because offset show on how many hours this time provided is different from UTC one.
Hello Viktor,
Interesting question thanks !
After having double checked you are totally right, so I will update the previous post.
We did not take into account the daylight saving time hour change that occurred the 26th of March 2017.
So 2017-03-19T09:00:00+01:00 is indeed 9:00 Paris time and 8:00 UTC
And 2017-03-26T09:00:00+01:00 is then 10:00 Paris time and 8:00 UTC
Using a good converter can be useful.
About RFC 3339, it is a profile of the ISO 8601 standard. They are basically the same concepts (except small subtle differences) but RFC 3339 needs more requirements to represent completely the date and time.
Here is a interesting thread about the subtleties between ISO 8601 and RFC 3339.
Hi Paul
Sorry for such late response, Iām not monitoring this forum too frequently 
I think on daylight saving time additional hour should be added to time offset. So 2017-03-26 09:00:00 should be represented as 2017-03-26T09:00:00+02:00 with +2 hours offset.
You are absolutely right