Twitter traditionally has had a rocky relationship with its developer group. The social media platform is making an attempt to reset developer relations but once more with the unveiling of its imaginative and prescient for the Twitter API platform and, for the primary time, publishing its public road map of what it has deliberate.
The apparent goal here is to be more transparent about what the social platform has in store for developers, which includes a unification of its API platform along with the launching of new APIs and endpoints for developers.
The acquisition, however, divided the developer base into different classes. Most developers continue to utilize the standard REST and real-time streaming APIs that have been around since 2006. Meanwhile, larger software companies could take advantage of Gnip’s enterprise-grade APIs to do more with Twitter data.
The APIs will be streamlined, so developers won’t have to deal with different access points and delivery protocols as they scale.
“This implies one API for filtering knowledge from the Firehose; one API for looking the Twitter archive; one API for getting realtime actions associated to an account — together with Tweets, Direct Messages, Likes & Follows,” writes Andy Piper, Employees Developer Advocate