Thanks Alex, looks great.

I'm playing with it now and am looking to use it to replace the
additional show/user.json call that I previously needed.  There are a
few properties that are in user/show but not in the verify_credentials
method, I was wondering if there are plans to include these in a
future update, or if I'll need to continue using two separate calls as
I am now.

Those that are missing/not returned are:
 - friends_count
 - utc_offset
 - profile_text_color
 - statuses_count
 - profile_link_color
 - notifications
 - following
 - time_zone
 - created_at
 - profile_sidebar_fill_color
 - favourites_count
 - profile_sidebar_border_color
 - profile_background_color

thanks

On Dec 11, 1:07 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> Just a reminder: today was the day for this change to go live, and it
> just went live.
>
>
>
> On Thu, Dec 4, 2008 at 12:42, Brooks Bennett <[EMAIL PROTECTED]> wrote:
>
> > I agree, this is a great change.
>
> > On Dec 3, 11:07 pm, "dean.j.robinson" <[EMAIL PROTECTED]>
> > wrote:
> >> "return the representation of the authenticated user"
>
> >> does that mean that the response will be the same as if we 
> >> calledhttp://twitter.com/users/show/id.format for the authenticated user?
> >> If so that would be awesome and means I could completely eliminate
> >> some of the extra api calls that I'm making.  Doesn't matter too much
> >> either way though, since both Hahlo 3.1 and Hahlo 4 (which I've
> >> recently begun work on) both currently use the http status for
> >> confirmation.
>
> >> thanks for the heads up.
>
> >> On Dec 3, 1:14 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
>
> >> > As perhttp://code.google.com/p/twitter-api/issues/detail?id=173we'll
> >> > be changing the /account/verify_credentials method to return the
> >> > representation of the authenticated user.  Because some applications
> >> > depend on the contents of this response, we're delaying this change
> >> > until December 10th, 2008.
>
> >> > Please update your applications to verify by response code, not by the
> >> > response body for this method.  If you get a 200 back, you're
> >> > verified.  If you get a 401 back, you're not.
>
> >> > If you can't ship an update in 8 days, please let us know and we'll
> >> > push the date out further.
>
> >> > --
> >> > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
>
> --
> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x

Reply via email to