>From search, and now looking at the page I apparently missed this big
warning:
Warning: The user ids in the Search API are different from those in the
> REST API (about the two APIs ). This defect is being
> tracked by Issue
> 214<http://code.google.com/p/twitter-api/issues/detail?id=214>.
> This means that the to_user_id and from_user_id field vary from the
> actualy user id on Twitter.com. Applications will have to perform a screen
> name-based lookup with the
> users/show method
> to get the correct user id if necessary.
My apologies for wasting your time.
--Christopher
On Thu, Apr 22, 2010 at 10:12 PM, Mark McBride wrote:
> The userid for elliottng appears to be 4696. How did you get the 8467
> value?
>
> ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Thu, Apr 22, 2010 at 9:52 PM, stumm wrote:
> > I'm doing a call on users lookup and for some reason it's saying IDs
> > do not exist (for IDs I'd gotten from tweets that I got by doing a
> > search). For example when looking up the user elliottng (who from a
> > quick glance doesn't look like spam). The call I'm making is:
> > http://api.twitter.com/1/users/lookup.json?user_id=8467
> >
> > Strangely if I do the call with the users screen name, it seems to
> > work.
> > http://api.twitter.com/1/users/lookup.json?screen_name=elliottng
> >
> > Why are these users not showing up when searched by user ID?
> >
> > Thanks,
> > --Christopher
> >
> >
> > --
> > Subscription settings:
> http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
> >
>
