Historically the verify_credentials API endpoint returned a 401 with a code of 89 if the user’s tokens have been revoked. It was still this way at least as late as October the 11th.
It seems it’s now returning the less specific 401 with a code of 32. I’d like to know if this is intentional and I should update my code to treat that as the new ‘invalid token’ code?
Here’s one of the docs that shows code 89 is the expected code: https://dev.twitter.com/docs/error-codes-responses