Developers Blog and the Retirement of the API v1

[John Bunting]

Hey all,

I've setup a blog for announcements and change logs over at
http://developers.tumblr.com.

You'll see that the retirement of the v1 API is going to be the first
announcement. I want to use this thread to help gather information
about how we can make this transition smoother for all of you.

Please let me know if you guys need anything.

~John B

[Kyle Zaragoza]

The first thing that should be added is the ability to post/read private blogs.  In API v1 I could post to private blogs, as far as I know we're still not able to do this in v2, this is by far the most requested feature from users.  Second, should be support for tracking tags.

[Phong Le]

I'm really surprise they didn't really add tracking tags when they released API v2. This is a big feature that many users really would appreciate.

[Steven Pears]

Thanks for the heads up John, and it's great to see a developer blog!

 

I'm pretty sure being able to use the markdown flag when posting is the only issue in the V2 API I've got to deal with before I can look at releasing the new DashBuddy code.

 

Steven

[Daniel Jalkut]

John - please consider restoring the original behavior of the V1 API, accepting authentication via query parameters, until the official September 1, 2012 phase-out date for authenticated access is reached. Currently you are causing several apps to malfunction and generating bad PR for Tumblr and 3rd party developers. At least by restoring the original functionality for the last-hurrah this month, apps that are already deployed will continue to work while we scramble to get things updated to the 2.0 API.

Daniel

[Oliver Fürniß]

Agree with Daniel, please restore the v1 API. This gives me the time to migrate to v2, instead of writing support mails why the login is no longer working. 

[hostj2me]

Any plans to create an API showcase where devs can showoff their API based creations?

[mrjason]

Our users continue to ask for the ability to search tags site wide, as the tumblr app recently added. Users don't want to look at #lol on one blog, they want to see the same content they see on tumblr.com/tagged/lol.

As others have said, privat blog posting and/or reading is a popular request.

And of course users are constantly asking to view more than 300 posts on their dashboard, we can appreciate the computational impact of that request though :)

- Jason

[Nick]

Dev blog is very cool, thanks!

With the retirement of API v1, the main feature I'll be missing is the ability to query for posts (via /read) without using an API key. AFAIK /posts on v2 requires an API key.

Are their plans to be able access to /posts without using an API key? If this was this a completely intentional decision, I understand, just curious.

FWIW this is small functionality I need for https://github.com/bicknoyle/jquery.tumblr, which I currently only use with one project for one of my clients. I will bluntly ask - if this is the sort of usage API v2 is aiming to curtail, let me know, and I'll let them know :)

On Thursday, August 2, 2012 10:58:44 AM UTC-4, John Bunting wrote:

[Daniel Jalkut]

I would like to add my vote for supporting reading of private posts via the 2.0 API. Is it just an oversight that it's not supported, or an intentional restriction? I note that I am able to submit a post through the 2.0 API with "private=1" and it submits the post to the site as expected, it just never comes back in the /posts array, and there doesn't seem to be e.g. a /posts/private endpoint that returns them, either.

Daniel

On Thursday, August 2, 2012 10:58:44 AM UTC-4, John Bunting wrote:

[Steven Pears]

John

 

Transparency PNG for your logo? Just gave me a great edge case on my mobile app's black background - never would have thought of testing that one, cheers! :)