The Twitter Developer Blog

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.Read more…

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

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.Read more…

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.Read more…