[Cars] locations : TimeZone Parsing + More than one month about xee-api-docs HOT 7 CLOSED

Hi, thank you for the feedback,
I could reproduce, I will give a look ASAP to fix this bug and I'll let you know.

from xee-api-docs.

Keep us informed :)

from xee-api-docs.

Any updates ?

from xee-api-docs.

Hello, sorry for the delay. I'm running out of time these days.

Anyway, @LeGuit could you check that the request is correctly URL encoded?

This request works :
curl -X GET -H "Authorization: Bearer XXXXX" -H "Content-Type: application/json" "https://staging.xee.com/v3/cars/2155/locations?begin=2016-09-20T00:00:00%2B02:00&end=2016-09-30T00:00:00%2B02:00"

This one, does not:
curl -X GET -H "Authorization: Bearer XXXXX" -H "Content-Type: application/json" "https://staging.xee.com/v3/cars/2155/locations?begin=2016-09-20T00:00:00+02:00&end=2016-09-30T00:00:00+02:00"

from xee-api-docs.

Hey @alexjomin !

I've just test both of those requests and yes the first is working and the second does not.

Referring to the documentation the format should be :
"Format is 2016-04-20T13:37:42Z(+/-HH:mm)"
So it's strange that the second one does not work

from xee-api-docs.

So, the correct URL-encoded url should be :
https://{env}.xee.com/v3/cars/{carId}/locations?begin=2016%2D09%2D20T00%3A00%3A00%2B02%3A00&end=2016%2D09%2D30T00%3A00%3A00%2B02%3A00

from xee-api-docs.

":" is indeed an unsafe character, it's better to encode it as %3A even if it leads to the same result : Example in the go playground

from xee-api-docs.