17 Sep 2021 08:17 AM - last edited on 20 Sep 2021 09:48 AM by MaciejNeumann
To whom it might concern 😉
The documentation says:
But using a space character will not work:
{"error":{"code":400,"message":"Constraints violated.","constraintViolations":[{"path":"from/to","message":"Failed to parse time instant expression. Reason: Failed to classify a date format: \"2021-01-01 00:00:01\".","parameterLocation":"QUERY","location":null}]}}
Using 2021-01-01T00:00:01 will work.
Tested using Swagger interface and curl
Is there any official way of reporting bugs - or is this the way?
Solved! Go to Solution.
22 Sep 2021 10:13 AM
thx for reporting this.
I´ve created an issue to have our engineers taking care of it.
27 Sep 2021 07:04 AM
@uhh fyi - this has been fixed according to the documentation, so the human readable timestamp now also allows whitespace.