You mention 150/hour so I am guessing that you are not authenticating
with Twitter. This means that if there are any other applications
sharing the same IP address (shared hosting) then they are also using
the same rate limit as your app. If you authenticate you will get the
250/hour ratelimit and it will be all yours to consume.


On Nov 1, 6:06 pm, PeterElsner <> wrote:
> I've written a small app for use with some auction software.  All this
> app does is run via cron every 2 hours and picks a random auction
> (that is open) and then posts it to my twitter page using OAuth.
> This works great, and many times it does update just fine.  However
> occasionally, I get a failed response back from Twitter stating
> 403 - Request has been refused. Possible causes: denied due to update
> limits.
> Since my cron only runs every 2 hours, then I am only submitting 12
> tweets to my Twitter page in a 24 hour period...
> That's certainly less than the 150/hour or the 1000/day that is listed
> in the wiki.
> My script/app does not do any deleting, following etc... It just sends
> an update to my page with a random auction listing.   So in a 24 hour
> period, I get on average about 8 successful tweets instead of the 12 I
> should be getting.
> I'm just wondering if there is something else that the 403 could be
> representing other than update limits.  Perhaps Twitter itself is over
> loaded?  If that is the case, should it not provide a different error
> code???
> Something that says "Twitter is busy right now, try again later",
> instead of the rate limit error which makes it sound like there's
> something wrong with my script/app.
> I sent an email to and the response was to come and
> ask here.
> If anyone wants to see the code, it can be downloaded 
> from
> Thanks in advance,
> Peter Elsner

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to