Twitter imposes rate limits on how many tweets can be accessed per day. Twitter controls the limits associated with any Twitter account.
If the live feed schedule shows that the date and time of the “next fetch” has already passed, then it likely means that you have exceeded the rate limits set by Twitter. These are Twitter policies, not DiscoverText policies. You can work around this by:
- Running fewer feeds
- Using more Twitter IDs to spread the jobs out over more accounts
- Staggering the start times
- Using less frequent fetches
DiscoverText onlys use the "search" endpoint:
and specifically the standard search API:
which is rate limited as:
- Requests / 15-min window (user auth) 180
- Requests / 15-min window (app auth) 450
All of DiscoverText's requests use the "user auth" (as they are tied to a user's account - hence, the need for the user to authorize their Twitter account to use DiscoverText).
With a DiscoverText enterprise subscription you can store up to 500,000 tweets or other data units. There is no use case review by Twitter as long as you are not doing government work (which is governed by different rules).
To learn more about our limits and pricing, please see:
To customize a monthly package, please see: