i wouldn't necessarily and harshly say "useless" :P it still prevents you from having to make 1000 user/show requests (which you can't do right now).
On Thu, Mar 11, 2010 at 10:59 AM, Michael Steuer <mste...@gmail.com> wrote: > Oh wow, I missed that. I understood it was rate limited at 1000 calls/hour > (which would come out to 20k user objects) > > Having a limit of only 1,000 user objects an hour, renders this new API > pretty useless! Come on! I thought the idea was to give developers who now > do 10's of thousands of user/show calls a more efficient alternative?!?! > > > > On Mar 11, 2010, at 10:11 AM, Abraham Williams <4bra...@gmail.com> wrote: > > My understanding is that it is 50 users/lookup API calls x 20 user objects > per call = 1000 user objects. Not 1000 users/lookup calls of 20 user > objects. > > Abraham > > On Thu, Mar 11, 2010 at 10:06, Michael Steuer < <mste...@gmail.com> > mste...@gmail.com> wrote: > >> >> Erm, doesn’t 20,000 x users/show equate to 1,000 x users/lookup ? >> >> Or are you whitelisted for more than 20,000 API calls an hour? >> >> >> On 3/11/10 9:53 AM, "Abraham Williams" < <http://4bra...@gmail.com> >> 4bra...@gmail.com> wrote: >> >> So for something like Intersect  where I have to do sometimes tens of >> thousands of profile lookups per hour I should stick with users/show? Or can >> I get an account whitelisted for more lookups per hour? >> >> Abraham >> >> On Thu, Mar 11, 2010 at 07:48, Raffi Krikorian <<http://ra...@twitter.com> >> ra...@twitter.com> wrote: >> >> hi all. >> >> we launched an endpoint yesterday that allows you to fetch 20 users by >> user_id or by screen_name at a time -- we call this our "bulk user show" >> API. for example, to retrieve user objects for user IDs 12863272, 3191321, >> 9160152, 8285392 and simultaneously screen names of rsarver and >> wilhelmbierbaum, put together the following authenticated request >> >> <http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,9160152,8285392&screen_name=rsarver,wilhelmbierbaum> >> http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,9160152,8285392&screen_name=rsarver,wilhelmbierbaum >> >> and you will receive an XML array of those six user objects. >> >> you can find more documentation at >> <http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup> >> http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup. >> >> thanks! >> >> > > > -- > Abraham Williams | Community Advocate | <http://abrah.am>http://abrah.am > TwitterOAuth | <http://github.com/abraham/twitteroauth> > http://github.com/abraham/twitteroauth > This email is: [ ] shareable [x] ask first [ ] private. > > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi