Tweet Scraper by URL - X (Twitter) Post Data

---

📌 Overview

The X (Twitter) Post Scraper takes specific tweet/post URLs (or tweet ids) and returns the complete data for each post: text, author, likes, retweets, replies, quotes, bookmarks and views, media, hashtags, mentions, links and the post date. Pass many URLs and it scrapes them all in one run.

It works with no login, no cookies and no API key — reading only public data through residential proxies, so there's zero risk to any X account. No headless browser means it's fast and inexpensive, even for large URL lists.

✅ Ideal for enriching tweet links you already have — from a spreadsheet, a report, a newsletter, or the output of another scraper.

---

✨ Features

	Feature	Description
🎯	Exact posts	Scrape precisely the tweets you specify — no noise.
📊	Every metric	Likes, retweets, replies, quotes, bookmarks & views.
🖼️	Full content	Text (incl. long posts), media, hashtags, mentions & links.
👤	Author data	Username, name, follower count and verified status.
📦	Bulk + concurrency	Hundreds of URLs per run, fetched in parallel.
🧯	Graceful errors	Deleted/protected posts are flagged, never break the run.
🛡️	Login-free & safe	Guest-token access over residential proxies — no account, no ban risk.
📤	Any format	Export to JSON, CSV, Excel, HTML or pull via API & webhooks.

---

🎯 Who it's for

• Engagement & PR reporting — pull metrics for a set of campaign or press posts.
• Content archiving — snapshot specific tweets before they change or disappear.
• Research & fact-checking — capture the exact data behind a tweet link.
• Data enrichment — hydrate tweet URLs collected elsewhere into full records.

---

🧾 Input

Field	Type	Description
postUrls	array	Required. Tweet/post URLs or tweet ids.
maxConcurrency	integer	How many posts to fetch in parallel (1–12). Default 5.
maxResults	integer	Stop after this many posts. 0 = all.
proxyConfiguration	object	Residential proxy (required by X). Pre-configured for you.

Example input

{
  "postUrls": [
    "https://x.com/NASA/status/2059393717111308634",
    "2059393717111308634"
  ]
}

---

📦 Output

Each post is saved as one structured record:

{
  "tweetId": "2059393717111308634",
  "url": "https://x.com/NASA/status/2059393717111308634",
  "text": "On Tuesday, June 9, we'll announce the four astronauts...",
  "createdAt": "Tue Jun 03 16:00:00 +0000 2026",
  "lang": "en",
  "likeCount": 38146,
  "retweetCount": 4120,
  "replyCount": 612,
  "quoteCount": 210,
  "bookmarkCount": 1503,
  "viewCount": 2834957,
  "isReply": false,
  "isQuote": false,
  "isRetweet": false,
  "hashtags": ["Artemis"],
  "mentions": ["NASA_Astronauts"],
  "urls": ["https://www.nasa.gov/..."],
  "media": [{ "type": "photo", "url": "https://pbs.twimg.com/media/..." }],
  "author": { "username": "NASA", "name": "NASA", "followers": 92089565, "verified": true }
}

📖 Output field reference

Field	Description
text	Full post text (long-form posts supported)
likeCount / retweetCount / replyCount	Core engagement
quoteCount / bookmarkCount / viewCount	Extended engagement & reach
isReply / isQuote / isRetweet	Post type flags
hashtags / mentions / urls	Entities extracted from the post
media	Photos / videos with type and URL
author	Post author with follower count & verified status
createdAt / url	Post date and direct link

---

⚙️ How it works

1. You provide tweet/post URLs or ids.
2. The actor resolves each post through X's public data layer over a residential proxy.
3. Every post is parsed into a clean record with full engagement and media.
4. Results stream to the dataset; deleted/protected posts are flagged.

No login, no cookies, no API keys — and no X account is ever used or risked.

---

❓ FAQ

Is this an X / Twitter API alternative?

Yes. It hydrates tweet URLs into full post data without the official X / Twitter API, developer account, app keys or per-tweet rate limits — just paste links and run.

Does it need login or cookies?

No. It uses public guest-token access only — no login, no cookies you provide and no developer API key. No X account is ever used, so there's zero ban risk.

Can I pass tweet URLs or tweet IDs?

Both — full post URLs (https://x.com/.../status/123) or bare tweet IDs. Mix them freely in one run.

What happens with deleted or protected tweets?

They're returned with a clear error flag so your run always completes cleanly instead of failing on a single bad link.

How many tweets can I scrape per run?

Hundreds to thousands — pass a large postUrls list and raise maxConcurrency.

How do I export X / Twitter post data to CSV or JSON?

Run the actor on your tweet URLs, then download the dataset as CSV, JSON, Excel or HTML — or pull it via API/webhook. It's a clean tweet data export with no extra steps.

Can I scrape tweets without an API key or login?

Yes. This is a Twitter unofficial API by URL — it reads public post data over residential proxies with no developer API key, no app, no login and no cookies.

Does it return tweet engagement metrics?

Yes. Every record includes likes, retweets, replies, quotes, bookmarks and views, making it a ready Twitter post engagement metrics scraper for reporting.

---

🔗 Works great with

• 🐦 X (Twitter) Tweet Scraper — pull a whole profile's timeline.
• 🐦 X (Twitter) Profile & Email Scraper — enrich the authors with contacts.

---

📝 Changelog

2026-06-07

• Docs: added coverage for tweet data export to CSV/JSON, scraping tweets without an API key (Twitter unofficial API), and the post engagement metrics use case.

2026-06-05

• 🛡️ Reliability fix: results are no longer dropped by strict output validation — runs now complete cleanly even at high volume (thousands of results).
• ⚡ Stability & performance hardening; fresh rebuild.

2026-06-04

• Verified live & refreshed build — reliability/maintenance pass.