Fix (v1.5.1)
There was an incongruencies between the “updated” data in the “last updated” API and the “public” API.
This value should be the date (unixtime) when, in the database, the information is updated.
In the “latest updated” API, the value was correct, but not in the “public” API, where the value was the time when the cache file was generated.
When the API was created, the value had a lot of sense, but with the latest changes it required a proper value.