The Twitter Developer Blog

Your source for new features, best practices and real-world use of the Twitter Platform.

Results from Developer for: March 2013

API v1 Retirement: Final Dates

The Twitter REST API v1 will officially retire on Tuesday, May 7, 2013. (See API v1 Retirement Date Extended to June 11, 2013)

We will hold another blackout test on April 16, 2013 beginning at 23:00 UTC (4:00pm PDT). Depending on the results of that blackout test, we may announce an additional test before the final retirement date.

There’s a lot to keep track of in this migration. Here’s a recap:


A Special Platform Event

We’re working on new Twitter platform features that we’d like to share with you at an upcoming mobile-focused event. If you’re a developer, product manager, designer, etc., working on a product with a mobile presence, then please join us at Twitter HQ on the evening of April 2nd, from 6:30pm to 9pm.

The content will cover how you can best integrate Twitter into your mobile experience. We’ll have limited space, so please register to attend:


Changes to following caps and message ordering for Site and User Streams

Our Site Streams feed was introduced as a limited beta in August 2010. It is a powerful service which allows an application to read a stream of Tweets and social events for a set of authenticating users. With the inclusion of an optional with=followings parameter, Tweets and social events from all the users the connected user is following are also streamed.


API v1 Retirement Update: Blackout Tests, OEmbed, & Streaming API edition

Now that application-only authentication is released, we wanted to give you an update on the ongoing gradual retirement of API v1.


Do applications dream of authenticated requests?

People — our users — are central to everything at Twitter. Users read, retweet, favorite, and compose tweets. They follow other users and search for what’s meaningful to them. The user is the primary agent of the Twitter experience, in all its varieties.

Applications built on the Twitter REST API are typically vehicles for user interaction with Twitter, but we recognize that applications may sometimes need to interact with Twitter on their own behalf, without bearing a user context.