Hey Dave, Glad to have helped. You know where we are if you have any questions when developing your app. Best, Matt
On Wed, Aug 25, 2010 at 11:30 AM, DaveH <[email protected]> wrote: > Thanks, Matt. > > Since I am still in development I do not need higher limits. So there > is no concern at the moment. Once I am in production it will be an > issue. From what you say here, my recourse is to use the whitelisting > process so seek higher limits when they are needed. > > Thanks for the clarification! > > Dave > > On Aug 24, 6:13 pm, Matt Harris <[email protected]> wrote: >> Hi Dave, >> >> Thanks for the reply, and i'm sorry the documentation didn't answer >> your question. >> >> OAuth does have a rate limit of 350 REST API requests per hour which >> applies mainly to GET requests. This API rate limit is separate to the >> limits you found on the support pages. In fact, the limits on the >> support pages are ones which apply if you use the API or not. >> >> The options you have are this: >> >> If your application requires a higher rate limit you can apply for >> whitelisting using the Whitelisting Request Form. Be aware that >> whitelisting is only available to developers and to applications in >> production though; all other requests are rejected. The link and >> details of what to expect for this can be found in the Whitelisting >> section of the Rate Limiting documentation: >> http://dev.twitter.com/pages/rate-limiting#whitelisting >> >> The alternative is to open a support ticket explaining your situation. >> The user support team will then be able to advise you on what options >> are available. You can open a ticket usinghttp://bit.ly/twicket >> >> Hope that helps, >> Matt >> >> >> >> >> >> On Tue, Aug 24, 2010 at 9:09 AM, DaveH <[email protected]> wrote: >> > Matt: >> >> > Not sure what you want me to pick up in the documentation. I must be >> > missing something. >> >> > When I read the page on daily POST limits [http://support.twitter.com/ >> > forums/10711/entries/15364] I see: >> > <quote> >> > Current Twitter Limits >> > The current technical limits for accounts are: >> >> > Direct Messages: 250 per day. >> > API Requests: 150 per hour. >> > Updates: 1,000 per day. The daily update limit is further broken down >> > into smaller limits for semi-hourly intervals. Retweets are counted as >> > updates. >> > Changes to Account Email: 4 per hour. >> > Following (daily): Please note that this is a technical account limit >> > only, and there are additional rules prohibiting aggressive following >> > behavior. You can find detailed page describing following limits and >> > prohibited behavior on the Follow Limits and Best Practices Page. The >> > technical follow limit is 1,000 per day. >> > Following (account-based): Once an account is following 2,000 other >> > users, additional follow attempts are limited by account-specific >> > ratios. The Follow Limits and Best Practices Page has more >> > information. >> > </quote> >> >> > When I read the page you pointed me to, I see that OAuth calls are 350 >> > per hour. >> >> > So I am still left with the same question, when we hit the daily POST >> > limit, is there a process to ask for an increase? The documentation >> > says it is controlled at a user level, which implies an increase is >> > possible. Yet the documentation does not explicitly say how an >> > increase is requested. >> >> > I am sure the answer is obvious, I just have been unable to find it. >> >> > Looking forward to your reply... >> >> > Dave >> >> -- >> >> Matt Harris >> Developer Advocate, Twitterhttp://twitter.com/themattharris > > -- > 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 > -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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
