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
Instead of the latest endpoint, I call the API with the current date. In this way, I get the same rates throughout the day, in case something happens to the cache. I used the current day in UTC+2 (my timezone) and it seems the API uses UTC, so for the first two hours of each day I receive an error. I'll fix this on my side, but I just wanted to mention that the error is unhelpful:
{
"success":false,
"error":{
"code":302,
"type":"invalid_date",
"info":"You have entered an invalid date. [Required format: date=YYYY-MM-DD]"
}
}
The date format is fine, it's just that the date is in the future, as seen from UTC+0.
I think this situation warrants a separate error message, one which also indicates the timezone of the API server.
The text was updated successfully, but these errors were encountered:
Instead of the
latest
endpoint, I call the API with the current date. In this way, I get the same rates throughout the day, in case something happens to the cache. I used the current day in UTC+2 (my timezone) and it seems the API uses UTC, so for the first two hours of each day I receive an error. I'll fix this on my side, but I just wanted to mention that the error is unhelpful:URL: http://data.fixer.io/api/2021-09-10?access_key=xxxxx&format=1&base=EUR
The date format is fine, it's just that the date is in the future, as seen from UTC+0.
I think this situation warrants a separate error message, one which also indicates the timezone of the API server.
The text was updated successfully, but these errors were encountered: