The Twitter App dashboard allows developers to quickly and easily perform the following tasks:
- View your existing Apps and Projects and their associated App ID.
- Create a new Project or standalone App.
- Delete a Project, App, or standalone App.
- Open up a specific App's settings by clicking into the App’s settings. Within the settings, you can see the App details, keys and tokens, and permissions.
Starting January 2021, App keys and tokens are no longer viewable within the Developer Portal and must be saved securely once generated. These credentials can be regenerated from within the App settings. We recommend using a password manager to store your keys and tokens.
It is important to keep this information up to date. Your App name and website URL will be shown as the source within metadata for any Tweets created programmatically by your application. If you change the use case of a Twitter App, be sure to update the use case in these settings in order to ensure you are in compliance with the Developer Terms.
If your application has a tag showing 'suspended' this is because your app is in violation of one or more of Twitter's developer terms such as our automation rules. The developer platform policy team will communicate with developers through the email address set up on the App owner's Twitter account, to review this email address please review your Twitter account settings. Notification emails about suspensions will be sent to this email address with the title similar to "Application suspension notice" and will have specific information on what to do next. To work with the Twitter team to address suspensions, please check your email for specific instructions, or use our platform help form.
Keys and tokens
Inside of an App in a Project or via a standalone App you can view, create, regenerate, or revoke the following tokens:
- API Key (consumer key)
- API Secret (consumer secret)
- Bearer Token
- Access Token - This token can be used to make requests on behalf of the user that owns the App
- Access Token Secret - This token can be used to make requests on behalf of the user that owns the App
Please note - If you would like to make requests on behalf of a different user (in other words, not the user that owns the App), you will have to use the 3-legged OAuth flow to enable that user to authorize your App, and in the process, generate a set of Access Tokens that can be used to make requests on their behalf.
If you are the App owner, you can adjust the permissions of the App (read-only; read and write; or read, write and direct messages). This controls which resources and events you have access to via Twitter APIs (note: some resources require further permission from Twitter directly).