New: the Scrapier MCP server. Every scraper in Claude Code with one command. See how →
GET/api/v2/twitter-post/

Twitter Post Scraper

One X (Twitter) post by URL or ID, or a profile's latest posts, as typed JSON: text, date, likes, replies, reposts, views, media links and author. 1 credit per call. No X login, no proxies.

Free API key · 1 credit per page of posts · failed calls free

Last updated
// GET /api/v2/twitter-post/?usernames=elonmusk · sample from the catalog
{
  "success": true,
  "data": {
    "usernames": "https://x.com/elonmusk/status/1585341984679469056",
    "page": 1,
    "page_size": 1,
    "tweets": [
      {
        "biography": "",
        "bookmarks": 16000,
        "date_posted": "2022-10-26T18:45:58.000Z",
        "description": "Entering Twitter HQ – let that sink in! https://t.co/D68z4K2wq7",
        "external_url": null,
        "followers": 241733278,
        "following": 1300,
        "hashtags": null,
        "id": "1585341984679469056",
        "input": {
          "url": "https://x.com/elonmusk/status/1585341984679469056/"
        },
        "is_verified": true,
        "likes": 1221559,
        "name": "Elon Musk"
      }
    ],
    "next_cursor": null
  }
}
Copy for your AI agent
Quick answer

Scrapier's Twitter Post Scraper returns a single post, or the latest posts of an account, as JSON: description, date_posted, likes, replies, reposts, quotes, bookmarks, videos and the author fields. It costs 1 credit per successful call. No X login.

Every request is fetched live at call time · failed calls are free

Twitter Post Scraper extracts posts from X in one of two ways: give it a post URL or ID and it returns that one post, or give it a username, profile URL or numeric user ID and it returns the account's latest posts, about 20 per page. Each post carries its text, date, engagement counts, media links, quoted post and author details. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store or feed a social-listening pipeline. It is one of 6 X (Twitter) endpoints on the same API key used by 12,000+ developers. Follow next_cursor to page on.

What data can I extract with Twitter Post Scraper?

Using this Twitter Post Scraper, you can extract the following data from public X (Twitter) pages of posts:

Author name and handle (name, user_posted)
Verified flag (is_verified)
Post text (description)
Date posted (ISO 8601)
Likes, reposts, quotes, replies
Bookmarks and views
Post URL and post ID
Photos and videos
Hashtags and tagged users
Quoted post (quoted_post)
Author followers and following
Author posts count
Author profile image link
Your input, echoed back
Page size and next cursor

Want the exact field names? See the example output.

Playground

Try Twitter Post Scraper Live

Press Run to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.

X (Twitter)Twitter/X PostsLive

Parameters
+ Run live with your API key
Response
Sample dataCatalog sample, run to see live data

How to use Twitter Post Scraper

Hand it to your AI assistant, or run it yourself in five steps.

Copy to your AI assistant

Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.

Use the Scrapier Twitter Post Scraper to get public X (Twitter) pages of posts. Endpoint: GET https://proxy.scrapier.io/api/v2/twitter-post/?usernames={usernames} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in usernames; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.tweets: biography, bookmarks, date_posted, description, external_url, followers, following, hashtags, id, input, is_verified, likes. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY" and call run_scrape with endpoint "twitter-post" (find it with search_endpoints).
Twitter Post Scraper MCP Server

Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads X (Twitter) pages of posts on its own: no glue code, no scraping logic in your prompts.

MCP setup →

Run it yourself

  1. Get your free Scrapier API keySign up at app.scrapier.io; the free tier lets you try it first.
  2. Open Twitter Post Scraper in the catalogIt lives under Scrapers / X (Twitter).
  3. Enter a post or an accountPut a post URL such as https://x.com/elonmusk/status/1585341984679469056 or a post ID in usernames for one post. Put a handle such as elonmusk, a profile URL or a numeric user ID for the latest posts.
  4. Send your API requestOne GET with your key in the X-API-Key header, or one run_scrape call from your agent. Set a 210-second client timeout.
  5. Save your resultsEach call returns JSON in data.tweets: store it as is, or flatten it to CSV. Pass data.next_cursor back as cursor for the next page until it is null.

How to scale to bulk X (Twitter) pages of posts

usernames takes one value per call, so for a list you loop: one request per post or account. For an account, pass back data.next_cursor to page through its posts. Run up to 3 requests in parallel per API key; above that the API answers 429 with a Retry-After header, and throttled calls cost nothing. Each call is 1 credit and failed calls are free, so 1,000 calls cost 1,000 credits, inside the Hobby plan's 15,000.

Features

Twitter Post Scraper turns X posts into clean rows. It suits social listening, brand monitoring, research and any workflow that needs the text and engagement of a post or an account's latest posts without managing X sessions or API credentials.

It extracts, per page of posts
  • Post textdescription holds the full text of the post
  • Engagementlikes, reposts, replies, quotes and bookmarks
  • Mediaphotos and videos links for the post
  • Quoted postquoted_post carries the post being quoted
  • Authorname, followers, is_verified and more
  • Pagingnext_cursor walks an account page by page

Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per page of posts and 0 credits for a failed call.

Use cases

  • Brand monitor checks a list of X accounts each morning, reads description and likes of the latest posts, and sends the top ones to a team channel.
  • Researcher fetches a set of post URLs, then stores description, date_posted and engagement counts as a dataset for a discourse study.
  • Marketing analyst pulls a competitor's recent posts and compares reposts, quotes and views to see which messages travelled.
  • Journalist drops in the URL of a post and saves its text, date, author and media links as a record before it can be deleted.
  • AI engineer gives an agent a tool that fetches a post or an account's latest posts, then summarises the results with an LLM.

Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.

Why choose this Scraper API?

One post or a whole feed.

usernames accepts a post URL or ID for a single post, or an account for its latest posts, so one endpoint covers both jobs.

Author data in every row.

Each post carries the author's name, followers, following, is_verified and posts_count, so you need no second call to know who posted.

One envelope, 6 X endpoints.

The same key and response envelope cover posts, profile tweets and video transcripts, so one call feeds the next without new code.

Input

The scraper takes one value per call in usernames: a post URL or ID for that single post, or a username, profile URL or numeric user ID for the account's latest posts (about 20 per page). It is required on the first call and ignored once you send a cursor. Send parameters in the query string (GET) or as a JSON body (POST).

NameTypeRequiredDefaultDescription
usernamesstringYes—A post URL or post ID (returns that one post), or a username, profile URL or numeric user ID (latest posts, about 20 per page). One per call. Required on the first call, ignored when cursor is set. Aliases: username, user, users, profile, url, urls, tweet_url, tweet_urls, post_url, tweet_id, id
cursorstringNo—Pass back data.next_cursor from the previous response to get the next page; null means the last page
use_proxybooleanNotrueUse Scrapier's residential proxy pool when true (default true). Leave as is
raw_databooleanNofalseReturn X's raw upstream payload under raw_responses instead of the formatted items

One value per call: to read ten accounts, make ten calls and page each with cursor. Booleans are the strings true or false.

Example input

POST body · input.json
{
  "usernames": "elonmusk",
  "use_proxy": "true",
  "raw_data": "false"
}

Error codes

StatusMeaningBilledFix
200Page of posts data returned in data.tweetsYes—
400Bad or missing inputNoCheck usernames: one value per call
401X-API-Key header missingNoAdd the header
402Out of credits (body has balance)NoTop up; retrying will not help
403Invalid or revoked API keyNoCheck the key in your dashboard
429ThrottledNoWait Retry-After seconds, then retry
5xxUpstream failure or timeoutNoRetry with backoff; set a 210 s client timeout

From the error reference. Any non-2xx response costs 0 credits.

Output

Typed JSON with the same schema on every call. One call returns a page of posts under tweets, each with 26 fields, inside the standard data envelope. data also carries your usernames input, the page, page_size and next_cursor. Field names stay the same on every call. Set raw_data to true if you want X's raw payload instead.

Example output

200 OK · 1 credit · catalog sample
{
  "success": true,
  "data": {
    "usernames": "https://x.com/elonmusk/status/1585341984679469056",
    "page": 1,
    "page_size": 1,
    "tweets": [
      {
        "biography": "",
        "bookmarks": 16000,
        "date_posted": "2022-10-26T18:45:58.000Z",
        "description": "Entering Twitter HQ – let that sink in! https://t.co/D68z4K2wq7",
        "external_url": null,
        "followers": 241733278,
        "following": 1300,
        "hashtags": null,
        "id": "1585341984679469056",
        "input": {
          "url": "https://x.com/elonmusk/status/1585341984679469056/"
        },
        "is_verified": true,
        "likes": 1221559,
        "name": "Elon Musk",
        "photos": null,
        "posts_count": 98000,
        "profile_image_link": "https://pbs.twimg.com/profile_images/example_normal.jpg",
        "quoted_post": {
          "date_posted": null,
          "description": null,
          "post_id": null,
          "profile_id": null,
          "profile_name": null,
          "url": null,
          "videos": null
        },
        "quotes": 70000,
        "replies": 160000,
        "reposts": 200000,
        "tagged_users": null,
        "url": "https://x.com/elonmusk/status/1585341984679469056",
        "user_posted": "elonmusk",
        "videos": [
          "https://video.twimg.com/ext_tw_video/1585341912877146112/pu/vid/1920x1080/example.mp4?tag=14"
        ],
        "views": null,
        "input_username": "https://x.com/elonmusk/status/1585341984679469056"
      }
    ],
    "next_cursor": null
  }
}

The catalog's sample response for usernames=elonmusk, labelled as a sample: live calls return the account's current values.

Post

FieldTypeExampleDescription
tweets.idstring"1585341984679469056"Post ID
tweets.urlstring"https://x.com/elonmusk/status/1585341984679…"URL of the post
tweets.descriptionstring"Entering Twitter HQ – let that sink in! htt…"Text of the post
tweets.date_postedstring"2022-10-26T18:45:58.000Z"When the post was published (ISO 8601)
tweets.hashtagsnullnullHashtags in the post, or null
tweets.tagged_usersnullnullUsers tagged in the post, or null
tweets.external_urlnullnullExternal link in the post, or null
tweets.quoted_postobject{…}The post being quoted (date_posted, description, post_id, profile_id, profile_name, url, videos); values are null when there is none

Engagement

FieldTypeExampleDescription
tweets.likesinteger1221559Number of likes
tweets.repliesinteger160000Number of replies
tweets.repostsinteger200000Number of reposts
tweets.quotesinteger70000Number of quote posts
tweets.bookmarksinteger16000Number of bookmarks
tweets.viewsnullnullView count, or null when X does not show it

Media

FieldTypeExampleDescription
tweets.photosnullnullPhoto links, or null
tweets.videosarray1 itemsVideo links, or null

Author

FieldTypeExampleDescription
tweets.user_postedstring"elonmusk"Handle of the author
tweets.namestring"Elon Musk"Display name of the author
tweets.is_verifiedbooleantrueWhether the author is verified
tweets.biographystring""Author bio text
tweets.followersinteger241733278Author follower count
tweets.followinginteger1300Number of accounts the author follows
tweets.posts_countinteger98000Author's total posts count
tweets.profile_image_linkstring"https://pbs.twimg.com/profile_images/exampl…"Author profile image URL

Input

FieldTypeExampleDescription
tweets.inputobject{…}The input URL the post was read from
tweets.input_usernamestring"https://x.com/elonmusk/status/1585341984679…"The usernames value you sent

Response envelope and paging

FieldTypeExampleDescription
successbooleantruetrue on every 200 response
data.usernamesstring"https://x.com/elonmusk/status/1585341984679…"Your input, echoed back
data.pageinteger1Page number of this response
data.page_sizeinteger1Number of posts on this page
data.next_cursornullnullPass back as cursor for the next page; null on the last page

How does it work?

01

Scrapier sends each request through its residential proxy pool (use_proxy, on by default), so you never manage IPs or proxy accounts.

02

Retries and parsing of X's responses happen on Scrapier's side. You send one HTTP request and get typed JSON back.

03

Only publicly visible data is returned: what any visitor sees without signing in. No X account, cookie or developer credential is used for this endpoint.

04

The schema is stable. When X changes, Scrapier updates the scraper and the field names stay the same.

How do you integrate Twitter Post Scraper into your stack?

It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the API tab.

MCP integration for AI agents

claude mcp add -t http scrapier …

This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including twitter-post: the agent finds it with search_endpoints and calls it with run_scrape. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. Full MCP setup →

No-code tools (n8n, Make, LangChain)

n8n

Use the HTTP Request node with your Scrapier API key in an X-API-Key header and point it at /api/v2/twitter-post/ with the input as a query parameter. Map data into the next node.

Make

Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map the fields you need straight into Sheets, Airtable or your CRM.

LangChain

Wrap the endpoint in a requests-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds twitter-post with search_endpoints itself.

Pricing and Rate Limits

One X (Twitter) page of posts costs 1 credit, so 1,000 pages of posts cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a Retry-After header.

PlanMonthly priceCreditsPages of posts includedPer 1,000 pages of posts
Hobby$2915,00015,000$1.93
Pro$7950,00050,000$1.58
Scale$299250,000250,000$1.20
EnterpriseCustom volume and terms

Prices from the live billing page. See all plans and limits.

Call cost and timing

1credit per successful call
0credits for a failed call
3parallel requests per key
210srecommended client timeout

How we measure this

Credit cost, pagination and the sample come from the live catalog (GET /api/v2/endpoints, /twitter-post/, checked 9 Nov 2026). Concurrency and timeout guidance come from the rate limits page of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.

Twitter Post Scraper vs the Official X (Twitter) API

FeatureScrapier page of posts scraperOfficial X (Twitter) API
Access neededOne Scrapier API keyA developer account, app credentials and a plan with access limits
Which postsA post by URL or ID, or an account's latest postsDepends on the endpoints and access level of your plan
Fields returned26 fields per post, including text, engagement and authorDepends on the fields and expansions you request
Rate limitsUp to 3 parallel requests per key; 429 with Retry-AfterLimits set per endpoint and plan
SetupSign up, copy a key, send a requestApply for access, create an app, manage tokens
Cost1 credit per call, from $1.20 per 1,000 callsSet by the plan you choose

The official X API is the better choice when you post or act on behalf of a user, or need data that only the account owner can see.

Frequently asked questions

What fields does Twitter Post Scraper return?

Each post has id, url, description, date_posted, likes, replies, reposts, quotes, bookmarks, views, photos, videos, hashtags, tagged_users, quoted_post, user_posted, name, followers and more: 26 fields in data.tweets. Each successful call costs 1 credit and needs no X login.

Can I scrape a single tweet by its URL?

Yes. Put the post URL or post ID in usernames and the call returns that one post, with page_size 1 in the catalog sample. Put a handle or profile URL there instead and you get the account's latest posts.

How many posts come back per call for an account?

About 20 per page for a username, profile URL or numeric user ID. To get more, pass data.next_cursor back as cursor; null means you reached the end. Each page is one call and costs 1 credit.

Can I scrape tweets from a profile?

Yes. Send the handle, profile URL or numeric user ID in usernames and you get the latest posts with text, date, engagement and author fields. For replies and a per-tweet user object, see the Twitter profile tweets endpoint.

Does Twitter Post Scraper require an X account or login?

No. Twitter Post Scraper uses no X account or cookies: you send your Scrapier API key in the X-API-Key header and the input, and get JSON back. Only public X data is returned, and no X developer account or API credentials are involved.

How fast does Twitter Post Scraper run?

Scrapier does not publish a latency figure for this endpoint. Each call reads X live. Set a client timeout of 210 seconds, as the docs recommend for every endpoint, and retry a failed call, which costs nothing.

What happens if the input is wrong or X returns nothing?

If a call fails, the API returns a non-2xx status and costs 0 credits. In code, check the status, then skip that input or retry it later. Throttled calls (429 with a Retry-After header) are free as well, so retry loops cost nothing.

Does Twitter Post Scraper work with Claude, ChatGPT and other AI agent tools?

Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header; it works in Claude Code, Cursor and Windsurf. The agent finds twitter-post with search_endpoints and calls it with run_scrape. Any agent that can call an HTTP endpoint can use the REST API directly.

How does it compare to other X scrapers?

Scrapier charges a flat 1 credit per successful call, and failed calls are free; platforms that bill compute units vary with run time and infrastructure. The same API key and MCP server reach all 199 Scrapier endpoints. Scrapier returns structured JSON for public X data.

Does it return data in a format LLMs can use directly?

Yes. Every response is typed JSON with the same field names on every call: no HTML parsing and no selectors. Pass it straight to an LLM, index it into a vector store or return it from an agent tool.

What happens when X changes its layout or anti-bot system?

Scrapier maintains the scraper. When X changes its pages or internal responses, Scrapier updates it, and your calls keep returning the same JSON field names without changes on your end.

How much does it cost to run Twitter Post Scraper 1,000 times?

1,000 credits, because each call is 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.

How do I use Twitter Post Scraper with Python?

Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/twitter-post/ with params={"usernames": "elonmusk"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["tweets"]: it is already JSON, so no HTML parsing is needed.

Is it legal to scrape X (Twitter) data?

It depends on your use and your country, so this is not legal advice. Scrapier returns public X data only. X's terms and privacy law such as GDPR or CCPA apply to how you store and use it. Collect only what you need, and ask a lawyer about your specific case.

Your feedback

Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.

Get started

Start Scraping X (Twitter) Pages Of Posts

Public X (Twitter) pages of posts as JSON, 1 credit each, from REST or MCP.