Your concern is valid and the message may be common for any kind of exception like "422 unprocessable entity". And its true that the exception is not at all related to the actually problem. I already come across this issue and got resolve too. Its only because of, either passing the token id which may be expired or the input format is wrong which is not satisfying the required criteria. For this the only solution is go through the API properly and make sure you are passing the proper input as per the API need.