In 2019, we launched Twitter Developer Labs as a new program to enable our developer community to test new features and endpoints—and, importantly, to share feedback—as we build the next generation of the Twitter API (coming VERY soon).
Labs has been invaluable in helping us understand what works well and what doesn’t, what you liked and what you didn’t. Throughout the year, we’ve listened to your thoughts across our community forum, UserVoice, and in hundreds of 1:1 conversations. We’ve also closely monitored feature and endpoint usage to see what changes resonated and we adapted as a result.
Labs has given us a space to test out new ideas, shape design decisions, and play with new endpoint structure.
Since introducing Labs in May of 2019, we’ve released and tested the following API features:
Additions to the Tweet object:
Before we launch the new Twitter API and graduate many of these features from Labs, we want to share a bit about how feedback in Labs has influenced the development of these features. Here are a few examples of what we’ve learned over the past year.
Understanding the need for more access options
We’ve always known that our developer ecosystem is diverse, but our Twitter API didn’t address this well. In fact, you could say our API has taken a one-size-fits-all approach. Over the course of the past few years, through many conversations with developers, we’ve learned just how limiting our pricing and rate limit models are for many types of developers: especially academic researchers and developers building for fun. Our next generation of the Twitter API takes this challenge head on. We can’t wait to share what we have planned.
Parity with the Twitter service
We’ve long heard requests for features available on Twitter that we have not enabled in the API. And your feedback throughout Labs further emphasized all of the differences and value of these features for your app and users.
A few of the most common feature requests we heard, included:
The features above are planned within the new Twitter API and we’ll be sharing more soon as we update our public product roadmap.
Endpoints, fields and expansions
With Labs, we introduced a new endpoint format standardizing the rendering of fields, expansions, and annotations. As we released these, feedback poured in about ideas and changes to make them even easier to use. A few of our favorite requests, all of which have been incorporated with the current Labs offerings, include:
We also received specific and guiding feedback about some of the newly introduced Labs endpoint functionality, like:
All of the above are planned for inclusion in the upcoming Twitter API. In fact, one piece of repetitive feedback led us to re-think our approach to delivering metrics data entirely:
We learned that delivering this information via a singular endpoint created extra work for you. As a result, we’ve introduced the metrics data directly into the Tweet object (available in the Labs recent search, Tweets, and users endpoints) and plan to bring this structure to the new Twitter API.
We’d like to extend a giant thank you to all of you who have engaged with us and shared your feedback. Your input has been tremendously helpful in helping us define and align our roadmap with your goals. You’re helping us to build a better API. We’re committed to continuing these conversations with you. Over the next year, we’re investing even more resources and funds into activities to further engage with our community. Keep sharing your ideas and feedback with us and keep an eye on @TwitterDev for updates. There is much more to come… soon!