Overview

If you have existing Apps, you can view, edit, or delete them via the developer portal’s App page.

Accessing the Twitter API and Twitter Ads API requires a set of authentication credentials, also known as keys and tokens, that you must pass with each request. These credentials can come in different forms depending on the type of authentication that is required by the specific endpoint that you are using.

Here are the different credentials that you can generate in your App and how to use them:

  • API Key and Secret: Essentially the username and password for your App. You will use these to authenticate requests that require OAuth 1.0a User Context, or to generate other tokens such as user Access Tokens or a Bearer Token.
  •  A set of user Access Tokens: In general, Access Tokens represent the user that you are making the request on behalf of. The ones that you can generate via the developer portal represent the user that owns the App. You will use these to authenticate requests that require OAuth 1.0a User Context.
  • Bearer Token: You will use this token when making a request to an endpoint that requires OAuth 2.0 Bearer Token.
     

To generate a set of OAuth 1.0a user Access Tokens for a user other than the owner of the App, you will need to use the 3-legged OAuth flow.

In addition to generating the keys and tokens necessary to make Twitter API requests, you will also be able to set access permissions, document the use case or purpose for the App, define a callback URL, and modify other settings related to your App developer environment from within the management dashboard.

 

Apps and Projects

You can use Apps and Projects to help organize your work with the Twitter Developer Platform by use case. Each Project can contain a single App if you have Essential access, and up to three Apps if you have Elevated or greater access.

If you would like to access the new Twitter API v2 endpoints, you will be required to use keys and tokens from an App that is associated with a Project.

If you have Apps that were created before we launched Projects, they will be visible in the section entitled “Standalone Apps”. Standalone Apps are Apps outside of the Project structure. If you have Elevated access, these Standalone Apps will be able to  make requests to just the Twitter API standard v1.1, premium v1.1, and enterprise endpoints, as well as the Twitter Ads API endpoints. If you attach a Standalone App to a Project, it will then be able to make requests to the v2 endpoints. 
 

Developer portal dashboard

You can visit the dashboard to manage the Apps associated with your account. To learn more, please visit our documentation page on the developer portal. The dashboard allows developers to quickly and easily perform the following tasks:

  • View your existing Standalone Apps and their associated App ID.
  • Create a new Project, App, or standalone App.
  • Delete an unused Project or App. 
  • Review or update a specific App's settings, including updating name, desciption, website, callback URL, and permissions.
  • Regenerate App specific credentials like API Key & Secret, Bearer Token, and the App owner's user Access Tokens.

 

Signing up for access

If you have existing Twitter Apps, you can view and edit your Apps via the Twitter App dashboard if you are logged into your Twitter account on developer.twitter.com.  Please note you will not need to sign up for an account to manage any and all Apps that were previously created on apps.twitter.com. 

If you need to create a new Twitter App, you will need to have signed up for a developer account.  If you are a member of a team account, you must be assigned an admin role to create a new App.

 

Next Steps