# Twitter Post Scraper API — REST, Python & Node | Scrapier (https://scrapier.io/scrapers/x-twitter/posts/api/)

> Call the Twitter Post Scraper REST API from cURL, Python or Node.js. One GET, one header, typed JSON back. 1 credit per call. Failed calls are free. No login.

Last updated: 2026-11-11

**GET**/api/v2/twitter-post/

## Twitter Post Scraper _API_

Last updated: 9 Nov 2026 · REST · JSON

Quick answer

Send `GET https://proxy.scrapier.io/api/v2/twitter-post/?usernames=elonmusk` with your key in the `X-API-Key` header. You get the page of posts back as JSON. 1 credit per page of posts; failed calls are free.

- 1 credit per page of posts
- Failed calls free
- 3 parallel requests per key

[Get a free API key →](https://app.scrapier.io/sign-up)[Jump to the playground](#playground)

Copy for your AI agent

API

## Call the Twitter Post Scraper API

Use the Twitter Post Scraper API from your own apps, scripts or agents. You need a Scrapier account and the API key from your dashboard. Pick a language.

posts.py

import requests\# Replace YOUR\_API\_KEY with the key from your Scrapier dashboardAPI\_KEY = "YOUR\_API\_KEY"params = {    "usernames": "elonmusk",}r = requests.get(    "https://proxy.scrapier.io/api/v2/twitter-post/",    headers={"X-API-Key": API\_KEY},    params=params,    timeout=210,)r.raise\_for\_status()\# The result sits under data.tweetsresult = r.json()\["data"\]\["tweets"\]print(result)

### Twitter Post Scraper API in Python

Plain `requests` is all you need — no SDK. Every response is typed JSON.

Install

**$** pip install requests

Other ways to call it

Playground

## Twitter Post Scraper API Interactive Playground

Edit the request, watch the code update, then run it. Without a key it shows the catalog sample and bills nothing. With your key it makes a real call from your browser; the key goes only to proxy.scrapier.io and is never stored.

ReadyLatency **—**Credits billed: **0**

Request ready`GET /api/v2/twitter-post/?usernames=elonmusk`

Press **Run request** to send it. Without a key you get the catalog sample.

Sending request…

**Error**

Failed calls are not billed.

[Import in Postman](https://docs.scrapier.io/integrations/openapi.md)[OpenAPI spec](https://proxy.scrapier.io/api/v2/openapi.json)

The sample is the same for every input: it shows the response shape, not the account you typed.

### Example response, catalog sample from 9 Nov 2026

{
  "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
  }
}

Data

## Data You Can Extract

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. Every field below comes from the catalog sample response, as typed JSON.

Post

8 fields in the response.

- id
- url
- description
- date\_posted
- hashtags
- tagged\_users
- external\_url
- quoted\_post

Engagement

6 fields in the response.

- likes
- replies
- reposts
- quotes
- bookmarks
- views

Media

2 fields in the response.

- photos
- videos

Author

8 fields in the response.

- user\_posted
- name
- is\_verified
- biography
- followers
- following
- posts\_count
- profile\_image\_link

Input

2 fields in the response.

- input
- input\_username

Response envelope and paging

5 fields in the response.

- success
- data.usernames
- data.page
- data.page\_size
- data.next\_cursor

Schema

## Response Schema Reference

Every field in the sample response. Field names stay the same on every call.

| Field | Type | Example | Description |
| --- | --- | --- | --- |
| `tweets.id` | string | `"1585341984679469056"` | Post ID |
| `tweets.url` | string | `"https://x.com/elonmusk/status/1585341984679…"` | URL of the post |
| `tweets.description` | string | `"Entering Twitter HQ – let that sink in! htt…"` | Text of the post |
| `tweets.date_posted` | string | `"2022-10-26T18:45:58.000Z"` | When the post was published (ISO 8601) |
| `tweets.hashtags` | null | `null` | Hashtags in the post, or null |
| `tweets.tagged_users` | null | `null` | Users tagged in the post, or null |
| `tweets.external_url` | null | `null` | External link in the post, or null |
| `tweets.quoted_post` | object | `{…}` | The post being quoted (date\_posted, description, post\_id, profile\_id, profile\_name, url, videos); values are null when there is none |
| `tweets.likes` | integer | `1221559` | Number of likes |
| `tweets.replies` | integer | `160000` | Number of replies |
| `tweets.reposts` | integer | `200000` | Number of reposts |
| `tweets.quotes` | integer | `70000` | Number of quote posts |
| `tweets.bookmarks` | integer | `16000` | Number of bookmarks |
| `tweets.views` | null | `null` | View count, or null when X does not show it |
| `tweets.photos` | null | `null` | Photo links, or null |
| `tweets.videos` | array | `1 items` | Video links, or null |
| `tweets.user_posted` | string | `"elonmusk"` | Handle of the author |
| `tweets.name` | string | `"Elon Musk"` | Display name of the author |
| `tweets.is_verified` | boolean | `true` | Whether the author is verified |
| `tweets.biography` | string | `""` | Author bio text |
| `tweets.followers` | integer | `241733278` | Author follower count |
| `tweets.following` | integer | `1300` | Number of accounts the author follows |
| `tweets.posts_count` | integer | `98000` | Author's total posts count |
| `tweets.profile_image_link` | string | `"https://pbs.twimg.com/profile_images/exampl…"` | Author profile image URL |
| `tweets.input` | object | `{…}` | The input URL the post was read from |
| `tweets.input_username` | string | `"https://x.com/elonmusk/status/1585341984679…"` | The usernames value you sent |
| `success` | boolean | `true` | true on every 200 response |
| `data.usernames` | string | `"https://x.com/elonmusk/status/1585341984679…"` | Your input, echoed back |
| `data.page` | integer | `1` | Page number of this response |
| `data.page_size` | integer | `1` | Number of posts on this page |
| `data.next_cursor` | null | `null` | Pass back as cursor for the next page; null on the last page |

Parameters

## Request Parameters Reference

| Name | Type | Required | Default | Description | Example |
| --- | --- | --- | --- | --- | --- |
| `usernames` | string | Yes | — | 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` | `elonmusk` |
| `cursor` | string | No | — | Pass back `data.next_cursor` from the previous response to get the next page; `null` means the last page | — |
| `use_proxy` | boolean | No | `true` | Use Scrapier's residential proxy pool when true (default true). Leave as is | `true` |
| `raw_data` | boolean | No | `false` | Return X's raw upstream payload under `raw_responses` instead of the formatted items | `true` |

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

### Pagination in the Twitter Post Scraper API

The Twitter Post Scraper API returns results in pages. Pass `data.next_cursor` back as `cursor` to get the next page; when it is `null` there are no more. Each successful call, first page or later, costs 1 credit.

Access

## Access Without X (Twitter) Login

The Twitter Post Scraper API needs no X (Twitter) account, no login and no session cookies. You send your Scrapier key in the `X-API-Key` header and get JSON back. It reads public data only: what any visitor sees without logging in.

Performance

## Speed, Cost and Concurrency

| Metric | Value | Source |
| --- | --- | --- |
| Cost of a successful call | 1 credit | Scrapier catalog |
| Cost of a failed call | 0 credits | Any non-2xx response |
| Parallel requests per key | 3 | Above that: `429` with `Retry-After` |
| Recommended client timeout | 210 seconds | Scrapier docs, every endpoint |

### Latency of the Twitter Post Scraper API

Scrapier does not publish a latency or success-rate figure for this endpoint. Each call reads X (Twitter) at call time, so response time depends on X (Twitter) and on the size of the result. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.

Limits

## Limits of the Endpoint

Honest constraints of the Twitter Post Scraper API.

- Public data only.
- A failed call, for example a missing or unavailable page of posts, returns a non-2xx status and costs 0 credits.
- Data is read live at call time.
- 3 parallel requests per key; above that the API answers `429` with `Retry-After`.
- Large results come in pages; pass `data.next_cursor` back as `cursor`.
- Fields X (Twitter) does not show are not returned.

Compare

## Scrapier vs the Official X (Twitter) API

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.

| Feature | Scrapier page of posts scraper | Official X (Twitter) API |
| --- | --- | --- |
| Access needed | One Scrapier API key | A developer account, app credentials and a plan with access limits |
| Which posts | A post by URL or ID, or an account's latest posts | Depends on the endpoints and access level of your plan |
| Fields returned | 26 fields per post, including text, engagement and author | Depends on the fields and expansions you request |
| Rate limits | Up to 3 parallel requests per key; 429 with Retry-After | Limits set per endpoint and plan |
| Setup | Sign up, copy a key, send a request | Apply for access, create an app, manage tokens |
| Cost | 1 credit per call, from $1.20 per 1,000 calls | Set by the plan you choose |

Errors

## Errors and Retry Handling

| Status | Meaning | Billed | Fix |
| --- | --- | --- | --- |
| 200 | Page of posts data returned in `data.tweets` | Yes | — |
| 400 | Bad or missing input | No | Check `usernames`: one value per call |
| 401 | `X-API-Key` header missing | No | Add the header |
| 402 | Out of credits (body has `balance`) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait `Retry-After` seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |

From the [error reference](https://docs.scrapier.io/errors/). Any non-2xx response costs 0 credits.

### Retry logic for the Twitter Post Scraper API

retry.py

import time, requests

def get\_posts(value, key, tries=5):
    for attempt in range(tries):
        r = requests.get(
            "https://proxy.scrapier.io/api/v2/twitter-post/",
            headers={"X-API-Key": key},
            params={"usernames": value},
            timeout=210,
        )
        if r.status\_code == 429:
            time.sleep(int(r.headers.get("Retry-After", 2 \*\* attempt)))
        elif r.status\_code >= 500:
            time.sleep(2 \*\* attempt)
        else:
            r.raise\_for\_status()
            return r.json()
    raise RuntimeError("gave up after retries")

Pricing

## Pricing and Rate Limits

| Plan | Monthly price | Pages Of Posts included | Cost per 1,000 |
| --- | --- | --- | --- |
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |

[See all plans →](https://scrapier.io/pricing/)

### Billing rules for the Twitter Post Scraper API

The Twitter Post Scraper API bills 1 credit per successful page of posts. Failed calls, meaning any non-2xx status, cost 0 credits. Every plan allows 3 parallel requests per key. The free tier lets you try it before you pay.

Bulk

## Bulk Lookups and CSV

`usernames` takes one value per call. For a list, loop and run up to 3 requests in parallel per key, then flatten each row into one CSV line.

bulk.py

import csv, requests
from concurrent.futures import ThreadPoolExecutor

values = \["elonmusk"\]  \# your list

def fetch(value):
    r = requests.get(
        "https://proxy.scrapier.io/api/v2/twitter-post/",
        headers={"X-API-Key": "YOUR\_API\_KEY"},
        params={"usernames": value},
        timeout=210,
    )
    r.raise\_for\_status()
    out = r.json()\["data"\]\["tweets"\]
    return out if isinstance(out, list) else \[out\]

\# 3 parallel requests per key is the limit
with ThreadPoolExecutor(max\_workers=3) as pool:
    rows = \[row for part in pool.map(fetch, values) for row in part\]

cols = \["user\_posted", "name", "date\_posted", "description", "likes", "reposts"\]
with open("out.csv", "w", newline="") as f:
    w = csv.DictWriter(f, fieldnames=cols, extrasaction="ignore")
    w.writeheader()
    w.writerows(rows)

### CSV export from the Twitter Post Scraper API

out.csvcatalog sample · 1 row

user\_posted,name,date\_posted,description,likes,reposts
elonmusk,Elon Musk,2022-10-26T18:45:58.000Z,Entering Twitter HQ – let that sink in! https://t.co/D68z4K2wq7,1221559,200000

Agents

## AI Agent Access via MCP

### MCP for the Twitter Post Scraper API

The same endpoint is available to AI agents through the Scrapier MCP server at `https://mcp.scrapier.io/mcp`. One command registers it in Claude Code: `claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY"`. The agent finds the endpoint with `search_endpoints` and calls it with `run_scrape` and the endpoint id `twitter-post`. It takes the same `usernames` input and costs the same 1 credit per page of posts. Setup for every client is on the [Twitter Post Scraper MCP page](https://scrapier.io/scrapers/x-twitter/posts/mcp/).

Integrations

## Integration Paths by Role

No-code

### n8n and Make

1. Add an HTTP Request step
2. GET the endpoint with your `X-API-Key` header
3. Map the `data.tweets` fields to your columns

Developers

### Loop and paginate

for value in values: rows += get(value) while cur := page\["data"\]\["next\_cursor"\]: page = get(cursor=cur)

AI agents

### MCP tool in your agent

Call `run_scrape` with endpoint `twitter-post` from Claude, Cursor or Windsurf. Setup is on the [MCP page](https://scrapier.io/scrapers/x-twitter/posts/mcp/).

Analysts

### CSV and flattened JSON

Flatten each row into one CSV line, one column per field, ready for Sheets, Excel or a BI tool.

Legal

## Legal and Compliance Notes

Scraping publicly available X (Twitter) data is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only public posts any visitor can see without logging in. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data, such as names, handles or posts, must still comply with local data-protection rules, and X's terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our [Terms of Use](https://scrapier.io/terms/).

FAQ

## Frequently Asked Questions

### Is there a X (Twitter) page of posts API?

Yes. Scrapier's Twitter Post Scraper API returns any public page of posts as JSON with one GET request and an X-API-Key header. No X (Twitter) app or login.

### How do I call it from Python?

Use \<code>requests.get\</code> on \<code>https://proxy.scrapier.io/api/v2/twitter-post/\</code> with \<code>params={'usernames': 'elonmusk'}\</code> and \<code>headers={"X-API-Key": KEY}\</code>. Read \<code>r.json()\["data"\]\["tweets"\]\</code>.

### What happens when a call fails?

Any non-200 response is free. Retry 429 and 5xx with backoff; the API already retries upstream failures.

### How much does it cost?

1 credit per successful call — about $1.58 per 1,000 pages of posts on the Pro plan. Failed calls are free.

### Is there an OpenAPI spec?

Yes. It needs no key and covers every Scrapier endpoint.

Related

## Related X (Twitter) APIs

[### Twitter/X Profile Tweets API

An account's posts, a page at a time, with text, like, reply, repost, quote, bookmark and view counts.](https://scrapier.io/scrapers/x-twitter/profile-tweets/)[### X/Twitter Video Transcript API

Speech-to-text transcript of a video post, with language and duration.](https://scrapier.io/scrapers/x-twitter/transcript/)[### All X (Twitter) APIs

All 6 X (Twitter) endpoints.](https://scrapier.io/scrapers/x-twitter/)

## Fetch public X (Twitter) pages of posts as typed JSON in one request

1 credit per page of posts · failed calls free

[Get a free API key →](https://app.scrapier.io/sign-up)

---
Canonical page: https://scrapier.io/scrapers/x-twitter/posts/api/
Site index for AI agents: https://scrapier.io/llms.txt
