Frequently Asked Questions
How do I transfer ownership of my Twitter App to another account?
You can transfer your Twitter App to another account by selecting 'I need to transfer an API key to another account' when filling out this form.
What's the difference between standalone Apps and Projects?
Projects allow you to organize your work based on how you intend to use the Twitter API, so you can effectively manage your access to the API, and monitor your usage. Each Project contains an App. You’ll need to create a Project to use v2 endpoints. Standalone Apps are Apps that exist outside of the Project structure. These Apps can connect to v1.1, Labs, or Premium endpoints but can’t connect to v2 endpoints.
Can I add existing Apps to a Project?
Yes, you can add an existing App to your new Project. While setting up your Project you should see an option to add any of your standalone Apps. Keep in mind that you may only have one primary or production App per approved use case. See our Developer Policy for more information, including guidelines around additional apps for development or testing.
What if I have more than 10 Apps already? Can I create a Project?
If you have 10 Apps you cannot create a Project unless you delete one of your Apps and create a new one. Once you’ve deleted your App and created a Project you can try the new v2 endpoints.
Who should own Twitter Apps that are used in the development of a company's product?
It is a best practice for the company that owns a product or service that is using a Twitter App to own that Twitter App. If your company does not have a developer account, we recommend that you apply for an organization developer account with the company's handle and transfer any Twitter Apps being used by that company to the new organization account.
I have a Twitter App that is owned by handle A, but I want to make a request on behalf of handle B. How do I do that?
It is true that you can generate an access token and secret within your Twitter App to be used by the owning user. You do not, however, need to have a developer account nor a Twitter App for you to generate an access token for them. Even if the user does have a developer account and Twitter Apps, you would not be able to use any of the access tokens that they generate from their Twitter Apps, because those tokens are meant to be used with their respective Twitter Apps.
To make a request on behalf of another user, you need to generate a new set of user access tokens that are specifically meant to be used by your Twitter App. To generate these access tokens, you must use the 3-legged OAuth flow and have the user authenticate or authorize your Twitter App. The third step in the 3-legged OAuth flow provides you a set of access tokens that you can use along with your consumer key and secret to make a request on behalf of that user with your Twitter App.
You should be able to do all of your development for a single organization with one developer account. If you have a single organization with multiple use cases, please create and use different Twitter Apps for those different use cases.
Why aren’t my Apps showing up in the developer portal?
Your Twitter Apps may have been provisioned through an account other than the one you’re logged in to or set up through automated means. Please submit a platform support request for further assistance.
What changes is Twitter making within the developer platform for general Twitter platform health?
Over the last year, Twitter has taken several steps to protect our platform from abuse, spam, and malicious automation. We recently announced that we’re taking additional steps to ensure that our developer platform works in service of the overall health of conversation on Twitter.
Starting July 24th, 2018, anyone who wants to create a new Twitter App will need to have an approved developer account. You can apply for a developer account at developer.twitter.com. Once your application has been approved, you’ll be able to create new Apps on developer.twitter.com.
Are there any future changes that we should be aware of?
We will eventually require all developers to have an approved developer account to both create and manage their Twitter Apps. We will provide at least 90 days of notice before making this change.
Why is Twitter making these changes?
We’re committed to providing access to our platform to developers whose products and services make Twitter a better place. However, recognizing the challenges facing Twitter and the public — from spam and malicious automation to surveillance and invasions of privacy — we’re taking additional steps to ensure that our developer platform works in service of the overall health of conversation on Twitter.
We do not tolerate the use of our APIs to produce spam, manipulate conversations, or invade the privacy of people using Twitter. Between April and June 2018, we removed more than 143,000 Apps that violated our policies, and we’re continuing to invest in building out improved tools and processes to help us stop malicious Apps faster and more efficiently. To this end, in addition to continuing our work to remove problematic Apps after they're already active, we are taking steps to limit the access these Apps have to our platform in the first place.
How will these changes impact developers
Starting July 24th, 2018, all developers will need to have a developer account to be able to create new Twitter Apps. To do this, you must first apply for a developer portal account, during which time Twitter will review your use case. Once approved, you will be able to create up to 10 Apps in the developer portal.
What will I need to change as a result of these changes?
We encourage all developers who require Apps to apply for a developer account at developer.twitter.com/apply. Once you have been approved, you will be able to create new Apps and manage existing Apps in the developer portal.
If you just need to view and edit your existing Twitter Apps, you can still do so by logging in with your Twitter account on developer.twitter.com, but we will eventually require an approved developer account to view and edit your Twitter Apps.
Will these changes impact my existing application(s)?
These changes will not impact your existing applications. For now, you can manage them on developer.twitter.com if you are logged into your Twitter account, but we encourage you to apply for a developer account.
Why is Twitter limiting who can access its API?
We are not making any policy changes about who can access our APIs at this time. These changes are new ways to enforce our existing policy, ensure more accountability, and reduce the impact of spam and bad actors on our developer platform. We have been increasingly reviewing existing Apps and are making product changes to help.
I have a use case that requires more than 10 Apps. Why am I limited and how do I apply for an elevation?
We have limited accounts to a maximum of 10 Apps as an important step to combat spam and multi-key abuse. We recognize, however, that there are legitimate reasons for developers to have more than 10 Apps linked to their accounts. We suggest that you review our policy guidance on multiple Apps for the same use case to familiarize yourself with the types of App creation that are not policy-compliant. If, after reading this guide, you believe you may qualify for additional Apps beyond the 10 limit (or your current number of Apps, if it’s greater than 10) please complete the following steps:
If you haven’t already submitted a developer account application, please submit one. Please be as specific and detailed as possible to avoid additional requests for information and ensure a smooth review. You will also need to confirm your email address at the end of the application flow. Please make sure to pay attention to your email in case we need to clarify your use case.
While we review your developer account application, make sure we know the purpose of each of your individual Apps. Using developer.twitter.com, you can add a description of your App's use case(s) where it says “Tell us how this App will be used”.
Once you receive notice that your developer account is approved, you should submit an elevation request for each App that needs elevated App access:
Go to our API Policy Support Form
Open a case under the “I have an API policy question not covered by these points” category. (Be sure that you’re signed in from the @handle tied to the developer account that is requesting additional Apps.)
In the “Details” section of the form please provide the total number of Apps that you require, along with the specific use case for each App. We will not approve Apps that do not include a use case.
Submit the case, and complete instructions in follow up emails as requested.
I’d like to provide feedback. How can I do that?
That’s great! We’re always looking for feedback from the community. You just need to add your feedback to our feedback channel.
How do I stay informed about changes in the future?
Follow or subscribe to one (or all) of our many channels to stay informed about developer news.
Do you still have questions?
If you still have questions, let us know on the forums.