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 |
|---|---|---|---|---|---|
blue-verified-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
blue-verified-followers
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve the complete list of Twitter Blue verified users who follow any target account with a single API call.
The Twitter Graphql Blue Verified Followers API on ApiPass is a specialized endpoint that lets developers programmatically fetch all Twitter Blue (X Premium) verified accounts following a specific user. By simply passing a `userId`, along with a `count` and `includePromotedContent` flag, you receive a rich, structured JSON payload containing each verified follower's profile core data (name, screen name, creation date), avatar, banner, bio, follower/following counts, professional category, verification status, and relationship perspectives. Built on Twitter's internal GraphQL layer, this API bypasses the limitations of the official REST API and delivers deeper, more detailed follower intelligence in real time.
Instantly isolate premium, high-signal followers without having to fetch every follower and filter manually.
Get far more than IDs; each result includes profile images, banners, bios, professional business categories, and engagement metrics.
Built-in `cursorType: Bottom` and `Top` cursors make it easy to paginate through large follower lists without missing entries.
Skip the lengthy application process for X API access; authenticate with a single ApiPass Bearer token.
Submit a job, receive a `taskId`, and either poll `recordInfo` or receive results via your `callBackUrl` — perfect for large-scale batch workflows.
Avoid the steep monthly tiers of the official X API and pay only for the tasks you actually run.
Returns the timeline entries containing all Blue-verified follower user objects with `is_blue_verified: true`.
Each entry exposes core identity, legacy metrics (followers, friends, statuses, favourites, media), professional info, dm permissions, and relationship state.
Use the `count` parameter to control how many verified followers are returned per request, optimizing for speed or completeness.
Visualize the quality and composition of a creator's premium follower base.
Track which Blue-verified accounts follow your competitors and identify overlap with your own audience.
Extract verified business accounts (with professional category data like "Vitamins/Supplements Manufacturer") from a target's follower list.
Automatically recognize, tag, or reward premium verified followers of a brand account.
The official X API requires a paid developer subscription and gated access to follower endpoints, while ApiPass gives you the same GraphQL-level data with just an API key — no approval process, no monthly minimums.
Twitter's official REST followers endpoint returns a generic follower list without native Blue filtering; ApiPass mirrors Twitter's internal GraphQL `BlueVerifiedFollowers` query, returning pre-filtered verified followers with the same field depth the web client sees.
Measure the ROI of campaigns aimed at attracting premium Twitter Blue users.
Review the verified accounts associated with your brand or your executives' profiles.
Study how verified follower counts and profiles evolve across accounts, industries, or regions over time.
Push verified follower profile data (screen name, bio, website URL, professional category) into your CRM to power personalized outreach.
Sign up on ApiPass and generate a Bearer token from your dashboard.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with the model twitter/graphql/blue-verified-followers, passing the target userId, desired count, and includePromotedContent in the input.variables object. You'll receive a taskId in response.
Either configure a callBackUrl to receive results automatically once the task completes, or call GET /api/v1/jobs/recordInfo?taskId=... to fetch the full resultJson containing the timeline of Blue-verified follower user objects.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get Blue V Fan 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/blue-verified-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/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 }
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
