Product Tracks & Commercial Use

Share Your Thoughts

As we design the future of our developer platform we want to learn from our developer community.

We would like to invite you to provide feedback about our plans to offer developers access to the Twitter API through distinct product tracks, each designed to enable developers based on their use case and commercial intent. 

Before completing this form, we ask that you take a minute to review our guide to the future of the Twitter API. We look forward to learning more about you and reviewing your feedback!

You agree that Twitter may send you emails consisting of surveys, interviews requests and/or Twitter product updates related to our API. You may unsubscribe at any time.

As described in the guide to the future of the Twitter API, developers will be able to apply for API access through product tracks that are relevant to them and their use case:

  1. Standard - The default product track for most developers, including those building something for fun, for a good cause, to learn or teach
  2. Academic Research - Academic researchers are one of the largest groups looking to understand what’s happening in the public conversation. Within this track, qualified academic researchers will get highly Elevated access to a relevant collection of endpoints.
  3. Business - Developers build businesses on the Twitter API and we love that their products help other people and businesses better understand and engage with the conversation on Twitter. This track includes Elevated access to relevant collections of endpoints, or Managed access.

We plan on introducing licensing terms which will limit commercial use in certain product tracks. 

1. Which of the below best describes your reason for using the Twitter API? * *
4. a.) Based on the descriptions above, which of the following product tracks is most relevant to your intended use of the API?
3. Who will be using the product, service or analysis you plan to power with the Twitter API? * (please select all that apply) *


There is a field missing.

    Thank you for taking the time to share your feedback with us.