Twitter Goes JSON-Only With One API, More to Come?

Anyone requesting XML from the Twitter streaming API better switch to JSON as soon as possible. Starting in early December, the microblogging service will only send JSON-formatted responses from its popular new streaming API, the recommended way to get search results as they happen.

Twitter's Taylor Singletary explains the change:

We will end support for XML on all Streaming APIs on Dec 6th, 2010, after encouraging developers to use JSON-based output formats for some time now. This deprecation does not apply to the REST or Search APIs, but all clients requesting XML from, regardless of role and method
(sample, filter, follow, etc) will be affected.

As the announcement says, this currently does not affect other APIs, such as the Twitter Search API or the flagship Twitter API, which supplies user timelines and other data. However, we have to expect that this is a sign of future changes. Singletary points out that Twitter's newest APIs only use JSON, which pushes further the argument that an XML-less Twitter API is in the cards.

We called these newer streaming APIs a glimpse of the future of real-time. It seems that future may not have XML. After all, JSON is the developer's choice.


Comments (7)

[...] interest this week in the XML versus JSON debate. We had earlier reported that come early December, Twitter plans to stop support for XML in its Streaming API. So in case you are late into this news, the deadline is Dec 6th. If your app still expects XML, [...]

[...] TalkA podcast by developers for developerslinks for 2010-11-15by delicious on November 15, 2010Twitter Goes JSON-Only With One API, More to Come?Learning PHP: Working with Conditional Statements301 Redirect or Rel=Canonical – Which One [...]

[...] face à XML en qualifiant le choix des éditeurs de presque unanimes. Certains géants comme Twitter ont même annoncé l’arrêt futur d’XML. Après le recul des Webservices SOAP face à REST par les ténors du Web tels que Google, voici [...]

The bandwidth savings of removing XML API calls and responses is fairly substantial given the number of third party applications.

Has twitter considered YAML?