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-you-know 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-you-know
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve the list of mutual connections — the followers you and another Twitter/X user both know — through a single GraphQL-powered API call.
The Twitter Graphql Followers You Know API on ApiPass is an asynchronous endpoint that taps into Twitter/X's internal GraphQL layer to fetch the list of accounts that both you (the authenticated user) and a target user follow in common. By submitting a target userId along with your AuthToken, ApiPass creates a background task that returns a rich timeline payload containing detailed user profiles — including screen name, display name, follower counts, verification status, professional category, and profile media — for each mutual connection. Built on ApiPass's unified task-based architecture (createTask → recordInfo), it abstracts away the complexity of Twitter's private GraphQL schema and lets developers focus purely on consuming clean, structured JSON results.
Skip the headache of decoding Twitter's private GraphQL query IDs, feature flags, and variable schemas. ApiPass handles the low-level protocol so you only pass a simple JSON body.
ApiPass automatically distributes requests across starter, regular, and official providers based on real-time pricing and stability metrics, giving you the best balance of cost and reliability without any manual configuration.
Fire off a request, get a taskId instantly, and receive results via webhook (callBackUrl) or by polling recordInfo. Perfect for batch social-graph analysis without holding open long HTTP connections.
Every mutual follower entry includes rest_id, screen_name, follower/friends counts, is_blue_verified, professional category, profile images, banner URLs, and pinned tweets — everything you need in one payload.
The starter and regular channels are priced far below Twitter's official enterprise API tiers, while the official channel offers native-parity stability when you need it.
Use your ApiPass Bearer API key for platform access and a standard Twitter auth_token cookie for user-scope data, letting you scale multiple Twitter identities under one billing account.
Use the count parameter (e.g., 20) to control how many mutual followers are returned per task, letting you tune payload size for pagination or preview scenarios.
The includePromotedContent boolean lets you cleanly exclude sponsored entries from the timeline so your dataset stays focused on organic mutual connections.
Results are returned inside a full TimelineAddEntries structure with TimelineUser items, preserving Twitter's native ordering (sortIndex) and entry IDs for downstream reconciliation.
Build sales or networking apps that surface which of your existing followers already follow a prospect, enabling warm introductions instead of cold outreach.
Visualize the overlap between your audience and any competitor, influencer, or partner account to identify shared communities and cross-promotion opportunities.
Combine mutual-follower data with is_blue_verified, followers_count, and professional category signals to score credibility before campaign spend.
Embed a mini-feed on user profile pages showing shared connections, mimicking the native "Followers you know" UX inside your own product.
Twitter's official API restricts follower-graph endpoints to expensive Enterprise tiers with strict rate limits and lengthy application reviews. ApiPass exposes the same GraphQL endpoint through a simple POST /api/v1/jobs/createTask call with pay-as-you-go pricing across three provider channels — no enterprise contract required.
The official API returns raw GraphQL responses that require you to manage query hashes, feature flags, and OAuth 2.0 with PKCE. ApiPass wraps everything into a single JSON body (model, input.AuthToken, input.variables) and returns results via callback or a lightweight GET /recordInfo?taskId=... poll, dramatically shortening integration time.
Before reaching out to a lead on X, sales teams query mutual followers to identify a warm connection who can facilitate an introduction, boosting reply rates.
Trust teams map the mutual-follower graph between suspected coordinated accounts to detect botnets, sockpuppets, or inauthentic behavior clusters.
Agencies match brands with creators whose audiences meaningfully overlap with the brand's existing followers, ensuring higher-ROI collaborations.
Researchers studying information diffusion or homophily on X collect mutual-follower edges at scale to build labeled graph datasets for network analysis.
Sign up on ApiPass to obtain your Bearer API key, then log in to Twitter/X in your browser and copy the auth_token value from F12 → Application → Cookies — this is your input.AuthToken.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with model: "twitter/graphql/followers-you-know", the target userId, your count, and (optionally) a callBackUrl. You'll receive a taskId immediately.
Either wait for the webhook to hit your callback URL or GET /api/v1/jobs/recordInfo?taskId=... until state transitions to success. Parse resultJson.resultObject.data.user.result.timeline to iterate every mutual follower entry.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get the followers you might know.
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 "userId": "string",
9 "count": "number",
10 "includePromotedContent": "boolean",
11 }
12 }
13}modelRequiredstringThe model name to use for generation
"twitter/graphql/followers-you-know"
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.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/followers-you-know",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "AuthToken": "YOUR_X_AUTH_TOKEN",
9 "variables": {
10 "userId": "44196397",
11 "count": 20,
12 "includePromotedContent": false,
13 }
14 }
15 }'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
