Today, we are retiring API v1 and fully transitioning to API v1.1. Given the array of blackout tests, blog posts, Tweets and other updates, this should (hopefully) not be a surprise. Before I get into the slew of resources available for you, let me first say thank you for your cooperation over the last several months.
Today, we’re introducing 11 new Twitter Certified Products. Since we introduced the program last summer, our goal has been to help businesses find tools and services that make them more successful on Twitter. To date, Certified Products have been largely U.S.-focused; this new group includes companies from Europe, Japan and Latin America –– extending the program’s global footprint and empowering brands and publishers around the world.
To build stable, robust applications, you need to understand when, why, and under what conditions your apps may crash. On the Android platform, variations in hardware, along with the multitude of in-market OS variants running your apps, make it even harder to identify and resolve crashes.
In further preparation for the retirement of API v1 on June 11, 2013, we'll be conducting another blackout test on May 22nd, 2013 from approximately 20:00 UTC to 21:00 UTC (1pm to 2pm Pacific).
During the blackout test, API v1 will respond to authenticated & unauthenticated requests with "HTTP 410 Gone". Please read this post for a more complete accounting of what to expect.
Engineers here at Twitter are always looking for ways to increase efficiency and simplify our codebase. To that end, we're deprecating HTTP 1.0 support for all streaming API endpoints. While our streaming API continues to grow, this version of the protocol is rarely used. Also, its successor (HTTP 1.1, introduced in 1999) offers features that are useful for streamed responses.
We're extending the API v1 retirement date from May 7, 2013 to June 11, 2013, in order to accommodate additional blackout testing.
You can find a recap of what to expect on the final retirement date here. We'll announce the date and time of the next blackout test from @twitterapi soon.
The first few months of 2013 brought a number of changes to the Twitter platform. In case you haven't kept up with our recent announcements, here are some key highlights.
The Retirement of API v1
Several major milestones relating to the deprecation of API v1, which was announced last fall, have occurred during the first quarter of 2013.
When the Tweet button was introduced in 2010, Microsoft’s Internet Explorer 6 was our baseline. Now, most users have upgraded and we see IE6 usage dwindled. On May 13th 2013, we’re going to prune our support for that browser and its successor, IE7.
Twitter auto-links financial symbols (which look like $FOO) in Tweet text. These parsed symbols will soon be made available via the API under the Tweet "entities" object. Sections of text which match a dollar sign ($) followed by a word identifier will show up under the "entities/symbols" key. For example:
Twitter Cards are being used by more than 10,000 developers, mobile apps and websites to richly represent content on Twitter, including article summaries, user-posted photos, videos, songs, and more. Today, through those Cards, we're introducing a new way to bring people directly to your app from a Tweet, and we're adding new types of Cards, so you can more creatively show your content on Twitter.