We’re currently hard at work to make Twitter better for everyone, including developers! We’ve decided to cancel the #Chirp developer conference while we build some things that we’re excited to share with you soon.
We’ll still celebrate the soon-to-be-announced winners of our Chirp Developer Challenge - stay tuned for more details!
As always, we’re just a Tweet away, so feel free to reach out with any questions. We’re grateful for your partnership to #BuildWhatsNext
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The time has finally come - you can now Tweet using the Twitter API v2!
We heard your feedback, and have added several new, highly requested API features. Read on (🧵) or check out the forum post: twittercommunity.com/t/announcing-m…
Academics are one of the biggest groups using the #TwitterAPI to research what’s happening. Their work helps make the world (& Twitter) a better place, and now more than ever, we must enable more of it.
Introducing 🥁 the Academic Research product track! blog.twitter.com/developer/en_u…
Feedback from hundreds of researchers around the world helped shape what’s launching today:
• The full history of public conversation data ⌛
• A higher Tweet cap 📈
• Advanced filtering ability 🔍
• Technical resources 🧑💻
• And all available for free 🎉
To get started, new and returning developers must submit an Academic Research application. This process helps us make sure that access to this data will be used safely, securely, and in line with our Developer Policy.
Your feedback over the past few years has played a huge role in helping shape what we're building. You helped us better understand what you want to accomplish with the Twitter API and where we can support you better.
Twitter launched in 2006, and just a few months later, the Twitter API was released. 🎉
The first s̶e̶t̶ ̶o̶f̶ ̶d̶o̶c̶s̶ doc for v1 looked like this 👇
Twurl, Twitter’s curl-like application, arrived in 2009. Twurl is specifically tailored for the #TwitterAPI — seriously, you can do so much with Twurl. It’s like the Swiss Army Knife for the Twitter APIs.
In 2011 our official #TwitterAPI documentation site launched. Up until then, developers were using Google Groups for discussions and solving problems. 👀
2️⃣0️⃣1️⃣9️⃣ was a big year for @TwitterDev 🚀
We released Twitter Developer Labs - a new program that enables our developer community to test new features + endpoints, and share feedback before we launch the next generation of the Twitter API. 🧵
Since Labs went live in March, we’ve launched 🤚 new releases for developers to test:
🆕 Tweets and users endpoints: Use these endpoints to quickly lookup Tweets and people on Twitter by ID.