Twitter Profile Posts Scraper – X Timelines & Media
Pricing
from $1.00 / 1,000 results
Go to Apify Store
Twitter Profile Posts Scraper – X Timelines & Media
Extract public Twitter (X) profile posts by username. Set a page budget and get text, authors, engagement, media and source-profile details in one row per post.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
ScrapingMonkey
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Collect public posts from selected Twitter (X) profiles using plain usernames and a page budget. Twitter Profile Posts Scraper returns one row per post with text, author, engagement, media and the profile it was collected from.
Use it to compare account publishing, review campaign activity or build repeatable snapshots of the public timeline content X makes available.
| At a glance | Details |
|---|---|
| 📥 Input | Plain usernames and a pagesPerProfile limit |
| 📤 Output | One row per post with profile context, text, counts and media |
| 🔐 Login required | No Twitter (X) credentials or cookies |
| ⚡ Processing | Up to 5 requests concurrently with automatic retries |
| 💾 Delivery | One table; each post has its own row and matching JSON fields |
What the Twitter (X) profile posts scraper extracts 🔎
The Actor resolves each account, reads its available post timeline and keeps post-level details together with the source profile.
- The requested profile's identity, bio, account links and public counts
- Post ID, canonical URL, text, publication date, language and content type
- Author identity, profile links, bio, public counts and account flags
- Available like, reply, repost, quote, bookmark and view counts
- Hashtags, cashtags, mentions and expanded links
- Images, video URLs, thumbnails, dimensions, alt text and available video variants
- Reply context, community reference, link-card values and edit metadata
- Quoted and reposted content included with the response, up to two embedded levels
How to scrape Twitter (X) profile posts 🚀
- Add a plain username such as
NASA, without@or a profile URL. - Set
pagesPerProfileto the maximum pages to request for each account. - Start the Actor and review the returned post rows.
- Export the dataset or connect it to a scheduled reporting workflow.
Exact duplicate usernames are normally processed once. Keep username spelling consistent across a batch; differently capitalized inputs are not explicitly merged. Post IDs are deduplicated within each profile's pagination; the same post can still appear when collected from different profiles.
Twitter (X) profile posts data fields and complete output 📦
| Field group | Included data |
|---|---|
| Source profile | The requested account's identity, links, counts and flags |
| Post | ID, URL, text, type, dates, language and source |
| Author | Available profile identity, bio, links, counts and account flags |
| Engagement | Likes, replies, reposts, quotes, bookmarks and views |
| Media and references | Images, videos, variants, hashtags, cashtags, mentions and links |
| Context | Reply targets, community, card data, quoted or reposted content and edit metadata |
Complete illustrative success item with fictional content, not a live result:
profile.* identifies the account whose collection was requested; author.* describes the post's author. These may differ for shared content.
The table and JSON share literal field names such as author.username. Lists for a collection align by position; media.video_variants.url contains one inner variant list per media item. Optional quote and repost branches remain null where no embedded content exists.
Link-card data uses card.values.path and card.values.value: each path identifies a card field, and the value at the same position holds its content. The same arrangement is used within quoted or reposted card fields.
Successful rows can contain empty strings, zero counts, false flags, empty lists or null optional branches when a value is unavailable. A failed row retains input, sets status to failed and leaves the entity data fields null.
Input requirements and coverage ⚙️
| Parameter | Type | Required | Default and rules |
|---|---|---|---|
inputList | array of strings | Yes | No default; at least one item. No fixed input-count maximum. |
pagesPerProfile | integer | No | Default 1; minimum 1; no fixed upper limit. Sets the page budget for each profile. |
Enter plain usernames of 1–15 letters, numbers or underscores, without @ or a profile URL. Navigation words such as home and search are not usernames accepted by the Actor.
The Actor reads the public profile-post timeline. Posts and reposts can appear as X returns them; the requested profile and each post's author are recorded separately. It is not a complete replies-tab crawl.
Each page requests up to 40 posts, but fewer may be returned. Pagination stops at the page budget or earlier if no new post IDs are found, no next cursor is available, or the next cursor repeats. A larger page budget does not guarantee complete history or a fixed number of rows.
Twitter (X) profile posts use cases 🎯
Publishing analysis
Compare topics, formats and posting dates across selected account timelines.
Campaign snapshots
Collect available recent campaign posts with engagement and media references.
Organization monitoring
Maintain scheduled snapshots of public posts from a known list of organization accounts.
Content archives for review
Retain source-linked post records within the public coverage and page budget available to each run.
Pricing and billable posts 💰
Check the Actor's Pricing tab for the current charging model and rate. The Store configuration is authoritative.
Under dataset-item pricing, each saved success or failed row can count as a billable item. Automatic retries do not independently add result rows.
Each newly saved post is a dataset item. Profile fields and embedded media remain in that post's row. The page setting controls requests, not a fixed row total. A profile reporting zero posts, or an empty first timeline page, produces a failed row. A later request failure can add a failed row alongside previously saved posts.
Twitter (X) profile posts API and integrations 🔌
Replace $ACTOR_ID with the ID shown in the Actor API tab and $APIFY_TOKEN with your Apify token.
Start runs through REST, Apify client libraries or schedules. Use webhooks to handle completion, then export the dataset as JSON, CSV or Excel, or send it to Google Sheets, Make, Zapier and your reporting tools.
Reliability and limits ⚠️
Protected profiles are rejected by this Actor. Temporary request failures and selected access errors are retried automatically. A profile reporting zero posts, or an empty first timeline page, produces a failed row. An empty later page ends collection without adding an empty success row. If a later request exhausts retries, earlier saved posts remain and a failed row can mark the incomplete collection.
Some posts expose only part of their media, author or engagement data. Missing counts can default to zero, and a false flag can mean the value was not exposed. Video URLs and image URLs may expire; the Actor does not download files.
Quoted and reposted content is read only when embedded in the response and is limited to two levels. Reply counts and reply-target IDs do not mean that a complete conversation has been collected. The community-note field is a flag, not the note text, and edit metadata does not include a full revision history.
Frequently asked questions ❓
Does it guarantee every historical post?
No. The result is limited by the page budget and the public timeline X exposes. Pagination may stop earlier.
Does one page always contain 40 posts?
No. The Actor requests up to 40 per page, but X can return fewer and duplicate IDs are skipped.
Can I submit a profile URL or @handle?
No. Enter a plain username without @ or a profile link.
What happens when no posts are returned?
A profile reporting zero posts, or an empty first timeline page, produces a failed row. That failed row is different from a successful post record.
Are quoted posts or replies separate rows?
Embedded quotes and reposts remain part of their parent row. The Actor does not separately paginate reply conversations.
Can the same post appear twice in a multi-profile run?
Post IDs are deduplicated within each profile's collection. A post returned for two different profiles can appear once under each source profile.
Support, responsible use, and related actors 🛟
For a reproducible issue, contact support with the run ID, approximate time and a safe public input. Keep credentials and private data out of support messages.
Use public data in line with applicable privacy, copyright and platform requirements.
