The same thing goes for 403... It's either update limit hit, or not allowed to DM that person because you're not following him. The latter should really have another error code, or you're forced to either make another api call, or to interpret the returned response.

On Sep 25, 2009, at 5:51 PM, Dewald Pretorius <> wrote:

API folks, could you please, please NOT return 401 "Not authorized"
when an authenticated call with a perfectly valid username and
password requests a /queryusername.json where that queryusername
happens to be a username that does not exist.

Rather return 404.

By returning 401 you are making it impossible for me to tell where the
actual problem lies and inform the user. Is it with the user's
password, or is it because the user wanted information about a Twitter
account that does not exist?


Reply via email to