[twitter-dev] users/lookup
I'm using the users/lookup.json API and passing a valid list of user_ids that I retrieve from friends/ids (yes, there are 100). I keep getting the response: No user matches for specified terms when making the call, even though the list is valid and I have inspected the request being sent. Any ideas why this would be happening? The friends/ids call is working fine authenticated and I am trying to make a similar authenticated GET call with the users/lookup function. -- Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet? Twitter developer links: Documentation and resources: https://dev.twitter.com/docs API updates via Twitter: https://twitter.com/twitterapi Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe
[twitter-dev] Users/Lookup
Hi,
I have read all the users/lookup related posts and also scoured the
internet looking for an appropriate example.I posted a question as a
reply on one but don't see it so I am hoping someone can help a
twitter api newbie.
I just want to get results from users/lookup. I am using Abraham's
Oauth library, which I have been able to get to work in other
instances with no problems. I'm hoping it's my lack of understanding
of how the syntax should be. Here is the code:
// all values populated correctly
$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET,
$OAuthKey, $OAuthSecret);
// saw this example as correction of the following line; neither
seems to work
$userDeets = $connection-get('/users/lookup.json',
array('screen_name' = 'biz,twitterapi'));
// $userDeets = $connection-get('/users/lookup.json?
screen_name=biz,twitterapi');
foreach ($userDeets as $item)
{
echo $item-followers_count;
echo br;
}
Thanks in advance for any insight.
-Gabe
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Users/Lookup
Try:
$userDeets = $connection-get('users/lookup' array('screen_name' =
'biz,twitterapi'));
That should work.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
http://abrah.amJust launched from Answerly http://answerly.com:
InboxQhttp://inboxq.comfor Chrome
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Tue, Apr 12, 2011 at 12:15, Gabe oneill.g...@gmail.com wrote:
Hi,
I have read all the users/lookup related posts and also scoured the
internet looking for an appropriate example.I posted a question as a
reply on one but don't see it so I am hoping someone can help a
twitter api newbie.
I just want to get results from users/lookup. I am using Abraham's
Oauth library, which I have been able to get to work in other
instances with no problems. I'm hoping it's my lack of understanding
of how the syntax should be. Here is the code:
// all values populated correctly
$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET,
$OAuthKey, $OAuthSecret);
// saw this example as correction of the following line; neither
seems to work
$userDeets = $connection-get('/users/lookup.json',
array('screen_name' = 'biz,twitterapi'));
// $userDeets = $connection-get('/users/lookup.json?
screen_name=biz,twitterapi');
foreach ($userDeets as $item)
{
echo $item-followers_count;
echo br;
}
Thanks in advance for any insight.
-Gabe
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] users/lookup Bug with incorrect attached statuses
Before I post this as an issue is anyone else getting this problem. When I lookup multi users by username I get correct information on the user but the status supplied is an out of date in some cases. Cheers Darren -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users
I can confirm that this happens whether the lookup is by screen_name or id. Incidentally, any progress on Twitter's side? Way over a month now, and it only seems to be getting worse. Cheers, Adrian On Tue, Mar 22, 2011 at 1:18 AM, Nischal Shetty nischalshett...@gmail.comwrote: Anything on this? It's been quite some time and user lookup I believe would be used by a lot of apps. -N On 16 March 2011 05:46, Taylor Singletary taylorsinglet...@twitter.comwrote: Still working on it, unfortunately. No ETA for a fix yet. I know it's an aggravating bug for anyone who runs into it. Thanks for being patient. Taylor On Mar 15, 2011, at 5:09 PM, Adrian Petrescu apetr...@gmail.com wrote: Hi Taylor, Not trying to be pushy or anything, but have you guys uncovered anything related to this issue? It's still happening quite regularly for a couple of weeks now. Thanks, Adrian -- Twitter developer documentation and resources: http://dev.twitter.com/dochttp://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- -Nischal twitter: NischalShetty http://twitter.com/nischalshetty facebook: Nischal http://facebook.com/nischal -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users
Anything on this? It's been quite some time and user lookup I believe would be used by a lot of apps. -N On 16 March 2011 05:46, Taylor Singletary taylorsinglet...@twitter.comwrote: Still working on it, unfortunately. No ETA for a fix yet. I know it's an aggravating bug for anyone who runs into it. Thanks for being patient. Taylor On Mar 15, 2011, at 5:09 PM, Adrian Petrescu apetr...@gmail.com wrote: Hi Taylor, Not trying to be pushy or anything, but have you guys uncovered anything related to this issue? It's still happening quite regularly for a couple of weeks now. Thanks, Adrian -- Twitter developer documentation and resources: http://dev.twitter.com/dochttp://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- -Nischal twitter: NischalShetty http://twitter.com/nischalshetty facebook: Nischal http://facebook.com/nischal -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users
Hi Taylor, Not trying to be pushy or anything, but have you guys uncovered anything related to this issue? It's still happening quite regularly for a couple of weeks now. Thanks, Adrian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users
Still working on it, unfortunately. No ETA for a fix yet. I know it's an aggravating bug for anyone who runs into it. Thanks for being patient. Taylor On Mar 15, 2011, at 5:09 PM, Adrian Petrescu apetr...@gmail.com wrote: Hi Taylor, Not trying to be pushy or anything, but have you guys uncovered anything related to this issue? It's still happening quite regularly for a couple of weeks now. Thanks, Adrian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] users/lookup returns duplicates, missing records for valid users
When using users/lookup with 100 random screen_names, I often get duplicate records, as well as missing records for valid users that are not deleted, suspended, or non-existent. Ive tested this with python-twitter as well as twurl. The responses I receive are non-deterministic; different users are omitted each time. Roughly 10% of all the users I request are omitted, this from a sample of 10,000 requests to users/lookup over distinct groups of 100 users. *Sample query with 100 random users (grabbed from public timeline): * twurl /1/users/lookup.json?screen_name= _cameraobscura,aboutmoneytips,aliceee_tw ,alltinomit,allysonfly,andy_marin,annadobak,aquarenasw,ardysmc,asd_tscmom,asyaetc,ayranlc,azianperc,bagelcc,bernah515, betinhots ,bichhu_10,billexd,bodyplus1,bruno_ral,buckley_l,buena_san,bunchukav,bunga_csv,c_loste,cansuneverson,canyalady,carolinefassl,ceedeezy,cernoblog,chairs4church,chakal_guitar,choice355,clubbanga,congelob,cr8cornucopia,crcon1863,creceitas,ctrl_news,cynsaurus,dancewithlola,danielbegun, demandplanner ,dennisboutkan,deyavoltolini,dharple,domeque,dptodecompras,era_donations,expertwitless,famousgang_31,folhadocariri,freebitchin,heywoodxjablomi,hifos, ihavetrunutz ,ikuke7,imar87,inmagv,jamilaelhasni,jplmoreira,jzyblu,katsunumaren767,kittoariobasara,kokohorewasshoi,laayanrc,ladylooc,lailavogelezang,mamibluemovie,manuzunino,marcelstuij,marco_paredes,mariel1820,marilimabio,misterplan,nslupski,pastormic,porterpet,rhizis,sabesa1,sai0531,scoopervin22,scwauters,sergio_ee,sethrynstorm,severoski,shaunatpayne,shikshin_ira,shima_online,shinnosukepass,sjsnsdaddict,smithsupport,ssa_prentiss,stayfrostyse,suellany_hta,sugarpop_bdg,taisinhamartins,tamayamasachiko,xsievert,yaragharib *Records I received a response for (after lowering, sorting):* _cameraobscura, aboutmoneytips, alltinomit, allysonfly, andy_marin, annadobak, aquarenasw, ardysmc, asd_tscmom, asyaetc, ayranlc, azianperc, bagelcc, bernah515, bichhu_10, billexd, bodyplus1, bruno_ral, buckley_l, buena_san, bunchukav, bunga_csv, c_loste, cansuneverson, canyalady, carolinefassl, ceedeezy, cernoblog, chairs4church, chakal_guitar, choice355, clubbanga, congelob, cr8cornucopia, crcon1863, creceitas, ctrl_news, cynsaurus, dancewithlola, danielbegun, dennisboutkan, deyavoltolini, dharple, domeque, dptodecompras, era_donations, expertwitless, famousgang_31, folhadocariri, freebitchin, heywoodxjablomi, hifos, ikuke7, imar87, inmagv, jamilaelhasni, jplmoreira, jzyblu, katsunumaren767, kittoariobasara, kokohorewasshoi, laayanrc, ladylooc, lailavogelezang, mamibluemovie, manuzunino, manuzunino, marcelstuij, marco_paredes, mariel1820, marilimabio, marilimabio, misterplan, nslupski, pastormic, porterpet, rhizis, sabesa1, sai0531, sai0531, scoopervin22, scwauters, sergio_ee, sethrynstorm, severoski, shaunatpayne, shikshin_ira, shima_online, shinnosukepass, sjsnsdaddict, smithsupport, ssa_prentiss, stayfrostyse, suellany_hta, sugarpop_bdg, taisinhamartins, tamayamasachiko, xsievert, yaragharib, yaragharib (1) There are missing records for aliceee_tw (valid user), betinhots (valid), demandplanner (valid), ihavetrunutz (valid) (2) There are duplicate recordsfor manuzunino, sai0531, marilimabio, yaragharib, bringing the total back up to 100 responses (3) While not in this example, suspended/non-existent members are correctly removed from results -- K -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] users/lookup returns duplicates, missing records for valid users
Hi Kurt, Thanks for the great detailed bug report. We're investigating this issue. Taylor @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Tue, Mar 1, 2011 at 10:36 AM, Kurt Thomas kurt.a.tho...@gmail.comwrote: When using users/lookup with 100 random screen_names, I often get duplicate records, as well as missing records for valid users that are not deleted, suspended, or non-existent. Ive tested this with python-twitter as well as twurl. The responses I receive are non-deterministic; different users are omitted each time. Roughly 10% of all the users I request are omitted, this from a sample of 10,000 requests to users/lookup over distinct groups of 100 users. *Sample query with 100 random users (grabbed from public timeline): * twurl /1/users/lookup.json?screen_name= _cameraobscura,aboutmoneytips,aliceee_tw ,alltinomit,allysonfly,andy_marin,annadobak,aquarenasw,ardysmc,asd_tscmom,asyaetc,ayranlc,azianperc,bagelcc,bernah515, betinhots ,bichhu_10,billexd,bodyplus1,bruno_ral,buckley_l,buena_san,bunchukav,bunga_csv,c_loste,cansuneverson,canyalady,carolinefassl,ceedeezy,cernoblog,chairs4church,chakal_guitar,choice355,clubbanga,congelob,cr8cornucopia,crcon1863,creceitas,ctrl_news,cynsaurus,dancewithlola,danielbegun, demandplanner ,dennisboutkan,deyavoltolini,dharple,domeque,dptodecompras,era_donations,expertwitless,famousgang_31,folhadocariri,freebitchin,heywoodxjablomi,hifos, ihavetrunutz ,ikuke7,imar87,inmagv,jamilaelhasni,jplmoreira,jzyblu,katsunumaren767,kittoariobasara,kokohorewasshoi,laayanrc,ladylooc,lailavogelezang,mamibluemovie,manuzunino,marcelstuij,marco_paredes,mariel1820,marilimabio,misterplan,nslupski,pastormic,porterpet,rhizis,sabesa1,sai0531,scoopervin22,scwauters,sergio_ee,sethrynstorm,severoski,shaunatpayne,shikshin_ira,shima_online,shinnosukepass,sjsnsdaddict,smithsupport,ssa_prentiss,stayfrostyse,suellany_hta,sugarpop_bdg,taisinhamartins,tamayamasachiko,xsievert,yaragharib *Records I received a response for (after lowering, sorting):* _cameraobscura, aboutmoneytips, alltinomit, allysonfly, andy_marin, annadobak, aquarenasw, ardysmc, asd_tscmom, asyaetc, ayranlc, azianperc, bagelcc, bernah515, bichhu_10, billexd, bodyplus1, bruno_ral, buckley_l, buena_san, bunchukav, bunga_csv, c_loste, cansuneverson, canyalady, carolinefassl, ceedeezy, cernoblog, chairs4church, chakal_guitar, choice355, clubbanga, congelob, cr8cornucopia, crcon1863, creceitas, ctrl_news, cynsaurus, dancewithlola, danielbegun, dennisboutkan, deyavoltolini, dharple, domeque, dptodecompras, era_donations, expertwitless, famousgang_31, folhadocariri, freebitchin, heywoodxjablomi, hifos, ikuke7, imar87, inmagv, jamilaelhasni, jplmoreira, jzyblu, katsunumaren767, kittoariobasara, kokohorewasshoi, laayanrc, ladylooc, lailavogelezang, mamibluemovie, manuzunino, manuzunino, marcelstuij, marco_paredes, mariel1820, marilimabio, marilimabio, misterplan, nslupski, pastormic, porterpet, rhizis, sabesa1, sai0531, sai0531, scoopervin22, scwauters, sergio_ee, sethrynstorm, severoski, shaunatpayne, shikshin_ira, shima_online, shinnosukepass, sjsnsdaddict, smithsupport, ssa_prentiss, stayfrostyse, suellany_hta, sugarpop_bdg, taisinhamartins, tamayamasachiko, xsievert, yaragharib, yaragharib (1) There are missing records for aliceee_tw (valid user), betinhots (valid), demandplanner (valid), ihavetrunutz (valid) (2) There are duplicate recordsfor manuzunino, sai0531, marilimabio, yaragharib, bringing the total back up to 100 responses (3) While not in this example, suspended/non-existent members are correctly removed from results -- K -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] users/lookup POST read-only applications cannot post
I just started getting this error message within the past hour for my application. My application is read-only in the sense that it never updates a user profile or posts any tweets or anything. My application does, however, use the users/lookup.json API, and I use POST because I am requesting many profiles at once when I use the API. Does the Read-only indication on my application's profile mean I can never use POST? Anyone else seeing anything similar? Brian Maso -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] users/lookup POST read-only applications cannot post
Yes, we have a global catch-all rule that all POST operations are write operations. User/lookup is typically a GET operation anyway ( http://dev.twitter.com/doc/get/users/lookup ) and you can pass the up-to 100 ids as a long query string parameter, provided your HTTP implementation allows for the length you're aiming for. For best results with the lookup API, I recommend keeping the limit a bit below 100 for best operations. Taylor On Tue, Sep 7, 2010 at 10:43 AM, Brian Maso br...@blumenfeld-maso.com wrote: I just started getting this error message within the past hour for my application. My application is read-only in the sense that it never updates a user profile or posts any tweets or anything. My application does, however, use the users/lookup.json API, and I use POST because I am requesting many profiles at once when I use the API. Does the Read-only indication on my application's profile mean I can never use POST? Anyone else seeing anything similar? Brian Maso -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] users/lookup not working for JSON
I might be overlooking something, but it seems like users/lookup isn't
working. I tried it using my app credentials and got the following
message:
{
errors: [
{
code: 17,
message: No user matches for specified terms
}
]
}
Just to be sure, I went to http://dev.twitter.com/console and entered
the parameters from the documentation
http://api.twitter.com/1/users/lookup.xml?user_id=1401881,1401882
http://api.twitter.com/1/users/lookup.xml?screen_name=dougw,raffi
I tried
1. user_id in the left field and 1401881,1401882 then followed
that unsuccessful attempt with
2. screen_name and dougw,raffi in the right field
The second setting was attempted using both GET and POST with
JSON selected as output, and I got the same message.
After trying a bunch of combinations, using XML seemed to still work,
but no more JSON.
[twitter-dev] users/lookup seems not to be working
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.
Re: [twitter-dev] users lookup - user missing
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 /API-Overview). This defect is being tracked by Issue 214http://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/Twitter-REST-API-Method%3A-users%C2%A0show 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 mmcbr...@twitter.com 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 christop...@stumm.ca 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
Re: [twitter-dev] users lookup - user missing
No problem. It's something high on our priority list to get rectified. ---Mark http://twitter.com/mccv On Fri, Apr 23, 2010 at 8:17 PM, Christopher Stumm christop...@stumm.ca wrote: 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. 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 mmcbr...@twitter.com 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 christop...@stumm.ca 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
[twitter-dev] users/lookup issues
Hi, I am using oauth and EPItwitter and I cannot get a decent response from users/lookup. I keep on getting 401 Unauthorized when with the same instance I can get any other method to work fine. I tried navigating in the browser to http://api.twitter.com/1/users/lookup.json?screen_names=screen_name=dougw,raffi and that is giving me a 404 I am not sure if I am fighting an api problem or an issue with EPITwitter. Kind Regards Darren -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] users/lookup issues
Hi Ninjamonk, Slight error in the docs that I'll get fixed right now -- try this instead: http://api.twitter.com/1/users/lookup.json?screen_name=dougw,raffi Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, Apr 22, 2010 at 1:33 PM, Ninjamonk dar...@stuartmedia.co.uk wrote: Hi, I am using oauth and EPItwitter and I cannot get a decent response from users/lookup. I keep on getting 401 Unauthorized when with the same instance I can get any other method to work fine. I tried navigating in the browser to http://api.twitter.com/1/users/lookup.json?screen_names=screen_name=dougw,raffi and that is giving me a 404 I am not sure if I am fighting an api problem or an issue with EPITwitter. Kind Regards Darren -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] users lookup - user missing
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
Re: [twitter-dev] users lookup - user missing
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 christop...@stumm.ca 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
[twitter-dev] users/lookup and OAuthed Signed requests
I'm having a heck of a time getting the users/lookup to work. I keep getting an invalid signature response, however if I try hitting other urls that require authentication (such as statuses/ home_timeline) I get the proper response. The only difference that I can see is that the users/lookup requires a comma separated screen_name param. An example of a call I'm making is as follows: http://api.twitter.com/1/users/lookup.json?screen_name=Ditton,THEO_BROWN,jeff_phillipsoauth_consumer_key=[WITHHELD]oauth_nonce=3702675319114583140oauth_signature=Bjm61%2F0dNQ1YY%2B6DZrKfluh3brk%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088234oauth_token=[WITHHELD]oauth_version=1.0 The above produces a 401. I though perhaps it's because the commas need to be encoded (however the examples I've seen that doesn't seem to be the case). Even if I tried sending up only 1 screen_name, however, it still fails with a 401. http://api.twitter.com/1/users/lookup.json?screen_name=Dittonoauth_consumer_key=[WITHHELD]oauth_nonce=12427699099383609456oauth_signature=gKSz6qPOiPKrJX6NqLuP7HjBkJ4%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088019oauth_token=[WITHHELD]oauth_version=1.0 Like I said, if I hit up the statuses/home_timeline endpoint it works fine. http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=[WITHHELD]oauth_nonce=4782314729649271771oauth_signature=LGfzsFEyzfHOszTPx1GPSzj%2BTN8%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271086839oauth_token=[WITHHELD]oauth_version=1.0 Anybody have any idears? Thanks!
Re: [twitter-dev] users/lookup and OAuthed Signed requests
creating oauth signatures is annoyingly subtle, isn't it? i would suggest playing with http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/and verifying the signature base string and signature you're generating to what that emits. On Mon, Apr 12, 2010 at 9:10 AM, ryan baldwin ryanbald...@gmail.com wrote: I'm having a heck of a time getting the users/lookup to work. I keep getting an invalid signature response, however if I try hitting other urls that require authentication (such as statuses/ home_timeline) I get the proper response. The only difference that I can see is that the users/lookup requires a comma separated screen_name param. An example of a call I'm making is as follows: http://api.twitter.com/1/users/lookup.json?screen_name=Ditton,THEO_BROWN,jeff_phillipsoauth_consumer_key=[WITHHELD]oauth_nonce=3702675319114583140oauth_signature=Bjm61%2F0dNQ1YY%2B6DZrKfluh3brk%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088234oauth_token=[WITHHELD]oauth_version=1.0 The above produces a 401. I though perhaps it's because the commas need to be encoded (however the examples I've seen that doesn't seem to be the case). Even if I tried sending up only 1 screen_name, however, it still fails with a 401. http://api.twitter.com/1/users/lookup.json?screen_name=Dittonoauth_consumer_key=[WITHHELD]oauth_nonce=12427699099383609456oauth_signature=gKSz6qPOiPKrJX6NqLuP7HjBkJ4%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088019oauth_token=[WITHHELD]oauth_version=1.0 Like I said, if I hit up the statuses/home_timeline endpoint it works fine. http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=[WITHHELD]oauth_nonce=4782314729649271771oauth_signature=LGfzsFEyzfHOszTPx1GPSzj%2BTN8%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271086839oauth_token=[WITHHELD]oauth_version=1.0 Anybody have any idears? Thanks! -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] users/lookup and OAuthed Signed requests
That's the link I was looking for. Will play around and figure some of this stuff out. Thanks Raffi! - ryan. On Mon, Apr 12, 2010 at 10:14 AM, Raffi Krikorian ra...@twitter.com wrote: creating oauth signatures is annoyingly subtle, isn't it? i would suggest playing with http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/and verifying the signature base string and signature you're generating to what that emits. On Mon, Apr 12, 2010 at 9:10 AM, ryan baldwin ryanbald...@gmail.comwrote: I'm having a heck of a time getting the users/lookup to work. I keep getting an invalid signature response, however if I try hitting other urls that require authentication (such as statuses/ home_timeline) I get the proper response. The only difference that I can see is that the users/lookup requires a comma separated screen_name param. An example of a call I'm making is as follows: http://api.twitter.com/1/users/lookup.json?screen_name=Ditton,THEO_BROWN,jeff_phillipsoauth_consumer_key=[WITHHELD]oauth_nonce=3702675319114583140oauth_signature=Bjm61%2F0dNQ1YY%2B6DZrKfluh3brk%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088234oauth_token=[WITHHELD]oauth_version=1.0 The above produces a 401. I though perhaps it's because the commas need to be encoded (however the examples I've seen that doesn't seem to be the case). Even if I tried sending up only 1 screen_name, however, it still fails with a 401. http://api.twitter.com/1/users/lookup.json?screen_name=Dittonoauth_consumer_key=[WITHHELD]oauth_nonce=12427699099383609456oauth_signature=gKSz6qPOiPKrJX6NqLuP7HjBkJ4%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088019oauth_token=[WITHHELD]oauth_version=1.0 Like I said, if I hit up the statuses/home_timeline endpoint it works fine. http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=[WITHHELD]oauth_nonce=4782314729649271771oauth_signature=LGfzsFEyzfHOszTPx1GPSzj%2BTN8%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271086839oauth_token=[WITHHELD]oauth_version=1.0 Anybody have any idears? Thanks! -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- To unsubscribe, reply using remove me as the subject.
