#1

Do we have deauthorize callback here?

#2

No, you won’t be directly notified when a user has deauthorized your application. The access token will simply cease functioning.

#3

are you guys going to implement a deauthorize callback in the near future?

#4

Is there an example anywhere of what the response should look like when trying to auth against an account that has de-authorized your app?

Also, are there any penalties for attempting to auth with an access token that’s been de-authorized? My intention is to remove access tokens from my app when they’ve been deactivated by users so I don’t continue trying to make calls with bad tokens.

Thanks in advance!
Adam

#5

Would really love a deauthorize callback so we can be proactive about account management. Facebook provides this functionality and so should Twitter.