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 |
|---|---|---|---|---|---|
followers 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
followers
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve the complete follower list of any public Twitter (X) account with a single API call — no OAuth, no developer approval, no rate-limit headaches.
The Twitter Graphql Followers API on ApiPass is a managed endpoint that taps directly into Twitter's internal GraphQL layer to return the followers of any public X account. By submitting a target userId to the /api/v1/jobs/createTask endpoint with the model twitter/graphql/followers, you receive a taskId you can poll (or have delivered via webhook callback) to retrieve a rich JSON payload containing each follower's profile metadata — including screen name, bio, follower/following counts, verification status, profile images, creation date, and more. Unlike the official X API, which launched pay-per-use as the default on February 6, 2026, charging credits per API request and requires complex OAuth flows, ApiPass wraps everything behind a simple bearer-token REST call so you can start exporting follower data in minutes.
Skip Twitter's multi-step app review and key-rotation process. Authenticate with a single Authorization: Bearer YOUR_API_KEY header and start pulling follower data immediately.
The official X API charges meaningful per-resource fees, and pay-per-use has a hard ceiling of 2 million post reads per month, above which X requires you to move to Enterprise pricing that starts at $42,000 per month. ApiPass routes your request to the most cost-efficient provider automatically.
The default channel: auto setting allocates each task across available providers in real time based on pricing and stability, so you get the best balance of cost and reliability without writing routing logic yourself.
Submit a task, get a taskId, and either poll /api/v1/jobs/recordInfo or receive a callback at your callBackUrl when the job finishes. Perfect for batch follower exports that would otherwise time out a synchronous request.
You receive the complete raw timeline structure Twitter's own clients see, including user_results.result.legacy fields, professional profile data, is_blue_verified flags, and affiliate badges — fields the official v2 REST API often strips or hides behind expansion parameters.
Pick starter for ultra-low-cost bulk jobs, regular for balanced production workloads, or official when you need stability and speed identical to Twitter's native API — all behind a single unified endpoint.
Each follower entry returns the full TimelineUser object: rest_id, screen_name, name, description, followers_count, friends_count, statuses_count, created_at, profile_image_url_https, profile_banner_url, verification status, pinned tweet IDs, and professional category metadata.
Control how many follower records you pull per task via the input.variables.count parameter, with userId as the only required field. Toggle includePromotedContent to filter promoted entries out of your results.
Every job exposes clear states — waiting, queuing, generating, success, or fail — along with createTime, completeTime, and costTime fields so you can monitor performance and surface failure reasons directly to your users.
Visualize a creator's, brand's, or competitor's follower growth, audience demographics, verified-follower ratio, and influencer overlap.
Pull followers of relevant industry accounts, score them by bio keywords and follower count, and push qualified prospects into your sales pipeline.
Identify high-signal followers (verified, large followers_count, niche professional categories) of any target account to source creators for campaigns.
Export follower networks for sentiment analysis, community detection, or longitudinal studies on how audiences shift around public figures and topics.
See how ApiPass stacks up against Twitter's official API on pricing, access requirements, and response richness — and why most developers ship faster with ApiPass.
The official X API operates on a pay-per-use credit system where owned reads — requests made by your own developer app for your own data such as posts, bookmarks, followers, and lists — are priced at $0.001 per resource, but pulling followers of other accounts requires standard (non-owned) read pricing that costs significantly more, plus a paid tier subscription. ApiPass has no monthly subscription floor, no developer approval gate, and no 2M-read ceiling — you pay per task and can target any public account from day one.
The official v2 REST API returns normalized JSON that requires expansion parameters and field assembly to get richer data, and rate limits are per-endpoint, per-auth-type, and per-15-minute window, returning a 429 status code when exceeded. ApiPass exposes the raw Twitter GraphQL response — every legacy field, professional badge, and affiliate label included by default — behind a simple async task model with no 15-minute windows to manage.
Periodically export a competitor's follower list to track who their audience overlaps with yours and discover untapped segments.
Analyze new followers' account age (created_at), statuses_count, and default_profile_image flag to flag inauthentic engagement on owned accounts.
Snapshot follower lists at launch milestones to airdrop tokens, gate Discord access, or reward early supporters of a creator account.
Pull the followers of journalists, analysts, and thought leaders in a vertical to map influence networks and refine outreach lists.
Sign up at ApiPass, generate a bearer token from your dashboard, and copy it into your Authorization: Bearer YOUR_API_KEY header.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with model: "twitter/graphql/followers" and an input.variables object containing the target userId (required), plus optional count and includePromotedContent fields. Include a callBackUrl if you'd like webhook notifications. You'll receive a taskId in response.
Either wait for the callback to fire at your callBackUrl, or GET https://api.apipass.dev/api/v1/jobs/recordInfo?taskId=task_xxxx to poll until state is success. The full follower payload — including every user's profile metadata, verification status, and engagement counts — will be available in data.resultJson.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get the follower list.
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 }
11 }
12}modelRequiredstringThe model name to use for generation
"twitter/graphql/followers"
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
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/followers",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "variables": {
9 "userId": "44196397",
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
