See Inline:

On Fri, Sep 25, 2009 at 4:21 PM, HardipSingh <> wrote:
> We are launching some code next week that will be using the API to
> post updates for multiple twitter accounts.  In preparation for our
> launch, I want to make sure that we're not going to get burned by rate
> limits.  While reading over the documentation, a few questions came
> up.
> My questions are as follows:
> 1) On this page -->, it
> states that updates via http post do not affect rate limits.
> Yet, on this page..,
> it states that ..there is a rate limit of "1,000 total updates per
> day, on any and all devices (web, mobile web, phone, API, etc. )".
> From my understanding, this means that there is no restriction on how
> many update requests come from a single IP.  There is, however, a
> limit on how many updates a single account can post.
> Is this correct?

That is correct.

> 2) I understand that there is a rate limit of 1000 updates per day per
> account.  The documentation also states that getting whitelisted does
> not remove this limit since this is done on a per account basis.  Does
> this mean that there is no way to post more than 1000 updates a day
> from a single account regardless of whether or not we get
> whitelisted?

Also correct.

> 3)  On the Whitelisting form, it states.. "Whitelisting is only
> available to developers and to applications in production; all other
> requests are rejected.".  Since our code is not actually live yet, but
> is set to go live next week, does this mean that there is no way to
> get whitelisted beforehand?  Also, if we were to get whitelisted
> beforehand, do we have to do this per account, or per ip address?

If you have a preview version available, you can add the URL in the
whitelist request form, otherwise you must wait until you are in
production, otherwise we cannot gauge the app. Typically applications
are whitelisted by IP, we do not do bulk account whitelisting.

> That's all I have for now.  Thanks in advance for your time.


Reply via email to