Does the PowerTrack API allow multiple streams

[GregDentEpi]

We are currently considering upgrading to an enterprise account to help mitigate issues with rate limits and logins. The PowerTrack API seems like a good fit for us… however, I notice that the documentation seems to all be centered around having a single stream with multiple connections to it that each get all the tweets for all the connections. We have an enterprise model with a server at each client site, and we would like to have a separate stream for each installation so that we don’t have to have each client fight with the others for data. Is this allowed? If not, it does not seem like a paid account is worth it for us.

As a corollary, I may be confused about what exactly “a request” is with regards to the PowerTrack api. The documentation says that it is limited to “60 requests per minute”, but that sounds awfully low to me, so I maybe don’t understand what you mean by “a request”. Is a request a request for new connection, or simply a search, or maybe something else? For example, if we are limited to 60 searches per minute, that could easily be exceeded by different enterprise users around the world all searching for something at the same time.

[happycamper]

@GregDentEpi - most enterprise customers use the rule tag feature in order to parse and sort which rules belong to each of their clients within their own software. Rule tags can be any string up to 255 characters long and most will use their own internal identifier and then manage the data delivery within their software, rather than directly from the PowerTrack stream itself.

Multiple streams (each with a different rule set) is possible, however there are extra costs for each additional stream. Many clients will set up two streams in order to have one set up fro ‘production’ and the other set up for ‘development’ and manage accordingly on their side.

The ‘request’ for a PowerTrack stream is either the connection to the stream, or a request to the rules management API. Rules can be added/removed from the stream while the connection is still active, there is no need to disconnect when a new rule needs to be added and there can be several thousand rules on a single stream.

[happycamper]