Extract X (Twitter) Data
Public posts, threads, and engagement data from X.
Tell AuraCrawl what you need from X in plain language — "every post mentioning this brand with its engagement," "all replies in these threads," "posts from these 300 accounts, hourly." X is the hardest social surface to read at volume right now: the public API is priced out of most use cases, and the web app is a client-rendered app behind an internal GraphQL layer with aggressive rate limiting. Both are access problems, which is the part we take on.
What a response looks like
REQUEST
ask“Tell AuraCrawl what you need from X (Twitter) in plain language — which entities, which fields, how often. That sentence is the spec.”
{
"post_id": "1927734118820392961",
"author": {
"handle": "bluetokaicoffee",
"name": "Blue Tokai",
"followers": 41822,
"verified": true
},
"text": "Monsoon Malabar is back. Limited roast, ships Monday.",
"posted_at": "2026-08-14T09:20:00+05:30",
"metrics": {
"replies": 84,
"reposts": 212,
"likes": 1904,
"bookmarks": 143,
"views": 88214
},
"is_reply": false,
"quoted_post_id": null,
"hashtags": [
"#coldbrew"
]
}What you can extract
- Post text, timestamps, and permanent ids
- Author handle, display name, follower count, and verification state
- Full engagement metrics: replies, reposts, likes, bookmarks, and views
- Reply and quote-post threads, reconstructed in order
- Search and hashtag timeline contents
- Account timelines collected on a schedule, with engagement deltas
PIPELINE Aura Strike absorbs X's rate limiting and session requirements, which is what stops most collection here before it starts; Aura Build reassembles reply chains into threads rather than loose posts.
Related targets
Request X (Twitter) data.
Describe the fields, the volume, and the cadence. We scope the extraction and deliver a sample before you commit.