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 |
|---|---|---|---|---|---|
user-tweets-and-replies 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
user-tweets-and-replies
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve a complete timeline of any Twitter user's tweets and replies with a single API call.
The Twitter Graphql User Tweets and Replies API on ApiPass is a powerful endpoint that fetches a Twitter user's complete activity timeline — including original tweets, replies, retweets, and community posts — by querying with a simple user ID. Built on Twitter's GraphQL infrastructure, this API gives developers programmatic access to chronological tweet and reply data without the need to scrape pages, manage authentication tokens, or maintain complex infrastructure. ApiPass handles the routing, provider selection, and request orchestration through an asynchronous task-based workflow, so you can focus on building your application instead of wrestling with Twitter's backend complexities.
Capture not just original tweets but also replies, community posts, and voice tweets in one unified response, giving you a 360° view of a user's activity.
With the default channel: auto setting, ApiPass automatically allocates your task across multiple providers based on real-time pricing and stability metrics, balancing cost efficiency with reliable performance.
Choose between starter, regular, and official provider tiers depending on whether you prioritize ultra-low cost, balanced performance, or maximum stability with official-grade infrastructure.
Submit your request, receive a taskId, and either poll for results or receive automatic notifications via your callBackUrl — perfect for processing large batches without blocking your application.
Fine-tune what's included in your response using boolean flags like withCommunity, withVoice, withV2Timeline, and includePromotedContent to minimize payload size and only fetch what you need.
Get started instantly with a simple API key — no OAuth dance, no Twitter developer account approvals, no rate-limit headaches.
Pass any valid Twitter userId (e.g., 44196397) and immediately retrieve their tweets and replies timeline without needing screen names or session cookies.
Control how many timeline entries to return per request using the count parameter, giving you full pagination flexibility for both small lookups and bulk historical data collection.
Monitor your request through five clear lifecycle states (waiting, queuing, generating, success, fail) via the /api/v1/jobs/recordInfo endpoint, with detailed timing metadata including createTime, completeTime, and costTime.
Surface insights about how a user interacts with their community by analyzing the ratio of original tweets to replies, response times, and conversation threads.
Build automated archival systems that preserve a user's complete tweet history, including replies and community posts, for journalism, research, or compliance use cases.
Collect high-volume conversational data from public Twitter accounts to fine-tune language models, sentiment classifiers, or recommendation engines.
While both ApiPass and Twitter's official API can deliver user tweets and replies data, they differ significantly in pricing model, integration complexity, and operational overhead. Here's how ApiPass stands apart from the official X API:
Twitter's official API (X API v2) requires a paid developer account with tiered subscriptions that can cost hundreds to thousands of dollars per month for meaningful access. ApiPass provides the same user-tweets-and-replies data through a pay-per-task model with three provider tiers, including an ultra-low-cost starter channel — letting you start small and scale economically without enterprise commitments.
While the Twitter official API uses synchronous REST/GraphQL calls subject to strict per-window rate limits and OAuth 2.0 token management, ApiPass abstracts everything into a clean asynchronous task pattern. You submit one POST to createTask, optionally register a callBackUrl, and receive results when ready — no manual rate-limit handling, no token refresh logic, no infrastructure overhead.
Evaluate an influencer's authentic engagement by examining the volume and quality of their replies in addition to their headline tweets, helping brands make smarter partnership decisions.
Continuously monitor executive or brand accounts to detect controversial tweets or reply threads early, enabling PR teams to respond before incidents escalate.
Collect public conversational data on political figures, journalists, or thought leaders to study discourse patterns, polarization, and community dynamics at scale.
Pull replies from your official support account to analyze response patterns, common customer pain points, and unresolved threads requiring follow-up.
Sign up on ApiPass and generate a bearer token from your dashboard. This single API key gives you access to the entire Twitter GraphQL endpoint suite, with no additional Twitter developer account or OAuth approval required.
Send a POST request to the createTask endpoint with the model set to twitter/graphql/user-tweets-and-replies. Provide the target userId along with any optional parameters such as count, withCommunity, withVoice, withV2Timeline, and includePromotedContent to fine-tune your response. Optionally include a callBackUrl so ApiPass can notify your server automatically when the task completes. You'll receive a unique taskId in the response, which you'll use to fetch your results.
Either wait for the callback notification to hit your callBackUrl, or poll the recordInfo endpoint with your taskId to check status. Once the state field returns success, the resultJson will contain the full user tweets and replies timeline ready for parsing and downstream use in your application.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get user tweets and reply timelines
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 "userId": "string",
8 "count": "number",
9 "includePromotedContent": "boolean",
10 "withCommunity": "boolean",
11 "withVoice": "boolean",
12 "withV2Timeline": "boolean",
13 }
14 }
15}modelRequiredstringThe model name to use for generation
"twitter/graphql/user-tweets-and-replies"
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.userIdRequiredstring44196397
input.variables.countOptionalnumber20
input.variables.includePromotedContentOptionalbooleanfalse
input.variables.withCommunityOptionalbooleantrue
input.variables.withVoiceOptionalbooleantrue
input.variables.withV2TimelineOptionalbooleantrue
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 "userId": "44196397",
10 "count": 20,
11 "includePromotedContent": false,
12 "withCommunity": true,
13 "withVoice": true,
14 "withV2Timeline": true,
15 }
16 }
17 }'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
