0

I haven't worked with the Twitter API before.

I have a Sinatra application pushed to Heroku, which makes use of the Twitter gem. The only thing I do in the application (as far as Twitter is concerned) is to pull my 5 latest tweets.

  @tweets = Twitter.user_timeline("username").first(5)

However, last night I had trouble getting it to work, Heroku threw an internal server error and the logs tell me: 

2011-12-03T11:30:08+00:00 app[web.1]: Twitter::Error::BadRequest - : Rate limit exceeded. Clients may not make more than 150 requests per hour.:

and a stack trace. Restarting the app made it work again.

Today I woke up, checked my heroku app and I got the internal server error again..

What can I do to make this work? Is there a way to make it cache the tweets in case it throws a BadRequest error, or is there a way to get unlimited (or nearly unlimited) requests to Twitter?

I'm not authenticating or anything. Bit confused.

lucapette
  • 20,564
  • 6
  • 65
  • 59
Joris Ooms
  • 11,880
  • 17
  • 67
  • 124

1 Answers1

2

It seems that you've met Twitter's Rate limit for unauth users/accounts:

The REST API does account- and IP-based rate limiting. Unauthenticated calls are permitted 150 requests per hour. Unauthenticated calls are measured against the public facing IP of the server or device making the request.

Try to use OAuth authentication:

OAuth calls are permitted 350 requests per hour and are measured against the oauth_token used in the request.

WarHog
  • 8,622
  • 2
  • 29
  • 23
  • Cool. Thanks, I'll try that. Weird though, I just woke up and I don't think anyone has visited my site while I was asleep, yet I got the error. – Joris Ooms Dec 03 '11 at 11:53
  • Maybe someone else within you network was having access to the feeds during that hour? Who knows? ) – WarHog Dec 03 '11 at 12:03
  • True, might be possible. I'll add the OAuth authentication and try again :) Thanks a bunch for the quick reply! – Joris Ooms Dec 03 '11 at 14:17