Twitter
p/twitter
Communicate and stay connected
Andy Piper

Twitter API v2 — A new Twitter API, built on a completely fresh foundation

Featured
16
Introducing the new Twitter API. Rebuilt from the ground up to deliver new features faster, including the first set of new endpoints and features we’re launching so developers can help the world connect to the public conversation happening on Twitter.
Replies
Best
Andy Piper
We're releasing the first endpoints for the new Twitter API v2 today, including features like access to topic annotations and poll data. You can also see where we are headed via the public API roadmap. https://trello.com/b/myf7rKwV/tw...
Tyler Hall
Quite simply, nope. Developers have been burned too many times by Twitter changing focus and being outright hostile to third-party developers. They lost my trust years ago, and it's going to take more than a blog post announcing a fresh start to gain that trust back. I'm not getting anywhere near this API. Maybe 5-7 years from now, if it's still around and Twitter has finally proven themselves to be trustworthy stewards of the immense power, influence, and data they are privileged enough to control, then maybe I'd consider building on top of their platform again.
Taylor Crane
@rtylerhall I'm surprised this hasn't been directly addressed by the makers. How can you possibly expect developers that have been around for 5+ years to trust building a business on top of the Twitter API? Almost offensive, really.
IRIS
@rtylerhall Every sr dev should know the story of Twitter blowing up their API. While this would be something interesting to play with, I agree that there needs to be a public commitment to the API.
Isaac Moore
@rtylerhall Absolutely - this is a total slap in the face to all of the indie developers whose products Twitter purposely and calculatedly ruined in the last decade.
Tessa Kriesel
@rtylerhall Hey Tyler. I totally understand and can relate to your pain points. I joined Twitter almost 9 months ago now and my goal is to rebuild developer trust. I know that actions taken previously can not be made up for, but I would love to do what I can to help developers now. If you're open to a conversation, I would love to hear your feedback. You do not owe me a thing, but your commentary can be shared internally to help make key changes to make the #TwitterAPI a trusted platform again. My DM's on Twitter are open (https://twitter.com/tessak22) otherwise, happy to connect any way that works for you.
Dwayne Charrington
Interesting to see the API being expanded. Twitter has had a turbulent history with third-party developers and its API. I am curious @andypiper why Twitter did not go down the path of GraphQL. It seems to me a GraphQL API would have made a lot of sense, especially with GitHub using it for their API successfully.
Andy Piper
@dwayne_charrington2 thanks for asking about this! If you dig into the linked Engineering blog post ("Rebuilding Twitter's public API"), you'll see that we are indeed built on top of a GraphQL layer internally, but opted for a more familiar REST interface externally.
Dwayne Charrington
@andypiper Hi Andy, that's why I asked. I was curious why the public API wasn't exposing GraphQL endpoints instead of RESTful ones. It seems like it would make more sense to just have one GraphQL API instead of maintaining a REST API built on top of GraphQL. I know the blog post mentions query complexity concerns, but these are problems that have solutions.
Andy Piper
@dwayne_charrington2 completely understand that. We took the decision that for the majority of our (many) developers, a transition to a changed, but still RESTful, API would be a less heavy lift than a move to GraphQL. You’re completely welcome to comment or offer suggestions via https://twitterdevfeedback.userv...
Oğulcan Girginç
Haven’t even used the API for my personal account and this is why get. There is no way I would trust them considering their history. Thank you for your interest in the Twitter developer platform. Based on our review of your use case, we are unable to approve your developer application at this time. - Applications may be rejected if they are found to be in violation of any section of the Developer Agreement and Policy, Automation Rules, Display Requirements, and/or the Twitter Rules. - We don’t currently allow you to appeal this decision. We are investigating options to allow people who feel they’ve been inappropriately rejected to appeal. Please stay informed for future updates. - We cannot comment on specific applications in public channels, including through official Twitter handles or our developer forum.
Sanket Makhija
Awesome work to integrate with 👍
Rich Paret
Nice work, y’all 🥳
Javier Burón 💾
Amazing release, Way to go! 🚀