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 |
|---|---|---|---|---|---|
following 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
following
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve the complete list of accounts a Twitter user is following through a single, reliable API call.
The Twitter Graphql Following API on ApiPass is an asynchronous task-based endpoint that retrieves the list of accounts a specified Twitter user is following. By submitting a simple POST request with a target userId, developers receive a task ID that can be queried to obtain a rich JSON payload containing detailed profile information for each followed account — including screen names, bios, follower counts, verification status, profile images, professional categories, and more. Built on Twitter's GraphQL infrastructure, this API delivers the same depth of data as Twitter's native clients while offering flexible pricing tiers, automatic provider routing, and callback notifications to simplify integration into any application or workflow.
Every followed account returns extensive metadata including followers_count, friends_count, description, profile_image_url_https, created_at, is_blue_verified, and professional category, so you get a complete social graph snapshot in one call.
With the default channel: auto setting, ApiPass automatically allocates tasks across available providers based on real-time pricing and stability metrics, balancing minimal cost with reliable performance.
Choose between starter (ultra-low-cost), regular (standard tier priced far below official APIs), or official (native Twitter API pricing with maximum stability) to match your budget and reliability needs.
Submit a task and receive an immediate taskId, freeing your application from long-running blocking requests — ideal for large-scale scraping and background jobs.
Provide a callBackUrl and ApiPass will automatically notify your server when the task completes, eliminating the need to poll for status.
A single Bearer API key grants access to the entire Twitter GraphQL suite on ApiPass, no OAuth handshakes, no developer application approval, no rate-limit juggling across multiple credentials.
Returns nested user_results objects with legacy fields, professional profile categories, affiliate badges, and verification flags — mirroring the exact structure Twitter's own clients consume.
Use the count parameter (default 20) to control how many following entries are returned per task, letting you optimize between latency and payload size.
Toggle the includePromotedContent boolean to filter out sponsored entries and receive only organic following relationships, keeping your dataset clean for analytics.
Map out who influential accounts follow to uncover hidden networks, industry clusters, or emerging communities.
Track which accounts your competitors follow to reveal partnerships, industry watchlists, and strategic interests.
Build recommendation engines that suggest new accounts to follow based on the following lists of similar users.
Analyze the quality and relevance of an influencer's outbound following to assess authenticity before brand collaborations.
See how ApiPass streamlines access, enriches response data, and reduces costs compared to Twitter's native following endpoint.
Twitter's official GET /2/users/:id/following endpoint requires an approved developer account, an X API paid tier subscription, and strict per-app rate limits. ApiPass eliminates this friction: sign up, obtain an API key, and start querying immediately — with starter and regular channels priced significantly below Twitter's official rates.
The official API returns a limited set of user fields and requires synchronous pagination with cursor tokens. ApiPass returns the full GraphQL response — including professional category, affiliates_highlighted_label, is_blue_verified, profile_banner_url, and pinned tweet IDs — through an async task model with optional callbacks, so you can handle high-volume workloads without managing cursors or rate-limit backoff logic.
Aggregate following lists from thought leaders in a niche to identify emerging tools, brands, and voices gaining traction.
Enrich customer profiles by pulling their public Twitter following data to personalize outreach and identify shared interests.
Study information flow, echo chambers, and network structures for peer-reviewed research or investigative reporting.
Power "accounts you might like" or "content from your network" features by leveraging real following relationships as a signal.
Sign up on ApiPass and generate a Bearer API key from your dashboard. This single key grants you access to the entire Twitter GraphQL suite, so there's no need to manage multiple credentials or complete Twitter's developer application process.
Send a POST request to /api/v1/jobs/createTask with the model set to twitter/graphql/following, the target userId, and optional parameters such as count and includePromotedContent. You can also include a callBackUrl to receive automatic notifications when the task completes, or leave it out and poll manually. The response returns a taskId you'll use in the next step.
Query /api/v1/jobs/recordInfo with the returned taskId to check task progress. Once the state field returns success, parse the resultJson payload to access the complete following list — including profile details, verification status, follower counts, and professional metadata — ready for your application.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get the following 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/following"
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/following",
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
