For research & academia
Twitter (X) API for
Researchers & Academics
Social-media data should not cost more than the grant that funds it. twitterapi.io gives research teams full historical Twitter/X search and real-time collection on plain pay-per-call pricing — no enterprise contract, no subscription minimum — and rebates half of what an academic project spends.
Used to build published research datasets · Pay only for the data you pull · $0.10 in free credit to start
Already in the research record
When a team of eight researchers needed more than a million public tweets to build a dataset of multi-party human–LLM conversations, they collected it through twitterapi.io. The dataset and its collection method are documented in a public arXiv paper.
“@GrokSet, a large-scale dataset of over 1 million tweets involving the @Grok LLM on X.”
Migliarini, Ercevik, Olowe, Fatima, Zhao, Le, Sharma & PandaRead it on arXiv
If twitterapi.io supports your research, we would genuinely like to hear about it — and we are happy to be cited as your data source.
Why the official X API stopped working for research
For years the official API had a dedicated academic track. That track was scaled back, and what replaced it does not fit how research is funded or how it is supposed to be reproduced. Four specific walls come up again and again.
The cost wall
Research-grade access on the official API now sits inside enterprise pricing — thousands of dollars a month. That is hard to justify for a single study and impossible to standardise across a department or a teaching cohort. The budget conversation ends the project before the data collection starts.
Access friction
What remains of academic access is an application-and-approval process with real delays and eligibility conditions. A reviewer's revision request that needs more data can stall for weeks waiting on an access decision, not on the analysis.
Quotas throttle real collection
Monthly post caps mean large-scale or longitudinal collection runs out of allowance quickly. You end up rationing the dataset to fit the tier, instead of sizing the dataset to fit the research question.
The reproducibility problem
When data access is gated, expensive and tiered, another lab cannot simply re-run your collection. A field that depends on replication cannot afford a data layer that only well-funded groups can reach.
What a research project gets instead
twitterapi.io is a third-party API for public Twitter/X data. It is built around one idea that matters for research: you pay for the data you actually pull, and nothing else.
Pay-per-call, no subscription
About $0.15 per 1,000 tweets retrieved. No monthly minimum, no annual contract, no tier to qualify for. A pilot study costs pilot-study money.
Full historical search
Query the archive by keyword, hashtag, account, language and date range. Assemble a corpus that matches your research question rather than the API's tier limits.
The endpoints research uses
User timelines, advanced search, follower and following graphs, tweet lookup by ID, and real-time filter rules for ongoing longitudinal collection.
Access in minutes
An API key issues immediately, with $0.10 in free credit so you can test and cost a collection script before you commit any spend.
New to the API? The step-by-step integration walkthrough covers free credits, the collection code and a worked example. The pricing page has the full per-call rate card.
What researchers build with it
The same pay-per-call surface supports very different studies. A few of the patterns we see most often:
Longitudinal & temporal studies
Pull the same query across months or years to watch how a discourse, a narrative, or an account's behaviour shifts over time. Historical search means you are not limited to the window in which you happened to be collecting.
Sentiment & discourse analysis
Assemble a labelled corpus around a topic, an event, or a set of hashtags. Filter by language and engagement so the dataset matches the population your study is actually about.
Information diffusion & networks
Reconstruct how a post travelled — reply chains, quote trees, follower and following graphs. The relationships, not just the text, are what most network research needs.
Bot & coordinated-behaviour detection
Sample large numbers of accounts and their timelines to train and validate detection models. Coordinated activity only shows up at a scale that per-tier post caps make expensive elsewhere.
LLM & human–AI interaction data
Conversational data involving AI accounts is a live research area — the @GrokSet dataset below is one example. twitterapi.io returns full thread context, not isolated posts.
Replication & shared datasets
Because collection is cheap and needs no institutional contract, another lab can re-run your script and reproduce your corpus — which is the point of a method section.
The academic rebate — 50% back
refunded — up to $200.
If you are doing academic or non-commercial research, half of your usage is on us. There are three steps, and none of them involve a sales call.
- 1
Apply
Email hello@twitterapi.io and tell us about your research — who you are, your institution or project, and what you are studying. A short paragraph is enough.
- 2
Use the product normally
Top up credits and run your collection pay-as-you-go. Build your dataset and finish your project at the standard rate — no special mode, no waiting on approval.
- 3
Claim the rebate
Email hello@twitterapi.io with proof of what you paid. We refund 50% of the amount, capped at $200.
Open to students, faculty, postdocs, lab groups and independent researchers doing academic or other non-commercial work.
Apply for the academic rebateQuestions researchers ask
Is the academic rebate really 50%?
Yes. After you have paid for usage, we refund half of what you spent, up to a maximum of $200. It is a rebate on real spend, not a discount code — you pay the normal pay-as-you-go rate first, then claim half of it back.
Who is eligible?
Students, faculty, postdocs, lab groups and independent researchers carrying out academic or other non-commercial research. The work does not have to be affiliated with a university — independent and pre-print research counts. It should not be a commercial product build.
What does it cost before the rebate?
twitterapi.io is pay-per-call: about $0.15 per 1,000 tweets retrieved, with no subscription and no monthly minimum. New accounts start with $0.10 in free credit, enough to test a collection script before spending anything. After the rebate, an academic project pays roughly half of that.
How far back does the data go?
The search endpoints query historical tweets, so you can build a corpus that predates the day you started collecting. You can also register a real-time filter rule to capture new posts going forward for an ongoing study.
Can I cite twitterapi.io in my paper?
Yes, and we encourage it — a clear data-collection method helps reviewers and anyone trying to replicate your work. twitterapi.io has already been used as the collection tool for published research datasets.
Do I need to apply before I start paying?
Applying first is best — email us about your research before you top up — but the rebate is calculated from your proof of payment, so what matters is that you tell us about the project and send the receipt when you claim.
Is collecting public tweets for research compliant?
twitterapi.io returns only publicly posted content — never private or protected accounts. Whether a specific dataset and analysis meet your institution's ethics requirements is a question for your IRB or ethics board; the tool gives you public data, your study design governs how it is used.
What if my project costs more than $400?
The rebate is capped at $200 back, so it fully covers the first $400 of spend. Beyond that you pay the standard pay-per-call rate, which is already a fraction of an enterprise API contract — there is no tier jump or minimum to cross.
Start with the data, not the contract.
Issue a key, test your collection script on free credit, and pull exactly the corpus your study needs. When you have spent, claim half of it back.