𝕏 (twitter) Community API avatar

𝕏 (twitter) Community API

Pricing

from $3.75 / 1,000 results

Go to Apify Store
𝕏 (twitter) Community API

𝕏 (twitter) Community API

Twitter Community API exports up to 1,000 successfully resolved X Community profiles per run with 16 possible fields and $0.005 per result.

Pricing

from $3.75 / 1,000 results

Rating

5.0

(2)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

3

Bookmarked

3

Total users

0

Monthly active users

14 days ago

Last modified

Share

X Twitter Community API is a twitter community api that converts 1–1,000 public X Community URLs or numeric IDs into sparse 16-field profile records with identity, membership, creator, policy, topic, rule, media, and provenance data. It is built for audience research, community mapping, monitored lists, and enrichment workflows that need structured rows instead of copied pages.

Apify Users Apify Runs $0.005 / result 16-field profiles API + MCP ready

  • One run accepts a required list of 1–1,000 strict HTTPS Community URLs or positive numeric IDs.
  • Each identity-valid public Community can produce one row with 16 possible top-level fields.
  • Invalid, suspended, unavailable, or incomplete Communities do not create placeholder rows or Result charges.
  • Images remain in output only when they can be stored successfully; text records survive an individual media failure.

The smallest useful FREE-tier run costs $0.01 for Actor Start plus $0.005 for one saved Community Result, or $0.015 total.

Why Choose X Twitter Community API

Batch community profiles. Submit one URL for a low-risk check or process up to 1,000 identifiers in the same run. Stable deduplication prevents repeated IDs from creating duplicate work or duplicate rows.

Useful public context. A successful record can include the Community name, description, creator identity and verification flags, member count, join policy, creation time, NSFW flag, primary topic, current tags, rules, stored banner, and stored featured-member images.

Truthful partial outcomes. A batch can retain successful rows even when another ID is suspended or unavailable. Missing communities are reported in the terminal counts but are not mislabeled as successful Dataset items.

Traceable exports. Every retained row carries status, processor, and processed_at, so downstream systems can identify the producing Actor and observation time alongside the public profile values.

Quick Start Guide

Step 1: Configure

Open the input form and keep the working Life AI Community prefill, or replace it with a canonical URL such as https://x.com/i/communities/1522493647744376833. Numeric IDs are also accepted.

Step 2: Run

Start the Actor and wait for the terminal message. The message reports ready, unavailable, and failed counts separately; inspect the Dataset count because a valid ID can still be unavailable at collection time.

Step 3: Collect

Open the default Dataset and export successful rows as JSON, CSV, Excel, XML, or RSS. Preserve the run ID and processed_at field when comparing snapshots collected on different dates.

{
"community": [
"https://x.com/i/communities/1992144505747931156"
]
}

Input Parameters

X Twitter Community API exposes one required property.

ParameterTypeRequiredLimitsDescription
communityarray of stringsYes1–1,000 itemsHTTPS X or Twitter Community URLs and positive numeric Community IDs

The accepted URL path is exactly /i/communities/{id} on x.com, www.x.com, twitter.com, or www.twitter.com. URLs must use HTTPS and must not include credentials or a custom port. Plain IDs must be positive decimal integers in the signed 64-bit range.

Invalid values are ignored when at least one valid ID remains. Duplicate normalized IDs are removed in first-seen order. The input ceiling is not a result guarantee: a suspended, unavailable, incomplete, or identity-mismatched Community does not create a row.

Output Data Schema

Each successful Community produces one sparse Dataset item with up to 16 top-level fields.

GroupFieldsMeaning
Identityid, display_name, descriptionResolved Community identity and public summary
Creator and accesscreator, join_policy, created_at, is_nsfwCreator flags, membership policy, creation time, and safety flag
Discoverymember_count, community_topic, community_tagsPublic size and categorization signals
Governancecommunity_rulesRule names and descriptions when supplied
Stored mediabanner_url, members_facepileRecord URLs only for images stored successfully
Processingstatus, processor, processed_atOutcome, producing Actor, and observation time

This abbreviated example uses a real successful shape; optional stored media and tags are omitted because they were not retained in that local evidence run.

{
"status": "success",
"processor": "https://apify.com/agentx/x-twitter-community-api",
"processed_at": "2026-08-12T18:26:37+00:00",
"id": "1522493647744376833",
"display_name": "Data Engineering",
"description": "Talk about data engineering and other data-related topics",
"creator": {
"user_name": "Al_Grigor",
"blue_verified": true,
"verified": false
},
"join_policy": "RestrictedJoinRequestsRequireModeratorApproval",
"member_count": 8486,
"is_nsfw": false,
"community_topic": "Software",
"community_rules": [
{"name": "Be kind and respectful."}
]
}

Optional keys are omitted when the source does not supply a usable value. Absence does not prove the real-world value is empty, zero, current, or complete.

Integration Examples

Use Actor ID Rh9WgmwbWqdEG2dUb or name form agentx/x-twitter-community-api from HTTP, an SDK, an automation platform, or MCP.

curl -X POST "https://api.apify.com/v2/acts/Rh9WgmwbWqdEG2dUb/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"community":["https://x.com/i/communities/1992144505747931156"]}'
from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("Rh9WgmwbWqdEG2dUb").call(run_input={
"community": ["https://x.com/i/communities/1992144505747931156"],
})
items = list(client.dataset(run["defaultDatasetId"]).iterate_items())
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('Rh9WgmwbWqdEG2dUb').call({
community: ['https://x.com/i/communities/1992144505747931156'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
{
"actor": "agentx/x-twitter-community-api",
"input": {
"community": ["https://x.com/i/communities/1992144505747931156"]
},
"callOptions": {"memory": 128, "timeout": 300},
"waitSecs": 60
}

If a client wait window expires, poll the returned run ID instead of starting a duplicate. Keep Apify tokens in server-side secrets rather than browser code, logs, Datasets, or support messages.

Pricing

X Twitter Community API uses pay-per-event pricing: Actor Start is $0.01 and each saved Community Result ranges from $0.005 to $0.00375 by plan.

EventFREEBRONZESILVERGOLDPLATINUMDIAMOND
Actor Start$0.01000$0.01000$0.01000$0.01000$0.01000$0.01000
Community Result$0.00500$0.00450$0.00400$0.00375$0.00375$0.00375

Actor Start is charged once per run. Community Result is repeatable and is charged only after a successful row is saved. A FREE run with one row costs $0.01 + $0.005 = $0.015; a run with 100 saved rows costs $0.01 + (100 × $0.005) = $0.51. An unavailable input has no Result charge. Prices can change, so review the current pricing page before setting a maximum total charge.

Use Cases

Community landscape mapping. Compare display_name, description, community_topic, community_tags, and member_count across a selected market or interest area.

Partnership qualification. Review creator identity, join policy, public rules, size, and topic before deciding whether a Community warrants deeper manual research.

Monitored panels. Schedule the same IDs and store processed_at with each snapshot to observe directional changes in names, descriptions, member counts, policies, or rules.

Governance review. Use is_nsfw, join_policy, and community_rules as preliminary context while keeping human review and the current Community page in the decision loop.

Data enrichment. Join successful rows to creator, company, content, or search-interest datasets by explicit IDs and timestamps. Do not treat membership as consent, affiliation, engagement, or purchase intent.

Alternatives

Manual browsing is suitable for one consequential Community when a researcher needs current posts and platform context. It becomes difficult to repeat consistently across tens or hundreds of known IDs, and copied values lose timestamps and structured provenance.

X provides an official Community lookup endpoint for approved developer access. Choose it when an organization requires the official credentialed API and its policy, quota, field, and support contract. This Actor is an independent public-profile data tool and is not the official X API.

Choose a different product when the job requires Community posts, a full member or moderator list, invitations, moderation actions, private data, engagement analytics, or keyword discovery across unknown Communities.

Limits and Troubleshooting

  • Fewer rows than inputs: invalid and duplicate values are normalized away; suspended, unavailable, incomplete, or identity-mismatched Communities create no row.
  • No Dataset row: open the Community URL manually, confirm the numeric ID and HTTPS path, inspect the terminal counts, and retry later.
  • Missing optional field: treat absence as “not observed in this snapshot,” not as a factual zero or empty real-world value.
  • Missing media: keep the valid text record; an image reference is removed when the asset cannot be downloaded and stored safely.
  • Changing counts: preserve processed_at and require repeated observations before interpreting membership movement.
  • Expired API wait: poll the existing run by ID rather than creating a duplicate chargeable run.

For support, include the run ID, redacted input, terminal status, Dataset item count, expected field, and observed key set. Never include tokens, credentials, private Dataset content, or unrelated personal information.

Trust and Reliability

Apify supplies run isolation, storage, schedules, webhooks, Dataset exports, and API access. The Actor declares one input property, a 1,000-item ceiling, and a 16-field Dataset contract, while billing Community Results only after rows are retained.

Output values come from the public source response plus processing metadata; absent values are not invented. X controls Community availability, visibility, and source behavior, so field density and row availability can change independently of this Actor.

The official X Communities help page explains that Communities are managed by admins and moderators, can use different join policies, and can be suspended. That source boundary is why unavailable Communities are excluded instead of emitted as successful profiles.

Public-data scope. The Actor accepts public identifiers and does not accept user credentials or cookies. Public visibility does not remove privacy, intellectual-property, database-right, contractual, consumer-protection, or sector-specific obligations.

Responsible use. Establish a lawful purpose, minimize retained data, protect Datasets and tokens, honor deletion and suppression duties, and add human review before consequential decisions. A member count or featured avatar does not imply consent, affiliation, demographic identity, or permission to contact anyone.

Platform terms. Review the current X Terms of Service and Apify General Terms. Do not use the Actor to bypass access controls, manipulate engagement, harass people, or process data you are not permitted to use.

Frequently Asked Questions

How do I use a twitter community api without an X developer key?

Run X Twitter Community API with a public Community URL or numeric ID and an Apify token. The Actor does not ask for an X developer key, but it remains an independent tool rather than the official X API.

How can I export X Community profiles in bulk?

Put up to 1,000 valid identifiers in community, run the Actor, and export the successful Dataset rows. Row count can be lower than input count because unavailable Communities do not produce placeholders.

Does the Actor return Community posts?

No. It returns Community profile metadata, not posts, replies, timelines, or engagement analytics.

Does members_facepile contain the full member list?

No. members_facepile contains only stored images from the small featured-member presentation returned with the profile; it is not a complete member or moderator list.

Is there a free X Community API?

The Actor uses pay-per-event pricing rather than promising a permanently free service. A smallest successful FREE-tier run costs $0.015, subject to current Apify pricing and account terms.

Can I schedule runs to monitor Communities over time?

Yes. Use Apify schedules, retain processed_at, and compare repeated snapshots cautiously because source values and availability can change.

Why was a suspended Community omitted?

Suspended or unavailable Communities do not provide an identity-valid successful profile. The Actor counts them as unavailable and does not charge a Community Result for them.

AgentX includes 77 Actors across social data, jobs, property, shopping, media, and automation categories. These three are the closest extensions for a Community-profile workflow:

Business and Market Intelligence

Jobs and Hiring

Social Media

Video, Transcripts and Downloads

E-Commerce and Retail

Classifieds and Automotive

Real Estate

Support and Community

Ask about Community inputs, unavailable IDs, sparse fields, pricing, Datasets, and integrations in the AgentX community on Telegram; for a reproducible bug, open an Issue with the run ID and exact redacted input.

AgentX is an Arcyton brand — arcyton.com.

Last Updated: August 12, 2026