Too Many Requests

Question

travisfisher opened this issue 10 years ago · comments

Due to Twitter's API rate limit restrictions on "https://api.twitter.com/1.1/account/verify_credentials.json" (15 per 15 min), it may be beneficial to lookup the user profile using "https://api.twitter.com/1.1/users/show.json" instead (180 per 15 min).

Right now, I'm getting a "Too Many Requests" response from Twitter if I don't cache the data.

Luciano Mammino · Answer 1 · Fri Oct 17 2014 20:43:50 GMT+0800 (China Standard Time)

Hi @tgfisher,
Great suggestion, seem very reasonable. Would you like to submit a pull request?

And · Answer 2 · Thu Apr 16 2015 04:32:37 GMT+0800 (China Standard Time)

Why don't use application cache for this? Library is not about caching.