How to Scrape X (Twitter) Data Without Login or API

Pull tweets, search results, profiles and follower counts from X (Twitter) without an API key, without logging in, and paying only for the results you actually keep.

The problem with the official X API

If you just want to collect public tweets for research, monitoring or analysis, the official X API has become an awkward fit. The free tier is effectively read-blocked for most use cases, and the paid tiers jump to expensive monthly subscriptions billed whether you use them or not. You also have to register an app, manage OAuth tokens, respect per-endpoint rate caps, and rebuild your integration whenever the access rules change again.

For a lot of practical work — tracking a hashtag, archiving an account, pulling tweets for a sentiment dataset — that is a heavy commitment for data that is already public on the open web. The no-login alternative below skips the subscription and the token plumbing entirely: you describe what you want, run it in your browser, and download the rows.

What data you get

This guide uses two actors. The Tweet Scraper handles tweets, search and timelines. The Twitter (X) User Scraper handles profile and follower data.

From the Tweet Scraper you typically get, per tweet:

Tweet text and the tweet URL / ID
Author handle, display name and author ID
Created-at timestamp
Like count, retweet count, reply count and view count
Media URLs (images and video) and any links in the tweet
Language and whether it is a reply or retweet

From the Twitter User Scraper you get, per profile:

Username and display name
Bio / description
Follower count and following count
Verified status
Tweet count, account creation date, location and profile image URL

Both export to JSON, CSV or Excel, or pipe straight into Notion or Slack.

Step by step: run the Tweet Scraper

1. Open the actor. Go to the Tweet Scraper page on Apify and click Try for free. A free Apify account is enough to start; you do not need an X account or any API key.
2. Choose what to collect. You can give it search terms (for example climate policy), one or more usernames to pull a timeline from, or a hashtag. You can also paste specific tweet URLs.
3. Set limits. Set a maximum number of tweets so a broad search does not run longer than you want. You can also narrow by date range or language where the input supports it.
4. Run it. Click Start. The run executes on Apify's cloud — nothing runs on your machine and you do not have to keep a browser open.
5. Export. When the run finishes, open the Storage / Dataset tab and download JSON, CSV or Excel, or connect it to a destination like Notion or Slack.

A realistic input example

Say you want the 500 most recent tweets mentioning a product launch, in English only. Your input would look roughly like this:

searchTerms: ["acme launch", "#acmelaunch"]
maxItems: 500
language: en
sort: Latest

And a single output row (JSON) would contain fields along these lines:

url, id, text
author.userName, author.name, author.id
createdAt
likeCount, retweetCount, replyCount, viewCount
media (array of image/video URLs)
lang, isReply, isRetweet

To enrich those results with author follower counts, take the unique author.userName values, feed them into the Twitter (X) User Scraper, and join on username.

When and why to use this

This approach fits the jobs that don't justify an API subscription:

Research datasets. Collect tweets on a topic for sentiment, discourse or trend analysis without negotiating API access.
Brand and reputation monitoring. Track mentions of a name, product or campaign on a schedule.
Competitor and creator tracking. Archive a handful of accounts' timelines and watch follower growth over time.
Lead and outreach context. Pull bios, follower counts and verified status to qualify accounts.

If you are also working across other networks, the same pay-per-result model is available for Instagram and TikTok, so you can standardise one workflow across platforms.

Honest comparison: official API vs paid incumbents vs this

Versus the official X API. The API is the only fully sanctioned, real-time firehose-style source and is the right choice if you need guaranteed SLAs, write access (posting), or streaming volume at enterprise scale. The trade-off is the fixed monthly cost, app registration, token management and rate caps. The no-login scraper has none of that overhead and you pay per result, but it reads public data only — no posting, no private accounts, and no contractual SLA.

Versus other paid Apify scrapers (such as apidojo's). The main differences here are price and billing model: the Tweet Scraper runs around $0.13 per 1,000 tweets, with no minimums, no monthly caps, and failed runs free. You are charged for usable results, not for a subscription seat. We don't publish user counts or ratings because this actor is newer and has no public reviews yet — judge it on the price and the free trial, not on testimonials.

A reasonable rule of thumb: use the official API when you need real-time guarantees or write access, and use the no-login scraper when you need affordable, on-demand collection of public data.

FAQ

Do I need a Twitter/X account or API key?
No. The scraper reads public data without logging in, so there is no account, app registration or token to manage.

Is this legal?
It collects publicly visible data. As with any scraping, you are responsible for how you use the data — respect copyright, privacy law (such as GDPR for personal data) and X's terms. For most research, monitoring and analytics use cases on public posts this is straightforward, but if you are unsure, get your own legal advice.

Can I get private accounts or DMs?
No. Only public tweets and public profile fields are accessible. Protected accounts and direct messages are out of scope.

What if a run fails or returns nothing?
Failed runs are free, so you are not charged for a run that doesn't produce results. Retry with a smaller scope or different search terms if a broad query times out.

How do I get follower counts alongside tweets?
Run the Twitter (X) User Scraper on the unique authors from your tweet dataset and join the two on username.

Can I schedule it to run automatically?
Yes. Apify lets you put any actor on a schedule and send results to Notion, Slack or a webhook, which makes it suitable for ongoing monitoring.

Related guides

Try it nowRun on Apify →

← All web scraping guides