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-graphql
Retrieve the complete list of users who retweeted any public tweet with a single API call.
The Twitter Graphql Retweeters API on ApiPass is a managed endpoint that lets developers programmatically fetch the list of users who retweeted a specific tweet on X (formerly Twitter). By submitting a tweetId along with optional pagination and filtering parameters, you receive a structured dataset of retweeting accounts—ideal for engagement analysis, audience research, and content amplification tracking. Built on an asynchronous task model, the API handles heavy lifting in the background: you create a task with POST /api/v1/jobs/createTask using the model twitter/graphql/retweeters, then poll or receive a callback to retrieve the result via /api/v1/jobs/recordInfo. This decouples your application from rate limits and long-running requests, making large-scale retweeter data collection simple and reliable.
No need to manage Twitter developer accounts, OAuth flows, or rotating credentials. A single ApiPass Bearer API key unlocks every endpoint.
The default channel: auto setting allocates each task across available providers based on real-time pricing and stability metrics, balancing minimal cost with reliable performance.
Submit a task and receive a taskId instantly. The system handles fetching in the background, so your app never blocks on slow upstream responses.
Provide a callBackUrl and ApiPass will push results to your server the moment the task completes—no polling required.
Choose between starter (ultra-low-cost), regular (standard, well below official pricing), and official (native Twitter API stability and speed) to match your budget and SLA needs.
Results are returned in a clean JSON envelope (code, message, data.resultJson) with explicit task lifecycle states (waiting, queuing, generating, success, fail) for easy integration.
Pass any public tweetId (e.g., 1694634492403843248) to retrieve the retweeter list for that exact post.
Use the count parameter (default 20) to control how many retweeter records are returned per task, optimizing for either speed or completeness.
Toggle includePromotedContent (boolean) to include or exclude promoted/ad-related entries in the response, keeping organic engagement data clean.
Identify high-reach accounts that amplify specific posts and surface them as outreach prospects.Identify high-reach accounts that amplify specific posts and surface them as outreach prospects.
Visualize who is spreading your content—or your competitors'—over time.
Feed retweeter lists into CRM or ML systems to build lookalike audiences and refine targeting.
Trigger alerts and downstream workflows whenever notable accounts retweet specific tweets you care about.
While the Twitter Official API provides direct access to retweeter data, it comes with significant barriers—strict developer approval, tiered usage caps, and fixed pricing that scales quickly with volume. ApiPass offers a streamlined alternative that delivers the same data through a simpler integration model, flexible provider routing, and dramatically lower costs.
The Twitter Official API requires an approved developer account and enforces strict per-tier monthly post caps and rate limits on its retweet-lookup endpoints. ApiPass abstracts all of this away—just send a request with your API key and pay only for the tasks you run.
While the Twitter Official API offers a single fixed pricing model, ApiPass automatically routes your task across starter, regular, and official channels to deliver the same retweeter data at a fraction of the price, with official always available when you need parity with the native service.
Measure which influencers and communities drove the spread of a branded tweet.
Track who is retweeting competitor announcements to map their advocate networks.
Quickly enumerate amplifiers of a viral or sensitive post to inform response strategy.
Collect structured retweet propagation data for studies on information diffusion, misinformation, or network analysis.
Sign up on ApiPass and generate a Bearer token from your dashboard. This single key unlocks every endpoint, with no Twitter developer account or OAuth setup required.
Send a POST request to /api/v1/jobs/createTask with the model set to twitter/graphql/retweeters, your target tweetId, and optional parameters such as count and includePromotedContent. You can also include a callBackUrl to receive results automatically. The API will instantly return a taskId you can use to track progress.
Either wait for ApiPass to push the results to your callBackUrl, or poll GET /api/v1/jobs/recordInfo?taskId=YOUR_TASK_ID until the state field becomes success. The complete retweeter list will be available inside data.resultJson.resultObject, ready to be consumed by your application.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get the list of users who retweeted
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "variables": {
7 "tweetId": "string",
8 "count": "number",
9 "includePromotedContent": "boolean",
10 }
11 }
12}modelRequiredstringThe model name to use for generation
"twitter/graphql/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.variables.tweetIdRequiredstring1694634492403843248
input.variables.countOptionalnumber20
input.variables.includePromotedContentOptionalbooleanfalse
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/graphql/user-by-screen-name",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "variables": {
9 "tweetId": "1694634492403843248",
10 "count": 20,
11 "includePromotedContent": false,
12 }
13 }
14 }'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
