#1

Testing the new invalidate_token endpoint
When you try to revoke a token for a user that’s been restricted, you get 403 errors

{“errors”:[{“code”:326,“message”:“To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.”}]}

So it doesn’t allow us to revoke access to users who have been restricted (Suspended accounts might also have the same problem)

1 Like
#2

Hmm thanks for the tip @Connexinet. Testing this internally.

2 Likes
#4

hello twitter,

facing issue similar to this where for a restrcited account this api is not giving 326 code instead of it provides response. How can I judge from the success response whether account is locked or not. help is much appreciated.

1 Like