Tumblr Introduces New Features In v2 API
Tumblr <a href="https://engineering.tumblr.com/post/7541361718/introducing-tumblrs-new-api" target="_blank" rel="noopener noreferrer">Tumblr Engineering — Introducing Tumblr's New API</a> a new API for 3rd party app developers on it's official tumblr Engineering Blog.
The new features of the API are:
<ul>
[*]An application can access list of blogs a user is following, once authorized by the user.
[*]Ability to upload multiple photos to create Photoset posts.
[*]Get Blog Info by pulling a blogâs description, avatar, and last-update time.
</ul>
#-Link-Snipped-#
To make developersâ lives easier, Tumblr has consolidated all API access to <code>api.tumblr.com</code> that has made their two major concepts in the URI: <code>/blog</code> and <code>/user</code>, clearly visible, which has made it possible to measure and balance traffic using DNS and other mechanisms. Opposed to this, the previous API differentiated between read and write operations, and pushed different activity onto different domains. (<code><a href="https://www.tumblr.com/" target="_blank" rel="noopener noreferrer">Trending topics on Tumblr</a></code> and the blog subdomain)
The blog says that they would like the users to focus on experimenting on the new API instead of going through the piles of #-Link-Snipped-# (which are still available if the users need exact description of terms)
Moreover, Tumblr now provides support for developers composing simple URLs instead of relying on REST (Representational State Transfer). For example, if users want to get a bigger avatar, they just need to write the size at the end of the URL and it's there: #-Link-Snipped-#
They have also eliminated XML support from the API, (inspired from Facebook)Â and are working on its JSON implementation for developers.
Earlier API allowed developers to store passwords on behalf of users. Eliminating that, in the new API, OAuth 1.0a is now required to access all non-public data and they are planning to make OAuth 2 available in near future.