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 |
|---|---|---|---|---|---|
create-retweet 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
create-retweet
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Programmatically retweet any public tweet on X (formerly Twitter) using a single API call powered by ApiPass.
The Twitter Graphql Create Retweet API on ApiPass is a managed endpoint that lets developers automate retweet actions on X without touching Twitter's undocumented internal GraphQL infrastructure. By sending a POST request to /api/v1/jobs/createTask with the model twitter/graphql/create-retweet, a target tweet_id, and your X auth_token, ApiPass handles the underlying GraphQL mutation, authentication headers, rate-limit routing, and provider selection on your behalf. The API operates asynchronously — you receive a taskId immediately, then poll /api/v1/jobs/recordInfo (or receive a callback) to confirm that the retweet has been successfully published. This abstraction turns a complex, fragile reverse-engineered flow into a reliable, production-grade HTTP call.
Skip Twitter's lengthy developer application, project tiers, and elevated-access reviews. Simply grab your auth_token cookie and start retweeting programmatically.
ApiPass routes tasks through starter, regular, and official provider channels, letting you cut costs by orders of magnitude compared to X's paid API tiers.
The default channel: auto setting dispatches each retweet task to the best-performing provider in real time, balancing price, stability, and speed automatically.
Fire off retweets at scale and receive results via an optional callBackUrl, eliminating the need for constant polling in high-volume workflows.
A minimal request body (model, AuthToken, tweet_id) replaces the dozens of headers, CSRF tokens, and query hashes required by the raw GraphQL endpoint.
Combine create-retweet with ApiPass's other Twitter GraphQL endpoints (user lookup, tweet search, like, follow) under a single API key and billing account.
Every retweet request returns a taskId with lifecycle states (waiting, queuing, generating, success, fail) so you can track and audit every action.
Choose between starter (ultra-low-cost), regular (balanced), and official (native X API) channels to match your reliability and budget requirements.
Uses the standard auth_token browser cookie, allowing you to authenticate any X account without OAuth flows or developer app registration.
Programs that detect trending posts from selected creators and instantly retweet them to boost reach.
SaaS tools that let agencies schedule and execute retweets across multiple client accounts from a single UI.
Workflows that automatically retweet your brand's own posts across secondary X accounts to maximize organic distribution.
Discord/Telegram integrations that reward community members by auto-retweeting their contributions from an official brand account.
See how ApiPass compares to X's official developer platform in terms of access, cost, and developer experience — and why teams choose ApiPass for production retweet automation.
The official X API requires a paid developer account (Basic tier starts at $200/month) plus write-permission approval to call the POST /2/users/:id/retweets endpoint. ApiPass requires only an API key and an auth_token cookie — you can be retweeting in under five minutes.
The official API enforces strict monthly write caps tied to your subscription tier, with overages requiring enterprise contracts. ApiPass charges per successful task and offers a starter channel for high-volume, cost-sensitive use cases where the official tier would be prohibitively expensive.
Coordinate synchronized retweets across a network of influencer accounts to launch a campaign with maximum initial velocity.
Automatically retweet breaking news, price alerts, or emergency updates from a source account the moment they're published.
Retweet posts from targeted niche communities to build visibility and reciprocal engagement for a new account.
Power a themed curation account that retweets the best content matching specific keywords, hashtags, or author lists in real time.
Sign up on ApiPass to get your Bearer API key. Then open twitter.com in your browser, log in, and copy the auth_token value from F12 → Application → Storage → Cookies.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with the model set to twitter/graphql/create-retweet, including your AuthToken and the target tweet_id inside the input object. Optionally provide a callBackUrl to receive completion notifications automatically.
Use the returned taskId to poll GET /api/v1/jobs/recordInfo?taskId=task_12345678, or wait for ApiPass to POST the result to your callBackUrl. When state becomes success, the retweet is live on X.
All APIs require authentication via Bearer Token.
Authorization: Bearer
retweet
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "AuthToken": "string",
7 "variables": {
8 "tweet_id": "string"
9 }
10 }
11}modelRequiredstringThe model name to use for generation
"twitter/graphql/create-retweet"
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.tweet_idRequiredstring123
input.AuthTokenRequiredstringOpen the Twitter homepage, log in, then go to F12 > Application > Storage > Cookies > auth_token.
YOUR_X_AUTH_TOKEN
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/create-retweet",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "AuthToken": "YOUR_X_AUTH_TOKEN",
9 "variables": {
10 "tweet_id": "1852944751370109241"
11 }
12 }
13 }'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
