X Twitter Community Scraper

X Twitter Community Scraper is an x communities scraper that turns 1–1,000 public Community URLs or numeric IDs into sparse 16-field profile rows for research, enrichment, and monitored datasets. It keeps successful identities, omits unavailable Communities, and separates every saved row from transport or placeholder data.

• One required community list accepts 1–1,000 strict HTTPS URLs or positive numeric IDs.
• A successful Community can expose 13 business fields plus three processing fields.
• Suspended, unavailable, incomplete, or invalid entries create no placeholder row and no Result event.
• Stored media references appear only after successful image storage; an individual media failure does not discard valid text data.

Run a Community-profile test · View the API

The smallest useful FREE-tier test costs $0.01 for Actor Start plus $0.0075 for one saved Community Result, or $0.0175 total.

What does X Twitter Community Scraper do?

X Twitter Community Scraper resolves known public X Community identifiers into structured profile snapshots. A retained row can include the Community name, description, creator username and verification flags, member count, join policy, creation time, NSFW flag, primary topic, current tags, rule names and descriptions, stored banner, stored featured-member images, and collection provenance.

The Actor is designed for selected-ID workflows. It does not discover every Community matching a keyword, return Community posts, enumerate all members or moderators, invite users, perform moderation actions, or infer activity and engagement. Each input must already identify the Community that matters to the workflow.

Partial batches remain useful. If one ID resolves and another is suspended, the valid row can be saved while the suspended Community is counted as unavailable. This prevents one source-side absence from erasing successful work and prevents an unavailable payload from being marketed or billed as a profile result.

How do I run X Twitter Community Scraper?

X Twitter Community Scraper needs one list of public Community URLs or numeric IDs.

1. Open the Actor input page.
2. Keep the prefilled Data Engineering Community or enter another known identifier.
3. Start the run and wait for the terminal ready, unavailable, and failed counts.
4. Open the default Dataset and verify the successful-row count independently of the submitted-item count.
5. Save the run ID, Dataset ID, id, and processed_at value with downstream records.

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

Use a small representative list before scheduling a large recurring job. A valid numeric ID is necessary but does not guarantee that the Community remains public and available at the moment of collection.

What data does X Twitter Community Scraper return?

X Twitter Community Scraper returns one sparse Dataset item per successfully resolved Community, with up to 16 top-level fields.

Group	Fields	Meaning
Identity	id, display_name, description	Resolved Community identity and summary
Creator and access	creator, join_policy, created_at, is_nsfw	Creator flags, membership policy, time, and safety flag
Discovery	member_count, community_topic, community_tags	Public size and categorization signals
Governance	community_rules	Rule names and optional descriptions
Stored media	banner_url, members_facepile	Stored record URLs for validated images
Processing	status, processor, processed_at	Outcome, producing Actor, and observation time

The following JSON is abbreviated from a successful shape. Optional stored-media and tag fields are omitted when they are not retained.

{
  "status": "success",
  "processor": "https://apify.com/truefetch/x-twitter-community-scraper",
  "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."}
  ]
}

An omitted optional key means the source did not provide a usable retained value in that snapshot. It does not prove the real-world value is empty, zero, current, or complete.

What inputs can I configure?

X Twitter Community Scraper exposes exactly one required input property and no hidden filter.

Input	Type	Required	Limits	Accepted values
community	array of strings	Yes	1–1,000 items	Exact HTTPS X/Twitter Community URLs or positive numeric Community IDs

The accepted URL path is /i/communities/{id} on x.com, www.x.com, twitter.com, or www.twitter.com. A URL cannot carry credentials or a custom port. A plain numeric ID must be positive and fit the signed 64-bit range.

Invalid items are ignored if at least one valid ID remains. Duplicate normalized IDs are removed while preserving first-seen order. Do not use profile URLs, post URLs, search queries, handles, cookies, API keys, join-policy filters, member limits, or date filters; none belongs to this contract.

What platforms and markets does X Twitter Community Scraper cover?

X Twitter Community Scraper covers public X Communities identified by a known X or legacy Twitter Community URL or numeric ID. The input has no country, language, category, date, or market selector, so coverage must not be described as a geographic or language guarantee.

Community fields can contain text from any language the public source returns. Consumers are responsible for language detection, translation, regional interpretation, and compliance after export. The presence of a topic, creator, or member count does not prove that the Community serves a particular market.

X controls visibility, suspension, join policy, search behavior, and page availability. The official X Communities help page explains public viewing, open and restricted membership, administrator and moderator roles, and suspension behavior.

Why use X Twitter Community Scraper?

X Twitter Community Scraper replaces repeated manual profile copying with consistent inputs, sparse JSON rows, timestamps, and Dataset exports. It is most useful when a workflow already has Community IDs and needs the same public attributes across a selected list.

The Dataset contract separates successful profile rows from unavailable inputs. Downstream tools can key records by id, preserve processed_at, compare member counts or policies over time, and distinguish a missing key from an observed zero.

Pay-per-event billing follows saved outcomes. The Actor Start event covers the run, while the repeatable Community Result event is charged only after a row is stored. This makes submitted-item count, successful-row count, and billed-result count conceptually distinct and inspectable.

Who is X Twitter Community Scraper for?

Market researchers can map selected Communities by topic, description, creator, member count, and join policy before deeper review.

Partnership and community teams can qualify known spaces using public rules, creator attribution, size, and safety context without treating membership as consent or endorsement.

Data engineers can normalize URL and ID lists, export successful rows, and join them to independent creator, content, company, or search-interest datasets using explicit timestamps.

Analysts maintaining panels can schedule repeated runs and compare mutable values cautiously. They should preserve history outside the latest Dataset and avoid interpreting one snapshot as a complete activity record.

This Actor is not a fit for post collection, member enumeration, private data, automated joining, moderation, outreach, engagement prediction, or consequential decisions without human review.

How can I use X Twitter Community Scraper through the API or MCP?

X Twitter Community Scraper uses Actor ID o1jXchn04PSHWYRPG; the equivalent name form is truefetch/x-twitter-community-scraper.

curl -X POST "https://api.apify.com/v2/acts/o1jXchn04PSHWYRPG/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"community":["https://x.com/i/communities/1522493647744376833"]}'

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("o1jXchn04PSHWYRPG").call(run_input={
    "community": ["https://x.com/i/communities/1522493647744376833"],
})
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('o1jXchn04PSHWYRPG').call({
  community: ['https://x.com/i/communities/1522493647744376833'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

For MCP, connect the official Apify MCP server, refresh tool discovery, select truefetch/x-twitter-community-scraper, and pass the same community JSON object. Keep tokens in server-side secrets, validate the discovered schema, and poll the returned run ID when a client wait window expires instead of starting a duplicate run.

How much does X Twitter Community Scraper cost?

X Twitter Community Scraper costs $0.0075 per saved Community Result on the FREE tier, plus $0.01 for Actor Start; the smallest successful run is $0.0175.

Event	FREE	BRONZE	SILVER	GOLD	PLATINUM	DIAMOND
Actor Start	$0.01000	$0.01000	$0.01000	$0.01000	$0.01000	$0.01000
Community Result	$0.00750	$0.00675	$0.00600	$0.00563	$0.00563	$0.00563

Actor Start is one time per run. Community Result is repeatable and is charged only after a successful row is written. The smallest FREE-tier calculation is $0.01 + $0.0075 = $0.0175 for one retained row; an unavailable input has no Result charge. Prices can change, so check the live pricing page before setting a maximum total charge.

How does X Twitter Community Scraper compare with alternatives?

X Twitter Community Scraper is appropriate when the input is a known list of Community IDs and the desired output is a consistent public profile dataset. Manual browsing is better for one consequential review that needs current posts and visual platform context, while this Actor is better for repeatable fields, timestamps, exports, and selected batches.

X offers an official Community lookup endpoint for approved developer access. Use that endpoint when an organization requires the official credentialed API, its policy contract, and its quotas. This Actor is independent and must not be described as affiliated with or endorsed by X.

A posts product, search product, or member product is a different capability. Choose another workflow if the required output includes posts, replies, engagement, all members, all moderators, invitations, moderation actions, or discovery by keyword rather than lookup by known ID.

What are the limits and troubleshooting steps?

X Twitter Community Scraper can return fewer rows than submitted strings because normalization removes invalid and duplicate values, while suspended, unavailable, incomplete, or identity-mismatched Communities produce no placeholder.

• No row: confirm an exact HTTPS /i/communities/{id} URL or positive numeric ID, inspect the terminal counts, and open the public Community manually.
• Missing field: interpret absence as “not observed in this snapshot,” then compare a later run rather than substituting zero.
• Missing image: retain the text profile; an image is omitted if it cannot be validated and stored.
• Changed member count: preserve processed_at and compare repeated observations before drawing conclusions.
• Timed-out client wait: poll the existing run by ID rather than starting another billed run.
• Large-list uncertainty: test a small representative sample before using the 1,000-item ceiling.

When opening an Issue, include the run ID, redacted input, terminal message, Dataset row count, observed key set, and expected behavior. Never send tokens, credentials, private Dataset contents, or unrelated personal data.

Frequently asked questions

How do I scrape X Community profile data from a URL?

Put the exact public Community URL in the community array. A successful resolution creates one sparse profile row containing the source-derived keys available at collection time.

How can I export X Community profiles in bulk?

Submit up to 1,000 URLs or numeric IDs and export the successful default Dataset rows as JSON, CSV, Excel, XML, or RSS. Unavailable inputs do not create placeholders.

Does the scraper return Community posts or replies?

No. The contract is Community profile metadata only; it does not include posts, replies, timelines, or engagement analytics.

Does members_facepile contain every member?

No. It is a small stored-image presentation from the profile response, not a complete member or moderator list.

Is there a free X Community API?

This Actor uses pay-per-event pricing. The smallest successful FREE-tier run is $0.0175 under the current metadata, rather than a promise of permanently free service.

Can I schedule runs to monitor Communities over time?

Yes. Apify schedules can rerun the same IDs. Retain processed_at and compare snapshots cautiously because source values and availability can change.

Why did a suspended Community produce no row?

X says suspended Communities are no longer accessible. The Actor classifies that state as unavailable and does not charge a Community Result.

Related TrueFetch Actors

X Twitter Community Scraper pairs with exactly three TrueFetch products when a workflow expands from Community profiles to people or another platform.

• X User Profile — resolve one public X account under a separate person-profile contract.
• Reddit Community Profile — compare a public Reddit community with platform-specific fields and pricing.
• Instagram Profile API — enrich a known Instagram profile through an independent input and Dataset schema.

Review each Actor's current input limits, field contract, billing unit, and source boundary before combining records.

Support

X Twitter Community Scraper support covers accepted IDs, unavailable Communities, sparse optional fields, Result billing, Dataset access, and API or MCP integration behavior in the TrueFetch Telegram group.

Include the run ID, redacted input, terminal message, Dataset item count, observed keys, and expected behavior. Do not send credentials, tokens, private Dataset content, or unrelated personal information.

Run a Community-profile test · View the API

Last Updated: August 12, 2026