You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the UTC date and time standard and so expect you to use this format YYYY-MM-DD hh:mm:ss.ssssss . The meaning of the letters is defined in ISO 8601.
This is unclear on what the timezone is. I suspect what it's trying to say is that:
Bunq uses the ISO8601 datetime format standard
All datetimes are in the UTC timezone
But it's ambiguous. Furthermore the API could instead be sending Z-suffixed datetimes to make it completely unambiguous what timezone the datetimes are in ("2019-12-26 05:43:34.091865Z" instead of 2019-12-26 05:43:34.091865).
The text was updated successfully, but these errors were encountered:
https://beta.doc.bunq.com/basics/api-conventions#time-formats
This is unclear on what the timezone is. I suspect what it's trying to say is that:
But it's ambiguous. Furthermore the API could instead be sending Z-suffixed datetimes to make it completely unambiguous what timezone the datetimes are in (
"2019-12-26 05:43:34.091865Z"
instead of2019-12-26 05:43:34.091865
).The text was updated successfully, but these errors were encountered: