Gnip Support
Historical PowerTrack API - metadata and filtering timeline
posted on 02 June 2017 by Jim Moffitt
Introduction How Twitter evolved as a platform, and how that affected the JavaScript Object Notation (JSON) used to encode Tweets, is discussed here. That article also begins the discussion of how these JSON details affect creating the filters needed to find your historical data of interest. This article continues that discussion by exploring how these details affect writing filters for Historical PowerTrack. This, and a complementary article about Full-Archive Search, will serve as a ‘compare and contrast’ discussion of the two Twitter historical products. Product Overview The Historical PowerTrack (HPT) API brings the same filtering capabilities developed for real-time streaming... keep reading
Tweet Metadata Timeline
The evolution of Twitter and its Tweet JSON metadata, and how that affects finding your historical signal of interest.
25 May 2017
Rule Limits
Information on managing rule limits.
18 January 2017
Migrating Code to Gnip 2.0
A guide for migrating code to Gnip 2.0 products.
22 August 2016
See More
Building your app?
Get going quickly with our code examples
PowerTrack / Firehose Stream
Connect to the PowerTrack and Firehose streams.
PowerTrack Rule Management
Add, delete, and list rules on the PowerTrack Rules API.
Historical PowerTrack
Create and manage Historical PowerTrack jobs.
Search API
Send Search and Counts requests to the Search API.
Engagement API
Request engagement metrics for specific Tweet IDs.
Audience API
Request audience demographics for specific UserID groupings.
Data Collector Stream
Connect to the streaming endpoint of Data Collector streams.
Data Collector Polling
Retrieve data from your Data Collector with GET polling.
Data Collector Rule Management
Add, delete, and list rules on your Data Collector feeds.