Applications that read Numista data via the API first read a list with get types, and then read the detailed data with get type and get issues. If they want to refresh this data later, have to repeat the process.
I request that a field be added to the endpoint /types with the timestamp of the last update of each type or its issues.
This way, to refresh the data, applications will only have to read the types that have changed, saving most of the API calls.