Cookie Preferences
We use cookies to personalize content and analyze traffic. See our Cookie Policy.
No output yet. Submit the form to generate content.
Transparent pricing with no hidden fees. Pay as you go.
| Rule & Modality | Channel | Credits | Price (USD) | Official / Reference Price | Daily Savings |
|---|---|---|---|---|---|
retweeters otherTwitter | Starter | 0.01per post | $0.00005 | - | - |
Competitor pricing costs $45.450 more
ApiPass is 90.90% lower, estimated at multiple calls returning 10,000 returned posts total
retweeters
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-simple
Retrieve the list of user IDs who have retweeted any specific tweet on X (Twitter) with a single API call.
The Twitter Simple Retweeters API on ApiPass is a lightweight endpoint that returns the IDs of users who have retweeted a given tweet. By submitting a target tweet_id, developers receive a clean array of retweeter user IDs along with a next_cursor_str for pagination, making it easy to enumerate every account that amplified a piece of content. Built on ApiPass's unified asynchronous task system, this API abstracts away the complexity of X's internal endpoints and delivers structured JSON results that can be consumed directly by analytics dashboards, growth tools, or engagement pipelines.
Skip the tedious application, review, and approval process required by X's official platform. Just grab an ApiPass API key and start pulling retweeter data immediately.
A single tweet_id is all you need. The response returns a straightforward list of user IDs — no bloated payloads, no unnecessary metadata parsing.
ApiPass uses a transparent pay-as-you-go model, avoiding the high monthly tiers and per-project restrictions of the official X API.
The createTask + recordInfo pattern (with optional callback URLs) makes it easy to integrate the API into background jobs, queues, and large-scale scraping pipelines without blocking your app.
The included next_cursor_str lets you paginate through viral tweets with tens of thousands of retweeters without hitting request-size limits.
ApiPass handles rate limiting, token rotation, and endpoint changes on the backend, so your integration keeps working even when X updates its internal APIs.
Returns a clean array of numeric user IDs (ids) representing every account that retweeted the target tweet.
Each response includes a next_cursor_str value, allowing seamless traversal of large retweeter lists across multiple requests.
Submit a task via POST /api/v1/jobs/createTask, optionally provide a callBackUrl, and either poll recordInfo or receive a webhook when the job completes (typically within seconds).
Build tools that monitor which accounts are amplifying trending tweets in real time.
Identify high-signal accounts that consistently retweet content in a specific niche or from specific creators.
Cross-reference retweeter IDs across multiple tweets to map communities and shared audiences.
Detect suspicious retweet patterns, bot amplification, or coordinated inauthentic behavior by analyzing retweeter cohorts.
X's official GET /2/tweets/:id/retweeted_by endpoint requires an approved developer account, project setup, and a paid tier for meaningful volume. ApiPass requires only an API key and works out of the box — no application, no gatekeeping.
The official X API imposes strict monthly caps (e.g., Basic tier limits and expensive Enterprise pricing for higher throughput). ApiPass charges per task on a usage basis, letting you scale retweeter lookups up or down without committing to a fixed monthly plan.
Measure which accounts help amplify branded posts and calculate true organic reach beyond raw retweet counts.
Verify that specific wallet-linked accounts actually retweeted a campaign post before distributing rewards.
Analyze which users are consistently boosting a competitor's tweets to understand their community structure.
Study information diffusion patterns, echo chambers, and network effects by collecting retweeter graphs at scale.
Sign up at ApiPass and generate a Bearer token from your dashboard.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with model set to twitter/simple/retweeters and the target tweet_id in the input field. You'll receive a taskId in response.
Call GET /api/v1/jobs/recordInfo?taskId=... (or wait for your callBackUrl to be triggered) to retrieve the ids array of retweeters and the next_cursor_str for pagination.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get the list of users who retweeted the tweet.
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "tweet_id": "string"
7 }
8}modelRequiredstringThe model name to use for generation
"twitter/simple/retweeters"
callBackUrlOptionalstringCallback URL for task completion notifications. If omitted, no callback will be sent.
"https://your-domain.com/api/callback"
channelOptionalstringYou may specify the corresponding provider within APIPASS via the channel parameter; these providers handle the actual image and video generation tasks. APIPASS currently offers three provider options:
The default value for the channel parameter is auto. When enabled, APIPASS automatically allocates tasks across available providers based on real-time pricing and stability metrics to balance minimal cost and reliable performance. Retain the default auto value unless you have custom routing requirements.
Available options:
auto
The input object contains the following parameters:
input.tweet_idRequiredstringTwitter post ID
"1694634492403843248"
1curl -X POST "https://api.apipass.dev/api/v1/jobs/createTask" \
2 -H "Content-Type: application/json" \
3 -H "Authorization: Bearer YOUR_API_KEY" \
4 -d '{
5 "model": "twitter/simple/retweeters",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "tweet_id": "1694634492403843248"
9 }
10 }'1{
2 "code": 200,
3 "message": "success",
4 "data": {
5 "taskId": "task_12345678"
6 }
7}codeStatus code, 200 for success, others for failure
messageResponse message, error description when failed
data.taskIdTask ID for querying task status and results
