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 |
|---|---|---|---|---|---|
tweet-result-by-rest-id 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
tweet-result-by-rest-id
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve complete tweet data—including text, media, engagement metrics, and metadata—by passing a single tweet ID.
The Twitter Graphql Tweet Result By Rest Id API on ApiPass is a GraphQL-powered endpoint that allows developers to fetch the full payload of any public tweet using only its unique tweet ID (rest_id). With a simple POST request to ApiPass's unified job system, you can access tweet text, author information, media attachments (images, videos, GIFs), engagement statistics (likes, retweets, replies, quote counts), Birdwatch annotations, conversation context, and more. It mirrors Twitter's internal GraphQL schema, giving you the same rich, structured data Twitter's own web client consumes—without the complexity of managing OAuth flows, rate-limit ceilings, or enterprise pricing tiers.
Skip the lengthy application, approval, and elevated-access process. Just grab an ApiPass API key and start pulling tweets in minutes.
Avoid Twitter's $5,000+/month enterprise tiers. ApiPass charges per successful task, making it viable for indie developers and growing startups alike.
The default auto channel automatically allocates each request across starter, regular, and official providers based on real-time pricing and stability, balancing cost and reliability for you.
Get the same comprehensive data Twitter's native frontend uses, including media variants, video bitrates, conversation IDs, and editability flags—not just the slimmed-down v2 REST response.
Submit a task, receive a taskId, and either poll recordInfo or supply a callBackUrl to receive results once processing completes. Ideal for batch workflows and serverless functions.
Toggle optional flags like withHighlightedLabel, withTweetQuoteCount, withBirdwatchPivots, withVoice, and withReactions to fetch only the fields you need and keep payloads lean.
Returns full legacy fields, entities, extended_entities, conversation thread IDs, and the original GraphQL __typename, giving you everything from full_text to display_text_range.
Includes every media variant: HLS streams, MP4 renditions across multiple bitrates (288k / 832k / 2176k), aspect ratios, durations, thumbnails, focus rectangles, and monetization status.
Pull live favorite_count, retweet_count, reply_count, and quote_count values directly from Twitter's GraphQL layer at the moment of the request.
Recreate Twitter's native card preview on your own website, newsletter, or messaging app with full media and engagement data.
Track the performance of specific tweets over time for brands, influencers, or marketing campaigns.
Save snapshots of tweets for legal evidence, journalism, fact-checking platforms, or research datasets.
Feed structured tweet data into LLM fine-tuning workflows, sentiment models, or trend-detection systems.
See how ApiPass's GraphQL-powered tweet retrieval stacks up against Twitter's official v2 REST endpoint in terms of accessibility, pricing, and data depth.
Twitter's official GET /2/tweets/:id requires a Developer account with paid tiers starting at $200/month (Basic) and climbing to enterprise levels for production volume. ApiPass requires no Twitter approval and uses transparent pay-per-task pricing through its starter, regular, and official channels.
Twitter's v2 REST API returns a flattened, opt-in field schema, requiring multiple expansions and tweet.fields parameters to assemble a complete picture. ApiPass returns the full GraphQL tweetResult.result object—including legacy entities, video variants, Birdwatch pivots, and conversation metadata—in a single response.
Newsrooms and OSINT teams pull individual tweets cited in breaking stories to verify content, capture engagement at a given moment, and archive media before deletion.
Marketing platforms drill into a specific viral tweet about a product to extract sentiment-driving quotes, media assets, and reach metrics.
Agencies report on sponsored tweet performance with verified retweet, like, reply, and quote counts straight from the source.
Law firms and compliance teams retrieve immutable tweet snapshots (including video variants and timestamps) for litigation, takedown disputes, or regulatory filings.
Create an ApiPass account at apipass.dev and generate a Bearer token from your dashboard.
Send a POST request to /api/v1/jobs/createTask with the model twitter/graphql/tweet-result-by-rest-id, the target tweetId in input.variables, and optional flags such as withTweetQuoteCount or withBirdwatchPivots. Optionally include a callBackUrl to receive results automatically.
Use the returned taskId to GET /api/v1/jobs/recordInfo?taskId=... and check state. Once state is success, parse resultJson.resultObject.data.tweetResult.result to access the full tweet payload.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get tweet results by tweetId
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 "withHighlightedLabel": "boolean",
9 "withTweetQuoteCount": "boolean",
10 "includePromotedContent": "boolean",
11 "withBirdwatchPivots": "boolean",
12 "withVoice": "boolean",
13 "withReactions": "boolean",
14 }
15 }
16}modelRequiredstringThe model name to use for generation
"twitter/graphql/tweet-result-by-rest-id"
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.tweetIdRequiredstring1694513603251241143
input.variables.withHighlightedLabelOptionalbooleantrue
input.variables.withTweetQuoteCountOptionalbooleantrue
input.variables.includePromotedContentOptionalbooleantrue
input.variables.withBirdwatchPivotsOptionalbooleantrue
input.variables.withVoiceOptionalbooleantrue
input.variables.withReactionsOptionalbooleantrue
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": "1694513603251241143",
10 "withHighlightedLabel": true,
11 "withTweetQuoteCount": true,
12 "includePromotedContent": true,
13 "withBirdwatchPivots": true,
14 "withVoice": true,
15 "withReactions": true,
16 }
17 }
18 }'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
