Warning: The user ids in the Search API are different from those in the
> REST API (about the two APIs <http://apiwiki.twitter.com/API-Overview>). This
> defect is being tracked by Issue
> 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
> to get the correct user id if necessary.
You will see from
http://api.twitter.com/users/show.json?screen_name=katie_walls that the
actual user id is 75030777.
On Sun, Apr 11, 2010 at 12:07, ryan baldwin <ryanbald...@gmail.com> wrote:
> Hey all, I've noticed some very odd and inconsistent behaviour over
> the past couple days that has me stumped. When I use the users/show
> endpoint using user_id the response produces a 404. When I use
> screen_name of that same user everything works fine. Anybody know what
> the scoop is?
> here are a couple of examples:
> u'text':u'Twittering from the eye doctors office. Its kinda
> really boring here....',
> 10 Apr 2010 16:20:50 +0000',
> u'profile_image_url': u'http://a3.twimg.com/profile_images/
> u'source': u'<a href="http://ubertwitter.com"
> u'location': u'ÜT:52.138437,
> -106.667903 ', u' from_user':u'katie_walls',
> u'id':11944382350 L,
> http://api.twitter.com/users/show.json?user_id=53548499 (404)
> http://api.twitter.com/users/show.json?screen_name=katie_walls (200,
> works fine)
> Any ideas? I'm at a complete loss and I'm really not looking forward
> to the repair costs of the hole I've made in the wall with the top of
> my head.
> - ryan.
> To unsubscribe, reply using "remove me" as the subject.
Abraham Williams | Developer for hire | http://abrah.am
PoseurTech Labs | Projects | http://labs.poseurtech.com
This email is: [ ] shareable [x] ask first [ ] private.