Hello Matt, Thanks for trying again (I did only see your answer just now, sorry). Good to know you've found out that the console is not seeing the parameters. Thank you very much for filing it in the issue tracker. This means that I only have one question left: can someone tell me if users/lookup with oauth-authentication is working fine?
Thanks for your help people. Regards, René On 30 mei, 08:11, themattharris <thematthar...@twitter.com> wrote: > OK, I've tried this again. It seems the console is not seeing the > parameters. I've filed this in the issues tracker [1] as issue 1661. > Thanks for letting us know. > > 1.http://code.google.com/p/twitter-api/issues/detail?id=1661 > > On May 29, 10:33 pm, Abacadabrados <rene.rikk...@gmail.com> wrote: > > > Hello Matt, > > > Thank you for your quick and clear response. > > > However, the user id and screen name are both valid. Both User_id = 0 > > or screen_name = twitterapi work perfectly in the API Console for home/ > > timeline - but not for users/lookup. I also tried it with my > > screen_name, this works fine with home/timeline but gives a 'No user > > matches for specified terms' for users/lookup. Maybe I'm doing > > something wrong. Is the API console users/lookup working for your > > screen_name at the moment? > > > Regards, René > > > On 30 mei, 01:24, themattharris <thematthar...@twitter.com> wrote: > > > > ... > > > You need to give the user lookup request some valid user ids or screen > > > names. The error you are receiving is because you are sending a > > > user_id of 0 which is not a valid account. Maybe try with your screen > > > name first. > > > ...
