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-tweets-timeline 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-tweets-timeline
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve the ranked tweet timeline of any Twitter (X) community in real time with a single API call.
The Twitter GraphQL Community Tweets Timeline API on ApiPass is a powerful endpoint that fetches the full ranked timeline of tweets posted inside a specific Twitter (X) community. By simply passing a communityId, developers can access community-scoped conversations, top-ranked posts, and paginated timeline entries — including cursors for seamless scrolling and infinite loading. It's designed for developers who need reliable, structured access to community-based content on X without dealing with authentication, rate limits, or GraphQL query construction directly.
Skip the lengthy Twitter Developer application process and start pulling community data immediately with just an ApiPass API key.
ApiPass handles the underlying request infrastructure, so you're not throttled by Twitter's strict per-endpoint quotas.
Instead of crafting complex GraphQL queries with feature flags and variables, just send a clean JSON payload with a communityId.
Submit a task, receive a taskId, and optionally use a callBackUrl to get notified when results are ready — ideal for high-volume workloads.
Get community tweets ordered by relevance via the rankingMode parameter, mirroring what users see in the native X app.
The response includes top and bottom cursors, making it trivial to paginate through large community timelines.
Returns the raw GraphQL instructions array (including TimelineClearCache and TimelineAddEntries), preserving the exact structure Twitter's frontend consumes.
Fine-tune your request with count, displayLocation, rankingMode, and withCommunity to control payload size and content shape.
Receive fully parsed resultJson with community metadata, timeline entries, and cursor tokens ready for downstream processing.
Track engagement, top posts, and trending topics inside niche X communities.
Pull the latest posts from multiple communities into a unified feed for newsletters or apps.
Monitor community activity for policy violations, spam, or harmful content.
Extract discussions from industry-specific communities (crypto, AI, gaming, etc.) to detect emerging trends.
The official Twitter API requires OAuth 2.0 setup, elevated access approval, and per-user token management. ApiPass replaces all of that with a single Bearer token.
The official X API v2 does not expose a dedicated community timeline endpoint at accessible pricing tiers. ApiPass surfaces this GraphQL endpoint directly, giving developers affordable access to community data that would otherwise require enterprise-level plans.
Watch how your brand or product is discussed inside relevant X communities.
Follow communities where competitors and their users engage to spot new features or complaints.
Gather high-signal, topic-focused conversation data for fine-tuning LLMs and building datasets.
Measure post frequency, ranking shifts, and content velocity to benchmark community health over time.
Sign up at ApiPass and generate a Bearer API key from your dashboard.
Send a POST request to https://api.apipass.dev/api/v1/jobs/createTask with the model twitter/graphql/community-tweets-timeline and pass the target communityId inside the input.variables object. You'll receive a taskId in the response for tracking.
Use the returned taskId to fetch the ranked community timeline via the recordInfo endpoint at https://api.apipass.dev/api/v1/jobs/recordInfo, or configure a callBackUrl to receive results automatically once processing completes.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get the Community tweet timeline.
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 "count": "number",
9 "displayLocation": "string",
10 "rankingMode": "string",
11 "withCommunity": "boolean"
12 }
13 }
14}modelRequiredstringThe model name to use for generation
"twitter/graphql/community-tweets-timeline"
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
countOptionalnumber20
displayLocationOptionalstringCommunity
rankingModeOptionalstringRelevance
withCommunityOptionalbooleanTrue
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-tweets-timeline",
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
