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 |
|---|---|---|---|---|---|
community-members 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
community-members
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve paginated community member data from Twitter/X communities through ApiPass's unified GraphQL endpoint — with rich user profiles, community roles, and cursor-based pagination built in.
The Twitter GraphQL Community Members API on ApiPass is an asynchronous task-based endpoint that returns the complete member list of any Twitter/X community. You submit a POST request to /api/v1/jobs/createTask with the model twitter/graphql/community-members and a target communityId, receive a taskId in return, then either poll /api/v1/jobs/recordInfo or receive a webhook callback with the results. Each response contains structured community metadata plus a paginated members_slice with detailed member records — including display name, screen name, avatar URL, rest_id, verification status (is_blue_verified), and importantly the community_role field (e.g., Admin, Member) — along with a next_cursor for continued pagination through communities of any size.
Skip Twitter's lengthy application, approval, and elevated-access process. Generate a Bearer token in your ApiPass dashboard and start calling within minutes.
At $0.0005 per call (0.1 credits), ApiPass is roughly 99.90% cheaper than the estimated cost of equivalent Twitter enterprise endpoints — a savings of ~$45.45 per 10,000 calls.
Every member record ships with profile core (name, screen_name), avatar.image_url, rest_id, verification flags, relationship perspectives, and community_role — no additional enrichment calls required.
The default channel: auto setting balances tasks across starter, regular, and official providers in real time, optimizing cost and stability without any manual configuration.
Submit once, receive a taskId, and either poll or supply a callBackUrl to have results pushed to your server the moment they're ready — perfect for large communities requiring cursor-based pagination.
Every endpoint page shows real-time success rate (currently 100%), so you always know the health of the API before you build against it.
Only input.variables.communityId is required. Pass a Twitter community ID (e.g., 1517189118140325888) and receive the full member slice — no complex GraphQL variables to configure.
Every response includes members_slice.slice_info.next_cursor, enabling you to page through communities of any size, from small niche groups to communities with tens of thousands of members.
Each member object includes a community_role field (Admin, Member, etc.), making it trivial to filter for moderators, identify power users, or map governance structures inside a community.
Snapshot membership on a schedule to visualize community size, growth curves, admin turnover, and member composition over time.
Extract member rosters from niche communities and filter by is_blue_verified or community_role to surface high-signal accounts for marketing outreach.
Map your existing customers to the Twitter communities they belong to using screen_name and rest_id, enriching profiles with community-based interest signals.
Power moderation tools, cross-platform member mirroring, or admin dashboards that community owners can integrate with Discord, Slack, or internal CRMs.
Twitter's official API requires a developer account, project setup, and (for community-level GraphQL data) higher-tier paid access — often with weeks of approval delays. ApiPass requires only an API key generated from your dashboard; you can run your first createTask request within minutes of signup.
Twitter's official Basic and Pro tiers cost hundreds to thousands of USD per month with hard monthly caps. ApiPass charges $0.0005 per call on a pay-as-you-go basis across multiple provider channels — an estimated 99.90% lower cost, letting you scale community-scraping workloads without a fixed monthly commitment.
Monitor membership shifts in crypto, NFT, or DAO-related Twitter communities to detect early signals of project momentum or capital rotation.
Combine community member lists with tweet-timeline APIs to run targeted sentiment analysis on conversations happening inside specific brand or product communities.
Track competitors' Twitter communities to see who's joining, how fast they're growing, and which verified accounts overlap with your own audience.
Collect anonymized community membership datasets for studies on online group formation, information diffusion, and admin/member dynamics in decentralized social networks.
Sign up at ApiPass and generate a Bearer token from the API Key Management page in your dashboard.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with model: "twitter/graphql/community-members" and input.variables.communityId set to your target community. Optionally include a callBackUrl for webhook delivery and leave channel on auto for automatic cost/stability optimization.
Use the returned taskId to query GET /api/v1/jobs/recordInfo?taskId={taskId}. Once data.state reaches success, parse the member roster from data.resultJson.resultObject.data.communityResults.result.members_slice.items_results, and use the next_cursor to page through the remaining members.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get the list of Community members.
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 "communityId": "string",
8 }
9 }
10}modelRequiredstringThe model name to use for generation
"twitter/graphql/community-members"
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.communityIdRequiredstring1517189118140325888
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/community-members",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "variables": {
9 "communityId": "1517189118140325888"
10 }
11 }
12 }'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
