Pricing

from $2.99 / 1,000 results

Twitter (X.com) Tweets & Profiles Scraper

Twitter X Tweets Profiles Scraper collects tweets and profile details from any public X (Twitter) account, including bios, follower stats, timestamps, media, hashtags, and engagement metrics. Ideal for research, trend tracking, social listening, and automating structured Twitter/X data extraction

Pricing

from $2.99 / 1,000 results

Rating

0.0

(0)

Developer

SimpleAPI

Actor stats

Bookmarked

Total users

Monthly active users

5 days ago

Last modified

Categories

Automation

Lead generation

Social media

🗺️ X Profiles, Handles or Search Terms

startUrls

Required

Profile URLs (https://x.com/nasa), bare handles (nasa, @nasa), numeric user ids, or search terms. A term with a space, a leading #, or a 'search:' prefix is treated as a search; anything that looks like a handle reads that profile's timeline. Profile timelines work with NO cookie. Example: ["https://x.com/nasa", "search: street food"].

Type:array

Default:

[
  "https://x.com/nasa",
  "search: street food"
]

📍 Place Search Terms

placeSearchTerms

Optional

Search terms that always run through the place filters below. Leave the list empty to search on the place filters ALONE (e.g. every recent geo-tagged post in Japan). Example: ["coffee", "traffic"].

Type:array

Default:

[]

🛰️ Only Posts Carrying A Real Place Tag

onlyGeoTaggedPosts

Optional

Sends X's server-side 'has:geo' operator, so every returned post carries a place object (id, name, full name, type, country, country code). Measured 40/40, 20/20 and 19/19 on live runs. X refuses to combine this with a radius search — if you set a radius as well, the radius wins and this is dropped with a warning in the log.

Type:boolean

Default:true

🌍 Place Country (ISO-3166 alpha-2)

placeCountry

Optional

Two-letter country code sent as 'place_country:'. Measured exact: 20/20 rows matched GB, 20/20 JP, 20/20 FR. Combines cleanly with the geo-tag switch above. Example: GB, JP, FR, US, BR.

Type:string

Default:

🏷️ Exact X Place ID

placeId

Optional

X's own place identifier, sent as 'place:'. You can read one off any row this actor returns (the placeId column). Measured exact: 20/20 and 10/10 returned posts carried that same place id. Example: 6863fd050de21120 (Leeds, England).

Type:string

Default:

🧭 Near A Named Place

nearPlace

Optional

Free-text place name sent as 'near:"…" within:km'. Narrows genuinely — a live control run returned 0 % of the same post ids. Volume is small and X does NOT attach a place object to these posts, so use it to find posts published around a place rather than posts tagged to it. Example: London, New York, Tokyo.

Type:string

Default:

📐 Latitude

latitude

Optional

Latitude in decimal degrees, -90 to 90, entered as text so decimals survive. Latitude AND longitude together send 'geocode:,,km' and override the named place above. Example: 40.7128 for New York.

Type:string

Default:

📐 Longitude

longitude

Optional

Longitude in decimal degrees, -180 to 180. Only used when latitude is set as well. Example: -74.0060 for New York.

Type:string

Default:

⭕ Radius Around That Place

radiusKm

Optional

Radius in kilometres for the named-place or coordinate search (1-500). Ignored when neither is set. Default is 25.

Type:integer

Minimum:1

Maximum:500

Default:25

🖼️ Only Posts With A Photo Or Video

onlyWithMedia

Optional

Adds X's server-side 'filter:media' operator to every place search, so the rows come back with pictures attached. Measured 15/15 and 20/20 media-carrying rows on live place runs. Leave off to keep text-only posts too.

Type:boolean

Default:false

💬 Mentioning This Handle

mentioningHandle

Optional

Restrict the place search to posts that mention one account. Enter it with or without the @. Example: nasa.

Type:string

Default:

🔤 Post Language

postLanguage

Optional

ISO 639-1 code sent as X's server-side 'lang:' operator, e.g. en, ja, fr, pt. Leave empty for every language.

Type:string

Default:

🔬 Prove The Place Filter Really Applied

verifyGeoFilter

Optional

Proves the geographic operator was honoured. For the place-tag, country and place-id filters the proof is free: every returned post must carry a matching place object. For radius searches the same query is re-run WITHOUT its geographic tokens (one extra request) and the two post-id sets are compared — identical sets mean X ignored the operator. The outcome lands on the place_search row as geoFilterVerified / verificationMethod / controlRowCount / controlOverlap, and a filter that was ignored is logged as an error instead of quietly handing you a worldwide sweep.

Type:boolean

Default:true

🔑 X auth_token Cookie

authToken

Optional

Your own X session cookie 'auth_token', taken from a logged-in browser. Needed ONLY for search and place filters — profile timelines run fully logged out. Stored encrypted by Apify and never written to the log.

Type:string

🔑 X ct0 Cookie

ct0

Optional

Your own X 'ct0' cookie from the same browser session as auth_token. Sent as a cookie and as the x-csrf-token header. Stored encrypted by Apify and never written to the log.

Type:string

🔃 Sort Order

sortOrder

Optional

'Newest first' and 'Oldest first' ask X for its chronological ranking and then sort the collected posts by post time; 'Most liked first' asks X for its Top ranking and sorts by like count. The sort runs BEFORE the maximum-posts cut, so 'Most liked first' really does return the most-liked posts. Tip: radius searches ('near'/coordinates) return noticeably more rows on 'Most liked first', because X's chronological index is thin for geography.

Type:string

Default:newest

Options:

newestoldestpopular

🔢 Maximum Posts Per Target

maxTweets

Optional

Upper bound on posts returned per profile and per search term (1-100). X's own search index hands back roughly 20 posts per page and stops offering a cursor after a page or two on narrow geographic queries, so a place search often returns fewer than this. Default is 10.

Type:integer

Minimum:1

Maximum:100

Default:10

↩️ Include Replies

withReplies

Optional

Keep posts that are replies to someone else. Turn off for original posts only.

Type:boolean

Default:true

👤 Include The Author Profile Block

includeUserInfo

Optional

Attach the author's profile object (bio, avatar, join date, follower / following / post / media counts, website, self-typed location) to every post row. Turn off for a slimmer dataset.

Type:boolean

Default:true

🌐 Proxy

proxyConfiguration

Optional

Every outbound request — credential discovery, guest-token activation, profile timelines and searches — goes through this proxy. Residential is the default because X rate-limits datacenter ranges hard.

Type:object

Default:

{
  "useApifyProxy": true,
  "apifyProxyGroups": [
    "RESIDENTIAL"
  ]
}

Twitter (X) Tweets Profiles Scraper

scraperforge/twitter-x-tweets-profiles-scraper

Twitter (X) Tweets Profiles Scraper extracts tweets, user profiles, bios, follower counts, engagement metrics, timestamps, hashtags, and other public data. Automate social media research, competitor monitoring, audience analysis, influencer discovery, and lead generation.

ScraperForge

Twitter (X.com) Tweets & Profiles Scraper

scraper-engine/twitter-x-scraper

Scrapes tweets and profile data from Twitter X, capturing usernames, bios, tweet text, media, timestamps, metrics, follower counts, and profile URLs. Ideal for research, trend tracking, competitor analysis, influencer insights, and large-scale Twitter X data extraction.

Scraper Engine

5.0

Twitter (X.com) Tweets & Profiles Scraper

scrapier/twitter-x-scraper

Scrape Tweets and profile data from X (Twitter) with the Twitter X Tweets & Profiles Scraper. Extract tweet text, timestamps, retweets, likes, replies, media, hashtags, user bios, follower counts, verification status, and location. Ideal for analytics, monitoring, research. Fast, scalable, API-ready

Scrapier

5.0

X/Twitter Scraper — Tweets, Profiles & Engagement Data

oneary/twitter-scraper

Scrape Twitter/X data at scale. Extract tweets, profiles, hashtags, trends, and engagement metrics for social media analytics.

Luan M.

X(twitter) User Profile & Tweets Scraper

scrapio/twitter-scraper

Scrapes tweets and profile data from Twitter X, capturing usernames, bios, tweet text, media, timestamps, metrics, follower counts, and profile URLs. Ideal for trend tracking, research, influencer insights, and large-scale Twitter X data extraction

Scrapio

1.0

Twitter X Tweets Profiles Scraper

api-empire/twitter-x-tweets-profiles-scraper

🐦 X (Twitter) Tweets & Profiles Scraper extracts public tweets, bios, followers, hashtags, mentions, links, dates & engagement. 📊 Filter by keywords or usernames and export to CSV/JSON. 🚀 Ideal for social listening, competitor analysis, research & lead gen.

API Empire

Twitter/X Scraper - Tweets, Profiles & Trends

viralanalyzer/twitter-scraper

Scrape Twitter/X: tweets, user profiles, followers, hashtags, and trending topics.

viralanalyzer

106

5.0

Twitter Profile Scraper — Extract Profiles, Tweets & Replies

scrapio/twitter-profile-scraper

Scrapes public Twitter X profiles, capturing usernames, bios, follower and following counts, tweets, media, timestamps, engagement stats, and profile URLs. Ideal for influencer research, competitor analysis, audience insights, and large-scale Twitter X profile data extraction

Scrapio

Twitter (X) Scraper : Tweets, Profiles & Data

techforce.global/twitter-scraper

Scrape tweets from any X (Twitter) profile or tweet URL, no official API needed. Get text, engagement metrics, media, hashtags & author data as JSON, CSV or Excel.