[twitter-dev] Re: users/lookup seems not to be working
After some research in my own application it appears that I forgot to UrlEncode the parameters of the users/lookup query. By incident I hadn't used any special characters in the parameters until now, so I didn't notice this earlier. Conclusion: - Matt addressed the issue that the console on dev.twitter.com ignores the parameters, - users/lookup with oauth-authentication is working fine. Thanks again for helping me. Regards, Rene On 30 mei, 12:34, Abacadabrados wrote: > 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 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 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 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. > > > > ...
[twitter-dev] Re: users/lookup seems not to be working
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 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 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 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. > > > ...
[twitter-dev] Re: users/lookup seems not to be working
Hello Abraham, You're right. I did not check the response of home_timeline well enough, I'm sorry for missing that. However, I'm still having some troubles, let me try to do a better job on explaining them. 1. The main problem is using users/lookup in a test application in which I provide authentication by oauth. I get a 404-error as result. I did however get the oauth-authorization working for other queries, these give the expected results: statuses/home_timeline, statuses/ user_timeline and friends/ids. So I have specifically a problem with users/lookup. Maybe I'm doing something wrong here. 2. To check if I did use the right syntax for users/lookup I tried it in the API console. It seems however the console is not seeing the parameters/values that I provide. Queries without parameters (like statuses/home_timeline) give the expected results. However, when I use a query with user_id as a parameter I don't get the exptected results. For example I get my own statuses on statuses/user_timeline even when I provide the parameter/value pair user_id/12345. And I get a "not found" error for users/show and a "No user matches for specified terms" error for users/lookup. In this case I first checked that 12345 is a valid user_id via hurl, by the url (http://goo.gl/DpWe) Abraham provided, (12345 is used in some dev.twitter examples too). However, when I check it on the API console, it seems that the parameters I provided (user_id-=12345) is not included in the request header somehow. 3. When using users/lookup directly via https://api.twitter.com/1/users/lookup.json?user_id=12345 and providing my username/password in the *basic* authentication popup- window, this query is working fine. Again, I guess I'm doing something wrong, but I hope anyone could help me out. Therefor two questions: 1. Most important: has anyone users/lookup working with oauth- authentication? 2. Can anyone check if the API Console sees the parameters that are provided as input? For instance is users/lookup userid=12345 working like it does in hurl? Thanks for your very appreciated help, Regards, René On 30 mei, 07:44, Abraham Williams <4bra...@gmail.com> wrote: > home_timeline always shows the statuses for the authenticated user not the > user_id you pass in a parameter. > > As you can see there is no user with the id of 0:http://goo.gl/DpWe > > Abraham > > > > On Sat, May 29, 2010 at 22:33, Abacadabrados 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 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. > > > ... > > -- > Abraham Williams | Developer for hire |http://abrah.am > @abraham |http://projects.abrah.am|http://blog.abrah.am > This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: users/lookup seems not to be working
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 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 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. > > ...
Re: [twitter-dev] Re: users/lookup seems not to be working
home_timeline always shows the statuses for the authenticated user not the user_id you pass in a parameter. As you can see there is no user with the id of 0: http://goo.gl/DpWe Abraham On Sat, May 29, 2010 at 22:33, Abacadabrados 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 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. > > ... -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: users/lookup seems not to be working
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 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. > ...
[twitter-dev] Re: users/lookup seems not to be working
Hey Abacadabrados, 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. You can find more information on how the method works on dev.twitter.com [1]. Hope that helps, Matt 1. http://dev.twitter.com/doc/get/users/lookup On May 29, 5:17 am, Abacadabrados wrote: > users/lookup seems not be working in the API console. > > For instance: I signed in, and selected my application in the console > Headers and methods: GET / 1 / users/lookup > Parameters and values: user_id / 0 > Response body: ... "No user matches for specified terms" ... > > The same for parameters and values: screen_name / twitterapi > > Interesting is maybe that I get a 404-error when using users/lookup in > my own application. > For your information: I do succesfully use OAuth, and other queries > like friends/ids are doing fine.
