We are a recently approved Premium API developer with some questions about rate limits.
Our application is a Twitter-feed widget that is embedded on websites for live television shows. While the show airs, the audience uses our widget to:
- view Tweets from (or mentioning) the show’s Twitter account
- view Tweets matching keywords supplied by the show (e.g., a guest’s name for a talk show)
- send Tweets mentioning the show (the mention allows the show’s producers to easily see Tweets from viewers during the show)
After launching our app on the free Twitter API, we started hitting a request limit and were blocked from writing (sending Tweets). To address these issues, we joined the Premium API.
However, now that we can see the available paid Premium products, none of them seem to apply to our situation. Specifically,
“Search Tweets: 30-Days”:
We don’t need to search back 30 days. We just need recent Tweets (results from the last hour or so is plenty).
“Search Tweets: Full Archive”:
We don’t need access to the full archive.
“Account Activity API”:
We don’t need to “subscribe to real-time delivery of an account’s activities.”
We currently retrieve Tweets using the /search/tweets.json endpoint, which is perfect for our needs except for the request-rate limitation to which we are currently being subjected.
We’d like to avoid signing up for a paid product that won’t actually address our needs, so we’re seeking guidance on how to proceed.
Is there a Premium product that will simply increase the request limit for /search/tweets.json?
Is there a Premium account representative that can explain why we were write-blocked, and guide us to the product that would reinstate our ability to send messages via https://api.twitter.com/1.1/statuses/update.json?
Other than exceeding request-rate limits, we believe we are not violating any API usage rules, so we have already contacted Twitter via the Twitter API Policy Support form (https://support.twitter.com/forms/platform) asking for more details. So far we have not received a response beyond the automated boilerplate email.
Thanks for any advice you can offer.