**The problem:
Many users report that an error occurs after a few requests, well this error occurs because they do not have a valid user token

**The solution:
allow requests only for users who have a valid token, so the user cannot use the API when not logged in

**The alternatives:
add valid token to all routes and return invalid token error or try logging in

Additional context
in the group it was also commented on improving the generic error message or refactoring the validToken try catch