Hello there,

The screen_name and user_id had to be removed from the redirect back to your site but I later added it to the response to the access_token call. That is an official feature and can be relied upon. Looking back it seems I never announced the feature here on the list after I put it on the change log [1]. Sorry I forgot to mention that … feel free to use those parameters.

 – Matt Sanford / @mzsanford
     Twitter Dev

[1] - May 13th - http://apiwiki.twitter.com/REST-API-Changelog

On Jul 11, 2009, at 9:34 AM, Scott Carter wrote:

I noted that the screen name (and user id) are returned along with the
Access token and secret.

It this a documented feature that I can rely upon?

The only related thread that I found on this topic was:

That thread was apparently referring to the callback after
authorization and why screen_name and user_id were removed for
security reasons.  Matt mentioned that the verify_credentials method
was the solution in that case.

If I have the screen_name available with the Access token/secret, I
don't see a need for calling verify_credentials at all in the
process.  I don't really need the screen name until after I exchange
my request token for an access token.   Can I rely on getting the
screen_name this way?  Am I missing another reason for needing to call


- Scott Carter

Reply via email to