Last week we informed the community of our plans to transition to the new Twitter Streaming API. (see the blog post) This post is going to focus on providing some information on how Gnip Filters will be updated in order to support the new requirements of the Streaming API.
Here is a general summary of what Gnip users need to have in mind to prepare for the transition.
1) The Twitter Streaming API uses HTTP Basic Authentication to open up a connection. The authentication requires the Twitter Username:Password combination, and the account access tier is set at the Twitter account level.
2) The default Gnip support provided to users will be to the “spritzer” and “follow” tiers as these are public and can be accessed by any valid Twitter account.
3) Developers and companies that have use cases which require higher levels of access (gardenhose, shadow, birddog) need to send an email directly to Twitter at email@example.com. The email should include basic information about your use case, the access level that is required (gardenhose, shadow, birddog), and the Twitter account to map the access. Also, Twitter has a new URL to request access for the gardenhose level.
Also, to provide a preview of what the new Gnip filters will provide we wanted to include some screen shots of what we are working on at this time. (Also, you will notice the prototypes were built using an updated user experience we are working on for a future release)
Figure 1: Gnip Filter Creation
This is the start page for creating a Gnip filter that will connect to the new Twitter Streaming API. Users now will need to provide a valid Twitter account in order to support the HTTP Basic Authentication requirements of the API.
Figure 2: Gnip Filters will support the multiple tiers of the Twitter Streaming API
Twitter has multiple tiers for the Streaming API which will be supported in this update to the Gnip filters. In the developer web app or at the Gnip API it will be possible to select the Streaming API tier that the filter will access.