The Twitter Developer Blog

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

Results from Developer for: 2013

List IDs to become 64-bit integers in early 2014

We’re proactively making room for more lists on Twitter by expanding their IDs to 64-bit integers. If you’re using our REST and Streaming APIs, you should confirm that your database, server-side and client-side code consume the safe string-based identifiers represented in “id_str” fields instead of the integer-based identifiers found in the “id” field of Twitter List objects and related references.


REST API SSL certificate updates

At the end of 2013, all Browsers and Certificate Authorities will no longer support 1024 bits RSA certificates to be compliant to National Institute of Standards and Technology (NIST) guidelines.

The SSL certificate currently used on is signed with the older Verisign G2 root CA certificate.


Introducing custom timelines: create timelines of Tweets for everyone

Today we’re introducing custom timelines to give you more control over how Tweets are organized and delivered on the Twitter platform.


Streaming SSL certificate updates

If you use our streaming APIs, you should be aware of a change that’s coming in a couple months: We are updating the SSL certificates for and on November 4, 2013.


Test accounts with user IDs greater than 32 bits

For a variety of reasons, the numbers used to identify accounts via Twitter’s API grow faster than the actual number of accounts in the system. Currently, user IDs fit in 32 bits—a standard size for integers on many platforms. In January, we explained that the current pace of Twitter user ID allocation meant that we’d exceed 32 bits sometime this year. All developers should make sure their code will handle the switch.


Headlines tell the story behind the Tweet

Hundreds of thousands of websites and publishers embed Tweets to share the best of Twitter with their readers. From world news, to sports, politics and entertainment, Tweets have changed the way breaking news is covered. And they help people everywhere discover important Tweets, even outside of Twitter.


API v1 Retirement is Complete - Use API v1.1

Today, we are retiring API v1 and fully transitioning to API v1.1. Given the array of blackout tests, blogposts, 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.


Twitter Certified Products Program Expansion

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.


Crashlytics for Android: Find the droid crashes you’re looking for

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.


API Blackout Testing on May 22, 2013

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.