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 |
|---|---|---|---|---|---|
communities-fetch-one-query 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
communities-fetch-one-query
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve complete metadata for any single X (Twitter) Community by its community ID using ApiPass's asynchronous, task-based GraphQL endpoint.
The Twitter Graphql Communities Fetch One Query API on ApiPass is a wrapper around X's internal CommunitiesFetchOneQuery GraphQL operation that lets you pull the full profile of a specific X Community — including its name, description, member count, moderators, rules, banner, join policy, and visibility — using nothing more than a communityId. Because the underlying Twitter GraphQL operation is called with variables such as communityId and withDmMuting, ApiPass exposes the exact same parameters through a clean, unified job-based interface. You submit a task to /api/v1/jobs/createTask with the model twitter/graphql/communities-fetch-one-query, receive a taskId, and then poll /api/v1/jobs/recordInfo (or receive a callback) to get the fully hydrated community object — no OAuth flow, no rate-limit juggling, and no need to reverse-engineer X's private GraphQL schema yourself.
Skip Twitter's application review, enterprise pricing tiers, and access-token rotation — authenticate with a single ApiPass Bearer key and start fetching community data immediately.
Unlike the official v2 REST API, which doesn't expose full Community objects, ApiPass mirrors the same CommunitiesFetchOneQuery operation that x.com itself uses, giving you every field the web app sees.
Fire off a task and either poll for results or supply a callBackUrl — perfect for serverless functions, queue-driven pipelines, and high-volume batch enrichment.
With channel set to auto, ApiPass automatically dispatches your request across starter, regular, and official providers based on real-time price and stability, so you never overpay or hit an outage-prone upstream.
Results are returned as a structured resultJson string, ready to parse and load into your database — no HTML scraping, no headless browsers, no cookie management.
Whether you're fetching one community for a lookup tool or hydrating tens of thousands for a research dataset, ApiPass's per-call pricing beats the cost of maintaining a scraping farm or an X Enterprise contract.
Pass any valid communityId (e.g., 1517189118140325888) and receive the community's complete GraphQL-shaped record in one round trip.
Toggle the withDmMuting boolean to control whether direct-message muting relationships between the querying account and community admins are included in the response — the same flag used natively by Twitter's CommunitiesFetchOneQuery operation, which accepts communityId and withDmMuting variables.
Every job passes through explicit waiting → queuing → generating → success / fail states, so your application always knows exactly where a request stands and can react accordingly.
Build tools that display cover images, descriptions, member counts, and moderator lists for any X Community your users paste in — perfect for community explorers, directory sites, or "preview card" widgets embedded in chat apps.
Snapshot a community's member count, rules, and admin roster over time to surface growth trends, milestone alerts, and moderation changes — ideal for analytics platforms serving community managers and social-media strategists.
Pair this endpoint with community-members or community-tweets endpoints to power the kind of workflow marketers already rely on for lead generation, competitive analysis, and audience research — turning any community ID into a rich prospect signal.
Periodically re-fetch a community's metadata to detect policy changes, ownership transfers, or visibility flips (public ↔ closed) — enabling trust-and-safety teams, brand-safety vendors, and community auditors to stay ahead of risk.
Here's how ApiPass's Communities Fetch One Query endpoint compares to what's actually available through X's official developer platform — in terms of both data coverage and developer experience.
X's official API v2 does not offer a first-class endpoint for retrieving full Community metadata by ID — Communities remain largely an x.com-app feature powered by internal GraphQL operations. ApiPass bridges that gap by exposing the very same CommunitiesFetchOneQuery operation the X web client uses, so you get parity with what's actually rendered in the UI instead of a stripped-down public subset.
The official API requires a paid X Developer tier, app review, OAuth 2.0 user context, and strict per-app rate limits. ApiPass replaces all of that with a single Bearer token, an async job queue, and auto channel routing that balances cost and reliability across multiple providers — meaning you can go from zero to production in minutes rather than weeks.
Resolve any community ID mentioned in a tweet or link to enrich your monitoring feed with real community context (name, size, topic).
When a prospect lists an X Community in their profile or your onboarding form, hydrate it into your CRM with descriptions, member counts, and admin handles.
Build reproducible datasets of Community metadata for studying online group dynamics, topic clustering, or platform governance.
Track membership policies, rules, and admin composition of communities relevant to trust-and-safety investigations or ad-suitability scoring.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with your Bearer token in the Authorization header. In the JSON body, set model to twitter/graphql/communities-fetch-one-query and include an input object containing the target communityId (and optionally the withDmMuting boolean). If you'd like results delivered automatically, add a callBackUrl pointing to your webhook endpoint.
The create-task response returns a data.taskId value (for example, task_12345678). Store this ID so you can look up the task's status and results in the next step — or simply wait for the callback to fire if you supplied a callBackUrl.
Send a GET request to https://api.apipass.dev/api/v1/jobs/recordInfo?taskId=YOUR_TASK_ID with your Bearer token. Watch the state field as it moves through waiting → queuing → generating; once it reaches success, parse the resultJson field to get the full community object — ready to persist, display, or forward downstream. If the state returns fail, inspect the accompanying failure details to diagnose and retry.
All APIs require authentication via Bearer Token.
Authorization: Bearer
communities fetch one query
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 "withDmMuting": "boolean"
9 }
10 }
11}modelRequiredstringThe model name to use for generation
"twitter/graphql/communities-fetch-one-query"
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.communityIdRequiredstringcommunityId
1517189118140325888
input.withDmMutingOptionalbooleanwithDmMuting
false
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/communities-fetch-one-query",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "communityId": "1517189118140325888",
9 "withDmMuting": false
10 }
11 }'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
