Support > Twitter API > Academic Research

Academic research support

Twitter's Academic Reserach Program grants Twitter API access to approved academic researchers.  Here we answer frequently asked questions about access, technical functionality.


Frequently asked questions about the Academic Research Program setup

What is the Academic Research Program? 

Learn more about the Academic Research Program, program access requirements, or submit your academic research study.

Where can I check my academic research access setup?

After the application process, approved Academic Researchers will have an Academic Research Project within the developer portal.  Adding a new or existing App to this Academic Research Project will give that App access ot the Academic Research access levels and features, such as full archive search access, as well as a higher Tweet cap per month.

How many projects can I create for academic research?

Currently you can only have one Project in your developer portal with Academic Research access.

What level of Twitter API v2 access is allowed with academic research access?

A Project with Academic Research access includes:

  • 10 million Tweets per month
  • Longer query length & more rules on search Tweets and filtered stream
  • Access to Full-archive search
  • Advanced search operators like place_country, has:geo etc in search and bio_name, bio_location etc in filtered stream

Are there rate limits on full archive search, different from the monthly Tweet cap of 10 million Tweets?

Yes, full-archive search has a rate limit (including pagination) of 300 requests per 15-minute window.

How can I track my academic research project usage?

Usage, including monthly Tweet cap and renewal date can be tracked in the developer portal on the Academic Research Project.



Frequently asked questions about full archive search for Academic Research

Why do I get truncated Tweets when searching using the API?

That happens for retweets & you can use the expansion and then get the full text from the includes object of your response. Learn more about using expansions & fields.

Why am I not able to get Tweets older than 30 days when using full-archive search?

If you do not specify the start_time for your request, the endpoint will return Tweets for the last 30 days by default as explained in our technical documentation.

I am not able to get all Tweets for a conversation thread (using conversation_id)

Similar to the previous question, you may be missing the start_time which is why it defaults to Tweets from last 30 days. Tweets in the conversation outside of this timeframe will not be included.

Is there a way to get a random sample of Tweets using an operator on full-archive search endpoint?

There is no operator to request a sample from this endpoint. You may review some community posts like this one that discusses some ideas.

Why do I get 503s when requesting 500 Tweets per request to full-archive search with all fields & expansions?

This is a known issue we are working to resolve. The workaround is to request 100 Tweets at a time if requesting all fields and expansions.

Why am I not able to get Tweets from the Twitter API v2 using the library I used with v1.1?

If you're using a library that has not beed updated to work with v2 of the Twitter API, you will likely still be making requests to v1.1. Review the list of v2 ready libraries in the Tools & Libraries seciton, or browse our community forums for recently launched or updated tools.








Get support

We have a dedicated forum category for academic research that you can use to discuss the use of Twitter data in research, including methodological guidance, research best practices, etc. 

Please do not use this category for questions about your developer account application. Please use the Twitter API category of the community forum for technical questions.

Before you post a question

When you post a question, make sure to include the following information

  • A description of the problem
  • The API call being made (include headers, if possible)
  • The Twitter response returned (include any error messages)
  • What you expected to receive instead
  • List of steps taken to troubleshoot the issue
  • List of steps required to reproduce the issue
  • If relevant, the time frame during which an issue occurred 
  • If relevant, the App ID, Tweet ID, etc.
  • Any relevant code sample or screenshots

Please only include one topic/question per post. 

If you have feature requests or feedback, please submit these through the Twitter Developer Platform Feedback Form

For Policy-related issues, such as App suspension, please contact Policy support.

For Twitter-related issues, such as login and account support, please use the Twitter Help Desk.