Hi, Basic Auth will continue to work for an unspecified amount of time. Obviously we would push you to work toward an OAuth solution, now that it's public, but we will not remove support without a reasonable runway.
> 1. Upon OAuth going public, will Basic Auth be discontinued? Reason: I > am working on some internal desktop applications (non public and non > spam) and thus OAuth is not really required. No. > 2. In the 100 API calls per hr, are POST requests also included (like > create, destroy, update etc) You are correct, search requests and REST API requests are currently separate. 20 search requests in an hour is reasonable. Query away! > 3. I assume search API requests are not a part of the 100 API call > limit (which is for the REST API), is running about 20 search request > spread out over an hour a reasonable one? Rather than giving a number, please just post meaningful and valuable updates. If you are following these reasonable standards you shouldn't run into a problems. > 4. I see the 1000 updates limit, is the 1000 updates per IP or per > account. Trying to know the limitation, not learning to spam ..... if > it is per account and answer to question 2 is "POST requests are not > limited", then "A system (IP) could post upto 1000 updates per account > without using any of the 100 per hour api quota" is this right? > > I could apply for whitelisting and try these, but I want to design the > app to work within the 100 api limitation. Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Mar 17, 2009 at 12:42 AM, API_Tester <[email protected]> wrote: > > Hi, > > I realize that answers to my question might be discussed somewhere > already, if so please pardon my redundant questions. > > 1. Upon OAuth going public, will Basic Auth be discontinued? Reason: I > am working on some internal desktop applications (non public and non > spam) and thus OAuth is not really required. > > 2. In the 100 API calls per hr, are POST requests also included (like > create, destroy, update etc) > > 3. I assume search API requests are not a part of the 100 API call > limit (which is for the REST API), is running about 20 search request > spread out over an hour a reasonable one? > > 4. I see the 1000 updates limit, is the 1000 updates per IP or per > account. Trying to know the limitation, not learning to spam ..... if > it is per account and answer to question 2 is "POST requests are not > limited", then "A system (IP) could post upto 1000 updates per account > without using any of the 100 per hour api quota" is this right? > > I could apply for whitelisting and try these, but I want to design the > app to work within the 100 api limitation. > > Thanks for your time. >
