Refreshing and bringing together our developer resources

This spring, we announced the unification of our developer platform to make it easier for developers to tap into what’s happening on Twitter, and to build new applications that scale smoothly. As an initial step toward this better experience, today we are launching developer.twitter.com — replacing and bringing together gnip.com and dev.twitter.com — as a complete reference center for Twitter’s developer platform.

The new site will be a hub for all developer resources. Whether integrating with Twitter for the first time, or innovating and scaling solutions for your customers, you can look to developer.twitter.com as a place to learn, to manage tools and APIs, and to engage with the Twitter developer community worldwide.

As a developer myself, I’m excited about this launch because it marks the first deliverable in our plan to unify the developer platform. Here’s my perspective on what the changes mean:

A better learning path to discover APIs and tools

• We're building a better avenue for discovery and education to help you get started, whether your goal is advertising, analysis, publishing and curation, or driving engagement in your product. And—if you’re already familiar with the platform and APIs, we want to help you to branch out and learn more.
• We’ve added pages describing example ways to use the platform in your apps, and highlighted products to help you choose the endpoints and tools that will help you build on Twitter.
• Previously, we wrote about our commitment to building a more integrated experience. The new site will include our Publisher Platform and Twitter Kit tools, Ads APIs, Gnip APIs, and standard REST and streaming APIs — all in one place.

Easier to find the docs you need

The documentation and API reference materials have been reorganized to make it easier to find the endpoints and guidance needed to build on Twitter. Navigate to an endpoint based on object and function (e.g. Tweets > Search Tweets) and find the relevant overview, API reference, tutorials, and more.

Farewell to the API console

As part of the rebuild, we’re saying goodbye to the old API console. The console was a simple but basic way to test queries and did not keep pace with new endpoints. It also did not apply to all of our APIs, such as those for advertising and data. We recommend our command-line tool twurl as a good way to test simple Twitter API queries (and also to validate your keys and tokens), and in the coming months we will add tutorials that cover and explain the use of other common API testing tools such as Postman.

What’s next?

This is the first phase of the unification of the developer platform. This site lays the groundwork for upcoming tools to access and manage new APIs. The documentation will continue to evolve as the Twitter developer platform grows and soon you’ll begin to see guides, more tutorials, a new API status page, and more sample code.

This new resource center also marks the beginning of the transition of Gnip products to the Twitter API platform umbrella. Moving forward, you’ll find them listed with an ‘enterprise’ designation on developer.twitter.com. The new designation is intended to make the subscription level easier to understand; the endpoints and data will remain exactly the same.

There’s much more to do as we continue to refine the developer experience. Be sure to keep an eye on our API platform roadmap for the latest details of what we’re working on, and remember that you can always reach us on the developer forums. We’re looking forward to hearing what you think.