posted on 14 June 2016 by Stephen Compston, Jim Moffitt
Overview PowerTrack, Volume, and Replay streams utilize Streaming HTTP protocol to deliver data through an open, streaming API connection. Rather than delivering data in batches through repeated requests by your client app, as might be expected from a REST API, a single connection is opened between your app and the API, with new results being sent through that connection whenever new matches occur. This results in a low-latency delivery mechanism that can support very high throughput. The overall interaction between your app and Gnip’s API for these streams is described as follows: Step 1: Configure your stream To configure your... keep reading
Converting Data from JSON to CSV
A Ruby tool for Converting Data from JSON to CSV with Tweet Templates
30 November 2015
Descriptions of types of disconnections that can occur while working with streaming data.
08 May 2015
Storing Dynamic and Static Metadata - Part 3
Storing dynamic and static metadata in relational databases
26 March 2015
Building your app?
Get going quickly with our code examples
Connect to the PowerTrack and Firehose streams.
Add, delete, and list rules on the PowerTrack Rules API.
Create and manage Historical PowerTrack jobs.
Send Search and Counts requests to the Search API.