-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ETA in API result is off by 23+ hours because of time zone error #29
Comments
Thanks for reporting this issue! Our team is actively investigating the UPS tracking timezones. It does look like the API incorrectly returns UTC in some cases, instead of the corresponding locations' local timezone. We have prioritized this as a high priority bug and will provide updates here as soon as we know more. |
@simonkreuz has there been any progress on this issue? |
So we have plans on improving the datetimes that are being returned for tracking events soon. We are just wanting to solidify instances where a carrier doesn't provide any location or timezone information for a given event, and how best to clarify that via the API. We're always happy to hear input on this as we're working or improve what you get back. |
Is there an update on this one? |
Yes - we've made a lot of progress! As an example, try using UPS tracking number Some additional notes:
|
Thanks for the update @simonkreuz! |
Hi,
The UPS tracking page for 1ZY11A540340532092 says (or said):
Converting the latest datetime in that "Estimated Delivery Time" range to UTC makes it 2016-12-30 23:15.
If you look at https://api.goshippo.com/v1/tracks/ups/1ZY11A540340532092, the ETA says "2016-12-30T00:00:00Z". Since you are using Zulu time, which is UTC, your API should instead display the ETA as 2016-12-30 23:15.
Your API currently seems inaccurate by 23+ hours!
Am I misunderstanding something? I personally can't use an API that could be off by a whole day. I doubt others could either. Thanks for your help and for your cool service.
The text was updated successfully, but these errors were encountered: