Introduction

The Twitter developer portal is a set of self-serve tools that developers can use to manage their access as well as to create and manage their Projects and Apps.

In the portal, you have the opportunity to:

  • Create and manage your Twitter Projects and Apps.
  • Set up your developer environments.
  • Learn more about different endpoints and features available. 
    • In our Twitter API section, you will see a list of available endpoints. If you click on an endpoint you will be taken to a page that will show you key usage information and other documentation that can be helpful for you as you build with the API, such as quick start guides and migration guides.
    • In the Labs section, you can experiment with our newest endpoints and give us feedback to help shape the future of Twitter’s APIs.
    • In the Premium section, you can access our premium products which include the paid and free sandbox versions of the Account Activity API, Search Tweets, and Full Archive Search. 
  • See a billing page where you can view your payment details and previous invoices. 
  • View team pages where you can add and manage the different handles that have access to your team's Premium APIs.

 

How to apply

To get a Twitter developer account, please apply:

Please note: When applying, you will have to submit detailed use case information about your intended use of Twitter APIs. To get through the application process as quickly as possible, please make sure to be specific about what you are building.

Be sure to confirm your email address at the end of the application flow, and check that email in case our team has additional questions about your application before we can approve it. Your application will automatically close after 14 days of non-response to our team's questions.

 

Twitter for education

If you would like to use Twitter APIs in your classroom, please read through the following page - Playbook: Twitter for education.

 

App management

Developers can both create and manage Twitter Projects and Apps from the Dashboard in the developer portal. This is where you can find the App ID, edit an App's name, description, website, callback URL, and set an App's access levels. Most importantly, this is where you can regenerate the API Key & Secret, bearer token or app owner access token if they are lost. 

Learn more about creating and managing your Apps in Twitter Apps.

 

Premium usage

View your usage under the “account” section of the dashboard.

The developer dashboard is an account-level view of your various premium subscriptions and their respective usage metrics.

For the Premium Search API, you can view the total number of requests you’ve made this billing period, as well as the estimated requests you’ll make by the end of the current billing period. You can also view what percent of your request and Tweet allotment for the current billing period has already been consumed, and when you used your requests throughout the period.  Actual Tweet volume delivered and projected for the period.

For the Premium Account Activity API, you can view the number of subscriptions that you have used out of your total available subscriptions based on the tier.  The volume delivered through Account Activity is not measured. 

Using the drop-down menu in the top-left corner of the developer dashboard you can view request usage over different periods of time including the current month, the last 30 days, the last 24 hours, the last 120 minutes, and the past months. The developer dashboard and all requested usage are based on UTC time.

 

Subscriptions

View your "Subscriptions" page

The "Subscriptions" page is an account-level view of your:

  • Various product subscriptions
  • Current month usage for each product and estimated end of month usage
  • The product package you have for each product
  • The start date of the subscription and the renewal date
  • The subscription terms (month-to-month, etc.)
  • Usage limits
  • Current price-per-month for each package
  • The percent of your monthly request allotment that has already been consumed

You can also upgrade your existing subscriptions from this page. Clicking the upgrade button in the top right-hand corner of any product’s usage chart will allow you to view the other packages that are available for this product. Using the ellipses next to any product’s name, you can upgrade, cancel, or edit a current product subscription.

 

Dev environments

View the "Dev environments" page

To begin using one of the APIs available in the developer portal, you need to set up a dev environment for the endpoint. All of the subscription API packages support at least one dev environment (the number is dependent on the details of your package), which can be used to isolate usage, rules, rate limits, or otherwise within your systems. 

Please note: It is a best practice to associate the products with an App owned by your business @handle to avoid future inconveniences. 

 

Billing

View your "Billing" page

The billing page features information on your billing cycle and most recent charges, your payment methods, and a list of your previous transactions. If you click on a transaction ID, you will be taken to a more detailed view of that invoice.’

If you miss a payment, your paid access will downgrade to the sandbox tier. If you would like to continue to access a paid tier, please re-upgrade via the subscriptions page.

You will notice a "Charge date" field within the "Billing" page. This is the date during which your use case and account was Approved by the Twitter team. If you upgrade, you will pay a prorated fee to get you through your Charge date. From then until you downgrade, you will be charged the subscription fee on your charge date.

 

Team

Available on 'Organization' developer accounts only.  View the "Team" page.

From the team dashboard, you can manage developer access and edit the roles of the developers working on a premium application.  

On the "Active tab" of the team dashboard, you can remove developers from a team, invite users to join a team, change developer roles, and leave an account if desired. 

This tab will also allow you to review the current developers on the team, the role of given developers, and the day they were added to the team. On the "Invited tab" of the team dashboard, you can view the invitations that you have sent to developers, the date a developer was invited to join the team, and the status of their invite.

Currently, only Administrators have the ability to add/remove members of the team, upgrade/manage subscriptions, set up dev environments, and manage billing/payment methods. The developer’s role is limited to read-only access to the developer portal.

Team functionality is intended to facilitate collaborative development for premium APIs. Often teams have different people responsible for access control, development, billing/payments, etc. and this allows you to invite those people to contribute to your project.

Note: Team management does not currently grant/limit API access, which is based on App credentials.  It is not possible to share App management across your team. Currently the ‘team setup’ only Applies to the Premium API section; and not to the App management section.  Apps (keys/tokens) cannot be edited, created, or deleted by non-owners.

 

Team roles functionality, abilities, limitations:

Note: Team management does not currently include shared App credential view, edit, deletion abilities, or grant/limit API access, which is based on App credentials.

Administrator role:

  • Owned App management & new owned App creation
  • Ability to manage premium dev environments
  • Ability to choose/upgrade premium subscriptions
  • Ability to update billing/payment methods
  • Administrators should include all App owner @users that are implementing/operating under the specific use case of the developer account
  • An account can have an unlimited number of administrators

 

Developer role: 

  • Owned App management
  • Read-only access to premium setup
  • An account can have an unlimited number of developers


Next steps

Was this document helpful?

Thank you

Thank you for the feedback. We’re really glad we could help!

Thank you for the feedback. How could we improve this document?

Thank you for the feedback. Your comments will help us improve our documents in the future.