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> 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" <4bra...@gmail.com> wrote:
>
> So for something like Intersect [1] 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 <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
>
> 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.
>
> thanks!
>
>


-- 
Abraham Williams | Community Advocate | http://abrah.am
TwitterOAuth | http://github.com/abraham/twitteroauth
This email is: [ ] shareable [x] ask first [ ] private.

Reply via email to