- 200 runs (of a given Pipe) in 10 minutes
- 200 runs (of any Pipe) from an IP in 10 minutes
- If you exceed the 200 runs in a 10 minute block, your Pipe will be 999'ed for a hour (a 999 error implies you are over utilizing our service)
Twitter rate limits Yahoo! Pipes based on server IP. Within the Pipes network, there are X servers - each have unique IP, and get rotated when an IP reaches the rate limit of 20k requests per hour; if the IP rotation concludes before all Pipes have had a chance to run, the remaining Pipes will be blocked.
In order to make authorized calls to the Twitter API, your application must first obtain an OAuth access token on behalf of a Twitter user. The way you will obtain such tokens will depend on your use case. (See the usage table here.)
The Search API is not complete index of all tweets, but instead an index of recent tweets. At the moment that index includes between 6-9 days of tweets. You cannot use the Search API to find tweets older than about a week.
Search does not support authentication meaning all queries are made anonymously. This also means there is no OAuth requirement.
The Rate Limits for the Search API are not the same as for the REST API. When using the Search API you are not restricted by a certain number of API requests per hour, but instead by the complexity and frequency.
As requests to the Search API are anonymous, the rate limit is measured against the requesting client IP.
If you use your own OAuth tokens to access the Twitter API, you have more control, because you're not sharing your calls with the Yahoo! Pipes network.
You can use YQL to sign Twitter OAuth calls and then tie that in to a Pipe.
From twitter API v1.1, search API also needs access token, isn't it? In this case, do you have an example for YQL + Twitter + Pipes integration?