Some #TwitterAPI Trivia
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 👇
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.
developer.twitter.com/en/docs/tutori…
developer.twitter.com/en/docs/tutori…
In 2011 our official #TwitterAPI documentation site launched. Up until then, developers were using Google Groups for discussions and solving problems. 👀
developer.twitter.com/en/docs
developer.twitter.com/en/docs
In 2012, a year after our official docs launched, v1.1 was released. This was the first major update to the #TwitterAPI in 6 years.
Since then, we've introduced premium and enterprise access, but the v1.1 foundations remain the same... but that won't be the case forever.
Since then, we've introduced premium and enterprise access, but the v1.1 foundations remain the same... but that won't be the case forever.
Last year, we adopted a new approach - building our 🆕 API in the open with the launch of Twitter Developer Labs.
With Labs, you can test new endpoints and features before they launch. Here’s a recap of what we’ve learned over the last year.
With Labs, you can test new endpoints and features before they launch. Here’s a recap of what we’ve learned over the last year.
Thank you to all of you who have engaged with us and shared your feedback. Your input has been vital, and we’re committed to continuing these conversations with you.
There’s so much more we’re doing to build a better #TwitterAPI… and Early Access is coming tomorrow! ✨
There’s so much more we’re doing to build a better #TwitterAPI… and Early Access is coming tomorrow! ✨
