Twitter Community Scraper โ X Details & Rules
Pricing
from $1.00 / 1,000 results
Twitter Community Scraper โ X Details & Rules
Extract public Twitter (X) community details by URL. Get names, descriptions, member counts, topics, join policies, creator details and rules in one community row.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
ScrapingMonkey
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Collect the public description, rules and membership context of Twitter (X) communities from their URLs. Twitter Community Scraper returns the community name, member count, topic, join policy, creator details and banner in one row per community.
Use it to compare relevant communities, review participation rules or maintain a directory of public community pages.
| At a glance | Details |
|---|---|
| ๐ฅ Input | Full X or Twitter community URLs |
| ๐ค Output | Name, description, members, topic, join policy, creator and rules |
| ๐ Login required | No Twitter (X) credentials or cookies |
| โก Processing | Up to 5 requests concurrently with automatic retries |
| ๐พ Delivery | One community row in one table, with matching JSON fields |
What the Twitter (X) community scraper extracts ๐
The Actor reads the public community page and collects its available profile and rule information.
- Community ID, canonical URL, name and description
- Visible member count, topic and join policy
- Creation date and timestamp, plus the sensitive-content flag
- Banner image URL
- Creator ID, name, username, avatar and visible Blue verification flag
- Community rules with IDs, titles and descriptions
How to scrape Twitter (X) communities ๐
- Add a full community URL with an
/i/communities/path. - Add other community links for a batch.
- Start the Actor and review the result status.
- Export the community rows and rule columns.
{"inputList": ["https://x.com/i/communities/1493446837214187523"]}
Repeated valid links that resolve to the same ID are normally processed once per run.
Twitter (X) community data fields and complete output ๐ฆ
| Field group | Included data |
|---|---|
| Community | ID, URL, name, description and topic |
| Membership context | Member count and join policy |
| Appearance and dates | Banner, creation date and sensitive-content flag |
| Creator | ID, name, username, avatar and Blue verification flag |
| Rules | Rule IDs, names and descriptions |
Complete illustrative success item with fictional content, not a live result:
{"input": "https://x.com/i/communities/2088355206723477000","status": "success","id": "2088355206723477000","url": "https://x.com/i/communities/2088355206723477000","name": "Field Research Exchange","description": "A place to discuss field methods and share practical research notes.","member_count": 1280,"created_at": "2026-09-01T10:00:00Z","created_at_timestamp": 1788256800,"join_policy": "Open","is_nsfw": false,"topic": "Science","banner_url": "https://example.com/field-research-banner.jpg","creator.id": "100100100","creator.name": "Northstar Lab","creator.username": "northstar_lab","creator.avatar_url": "https://example.com/northstar_lab_normal.jpg","creator.is_blue_verified": false,"rules.id": ["1001", "1002"],"rules.name": ["Stay on topic", "Credit your sources"],"rules.description": ["Discuss field methods and research practice.", "Link to the original source when sharing published work."]}
Fields such as creator.username are literal column names in both the table and JSON. The rules.id, rules.name and rules.description lists align by position, so all rules stay attached to their community row.
Successful rows can contain empty strings, zero counts, false flags, empty lists or null optional branches when a value is unavailable. A failed row retains input, sets status to failed and leaves the entity data fields null.
Input requirements and coverage โ๏ธ
| Parameter | Type | Required | Default and rules |
|---|---|---|---|
inputList | array of strings | Yes | No default; at least one item. No fixed input-count maximum. |
Provide a full HTTP or HTTPS URL on x.com or twitter.com with the path /i/communities/COMMUNITY_ID. The community ID must be numeric. Bare IDs, search queries and ordinary profile or post links are not accepted.
The result covers public community details. It does not collect member profiles, community posts or a moderator directory. A member count does not imply that an individual member list is accessible.
Twitter (X) community data use cases ๐ฏ
Community directories
Keep names, descriptions, topics and source URLs for a selected group of communities.
Participation research
Review join policies and published rules before deciding whether a community fits your work.
Topic landscape reviews
Compare the public positioning and displayed membership of communities discussing related subjects.
Rule and profile monitoring
Save periodic snapshots of rule descriptions, banners and community descriptions.
Pricing and billable community rows ๐ฐ
Check the Actor's Pricing tab for the current charging model and rate. The Store configuration is authoritative.
Under dataset-item pricing, each saved success or failed row can count as a billable item. Automatic retries do not independently add result rows.
One processed community creates one result row. Its creator details and rules remain part of that row.
Twitter (X) community API and integrations ๐
Replace $ACTOR_ID with the ID shown in the Actor API tab and $APIFY_TOKEN with your Apify token.
curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"inputList":["https://x.com/i/communities/1493446837214187523"]}'
Start runs through REST, Apify client libraries or schedules. Use webhooks to handle completion, then export the dataset as JSON, CSV or Excel, or send it to Google Sheets, Make, Zapier and your reporting tools.
Reliability and limits โ ๏ธ
Temporary request failures and selected access errors are retried automatically. A deleted page or a response without usable community data produces a failed result.
X can omit the topic, creator details or rules from a public response. Missing counts default to zero, and unavailable text can be empty. The Actor collects the visible page data and does not verify membership totals or enforce the community's join policy.
Frequently asked questions โ
Does it export community members?
No. It returns the visible member count and community details, not individual member profiles.
Can it collect posts from the community?
No. This Actor reads the community profile and rules. Use Post Details Scraper for individual post URLs.
Does an open join policy guarantee access?
No. The field describes the public policy value. X may still restrict what a particular request can see.
Are rules returned as separate rows?
No. Rule names and descriptions remain aligned lists in the single community row.
Can I submit a community ID alone?
No. Submit the full X or Twitter community URL.
Support, responsible use, and related actors ๐
For a reproducible issue, contact support with the run ID, approximate time and a safe public input. Keep credentials and private data out of support messages.
Use public data in line with applicable privacy, copyright and platform requirements.