Hi Michael, Thanks you for your response. The error does not specify the reason (see below), but it does show when 'get status' method is being executed for an user ID that is has not been whitelisted; we cannot possibly whitelist all application users.
ERROR: "Rate limit exceeded. Clients may not make more than 150 requests per hour." We whitelisted our IP address; the response from Twitter stated that our IP address and twitter @user_id (that we used to submit the form) has been whitelisted (we did not ask for @user_id to be whitelisted, but Twitter whitelisted it anyway). The application is using user standard methods (get a status, update a status, get user screen name, etc.) for various users who use the application, but the initial login within the application code is done with the whitelisted user id. What's the common way of doing this task? In other words, how would somebody like HootSuite would approach this? They are getting thousands of status, screen name, etc. per minute it seems. I think we are missing something obvious. Thank you, -Stas On Nov 23, 2:56 pm, Michael Steuer <[email protected]> wrote: > Youre seeing rate limit errors for unauthenticated calls from that ip > address, or when you authenticated calls for a user that's not > whitelisted? > > On Nov 23, 2009, at 10:30 AM, Stas <[email protected]> wrote: > > > We have received whitelisting approval from Twitter, but seems it is > > applicable to the @name and the IP. > > Given that we still get "rate limit" errors, should we just whitelist > > the IP? > > > If so, what is the process of changing the whitelisting options? > > > Thank you, > > -Stas
