What exactly is a Project? 

A Project allows you to organize your work (based on use case) with the Twitter Developer Platform’s APIs, and are required when making requests to the Twitter API v2 endpoints. You are also limited to being able to retrieve a certain number of Tweets per month from specific endpoints at the Project-level.

How many Projects can I create? 

You are currently allowed to have one Standard Project and, if approved for access, one Academic Research Project. We may expand the number of Projects you can create as we launch more products and features.

Can I have more than one App connected to a Project?

At this time, you may only connect one App per Project. In the future we will introduce the capability to add more than one App per Project.

Can I add existing Apps to a Project?

Yes, you can add an existing App (also known as standalone Apps) to your Project. When setting up your Project, you should see an option to add a standalone App to that Project. 

Is there a way to check my progress towards the monthly Project Tweet cap?

There is a Project-level Tweet cap limiting the number of Tweets you can retrieve from several Twitter API v2 endpoints. This is set to 500,000 Tweets per month for Standard Projects at the Basic access level, and 10,000,000 Tweets per month for Academic Projects. 

You can check your progress towards the cap from the Project section on the developer portal dashboard

Are the existing Standard and Academic Research Project Tweet caps a hard limit? Is there a way to get more?

The existing Tweet caps are hard limits. In future releases, we will be launching elevated access options for the Twitter API v2 endpoints across every product track. This will create different options for academic researchers, businesses, and other types of developers. Learn how to stay informed of our plans and launches.

Can anyone else see my Project name or information other than me?

Your Project name and description will only be visible to you or your team if you have a team account. It is important to note that if you implement third-party authentication (sometimes referenced as “sign in with Twitter”), your App’s description will be displayed publicly. You should review and update this description before implementing this feature.

Why can't I edit a Project?

If your developer account was set up as a team account, you will not be able to edit a Project unless you are an administrator of the account. 

If you have an Academic Research Project, you will not be able to edit the details of the Project you used to apply for access.

Why can I see an App in a Project, but none of its details? 

If you are on a team, you may not view the details of, edit, or manage keys for someone else's App in a team account's Project due to privacy reasons. In this case, you will only be able to see the App name and owner’s name so that you can contact them.

If I had a Project in my account prior to the launch of v2, how do I obtain access to the newest versions of endpoints?

If you have more than one Project created as part of the developer portal beta experience, you will be able to choose which Project will get v2 access in the dashboard section of the portal. 

Where are my keys and tokens? 

You can access your keys and tokens inside of the Projects & Apps section of the developer portal, by clicking on an App. It is important to note that we recently stopped showing your keys and tokens in your Twitter developer App dashboard other than when you first generate or regenerate your credentials. You will need to store your keys and tokens securely. If you lost your keys and/or tokens, or believe that they have been compromised, you should regenerate your keys and tokens via the App dashboard. Note that regenerating your keys and tokens will invalidate any previous keys and tokens and you may need to rewrite and/or redeploy existing code.

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.