I run a web analytics service that includes a Twitter analytics feature, where you can input a search term and we regularly poll the API for new results. We’ve had this feature for almost 4 years now and over that time we’ve had over 16,000 searches created on our end, currently 7500 of those are active.
The current search API 1.0 limits have worked fine for us even as we have scaled up to this many searches. We essentially grab a random subset of the searches every 5 minutes and hit the API until you tell us the limits have been reached. Then the script exits and we wait the proper amount of requested time until starting up again.
I don’t know how many queries per hour we send to the API but it’s definitely several thousand at least.
The new search API 1.1 is currently listed as being throttled to 180 per 15 minutes, so 720 per hour. This is really going to limit the usefulness of our Twitter integration, as it will take 10 hours to run through and update all of the searches we’ve added, and that will only get worse.
I know, you all want to cry me a river. But my point is this.
We are perfectly willing and able to pay money for higher API limits, as I’m sure many other developers are as well. I wouldn’t even bat an eye at paying Twitter $1,000/month for considerably higher limits, say 3000 or 5000 queries per hour. Just 1,000 developers paying you this amount of money would generate $1,000,000 of revenue per month, or $12,000,000 per year, and this is a very conservative estimate in my opinion.
Please consider doing this. You will make us developers very happy and you will generate a good amount of extra revenue as well.