𝕏(twitter) Community Profile

Affiliate disclosure: TrueFetch may earn a commission when you open an Apify account through links on this page, at no extra cost to you.

X Community Profile retrieves a structured public profile for each available X Community URL or numeric ID you submit. Use one identifier for a controlled trial or process a list of up to 1,000 entries for audience discovery, qualification, monitoring, and enrichment.

• Simple required input: provide one list containing X Community URLs, numeric IDs, or both.
• Documented profile shape: receive sixteen top-level identity, membership, creator, access, topic, imagery, rule, and processing fields.
• Repeatable delivery: save successful profiles to an Apify Dataset for JSON, CSV, API, or integration use.
• Live evidence: the shared example has been verified against a successful cloud run and complete Dataset item.

Test one Community on Apify or review the API page. Community profiles and membership totals can change, while invalid or unavailable identifiers may return no row, so validate your own sample before increasing scope.

What does X Community Profile do?

The Actor resolves X Community URLs or numeric identifiers and returns the current profile information available for each successful lookup. The record covers the Community's numeric ID, name, description, creator attribution, join policy, creation time, banner, reported membership, sensitive-content flag, primary topic, trending hashtags when present, featured member avatars, and published Community rules. Three processing fields make the retrieval result and timestamp explicit.

This is a profile product, not a post or membership export. It does not return a Community timeline, individual posts, a full member directory, a moderator directory, engagement analytics, pinned content, or theme settings. The narrow contract prevents unrelated claims from being confused with the actual sixteen-field Dataset schema.

X describes Communities as dedicated spaces created and managed by people. Admins and moderators maintain settings, membership, and rules, while public visibility and participation depend on current platform behavior. X Community Profile captures the profile snapshot needed to shortlist or compare Communities before a person performs deeper review on X.

How do I run X Community Profile?

Open the Actor, enter at least one Community URL or ID in the community list, and start the run. This example uses the same Community checked during the latest regression:

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

After completion, open the default Dataset. A successful item should echo the resolved numeric ID, contain status equal to success, point processor to this Actor, and include a new ISO timestamp in processed_at. The current member count, names, topics, hashtags, avatars, and rules may differ from an older documentation sample because these fields describe a changing public profile.

The numeric form 1992144505747931156 is also accepted. For URLs, use a direct X Community path containing /communities/{id}. Begin with one known identifier, inspect the complete row and charge record, and only then expand to a representative batch.

What data does X Community Profile return?

Each successful lookup produces one item with sixteen top-level fields. status, processor, and processed_at provide run context. id, display_name, and description identify the Community. creator contains user_name, blue_verified, and verified. join_policy, created_at, banner_url, member_count, and is_nsfw describe access, timing, imagery, scale, and sensitive-content status. community_topic and community_tags capture current topical signals. members_facepile contains featured avatar URLs, and community_rules contains rule names and descriptions.

The following shortened item preserves all top-level fields while limiting repeated array content:

{
  "status": "success",
  "processor": "https://apify.com/truefetch/x-community-profile?fpr=aiagentapi",
  "processed_at": "2026-07-23T15:30:00+00:00",
  "id": "1992144505747931156",
  "display_name": "Life AI Community",
  "description": "A community united to awaken human-powered health intelligence where every contribution helps transform sickcare into true care for life.",
  "creator": {
    "user_name": "LifeNetwork_AI",
    "blue_verified": false,
    "verified": false
  },
  "join_policy": "Open",
  "created_at": "2025-11-22T08:13:57+00:00",
  "banner_url": "https://pbs.twimg.com/community_banner_img/1992182162611970048/GB9wTW9Y?format=jpg&name=orig",
  "member_count": 26668,
  "is_nsfw": false,
  "community_topic": "Artificial Intelligence",
  "community_tags": [],
  "members_facepile": [
    "https://pbs.twimg.com/profile_images/example/avatar.jpg"
  ],
  "community_rules": [
    {"name": "Be kind and respectful.", "description": ""}
  ]
}

Empty arrays are valid. A missing trending hashtag list does not imply that a topic has no activity. Featured avatars are only the small selection returned with the Community profile, not a complete member list. Treat the member count as a value observed at processed_at, not historical analytics.

What inputs can I configure?

The schema has one required property:

Input	Type	Limits	Accepted values
community	array of strings	1–1,000 items	Direct X Community URLs or numeric Community IDs

The Actor validates that the field is a non-empty list no larger than 1,000. Every entry must be a string. URL inputs are resolved from the path segment after /communities/; query strings and fragments are removed. Numeric inputs must contain digits only and fit the supported ID range. Invalid strings are filtered, and the run stops if no valid ID remains.

Input validity does not guarantee availability. A deleted, restricted, renamed, temporarily unavailable, or incomplete Community response may not create a row. Preserve the submitted list in your task or application when you need to reconcile requested IDs against Dataset output.

What platforms and markets does X Community Profile cover?

Coverage is specific to X Communities addressable by a numeric Community ID. The input accepts current x.com Community URLs, legacy twitter.com URLs with the same path structure, and bare IDs. There is no country, language, date, post-type, or keyword filter because this Actor retrieves Community profiles rather than searches for Communities.

The returned description, name, topic, rules, and creator text remain in the form exposed for that Community. The Actor does not translate fields or infer a market. Availability can vary with X visibility, platform changes, upstream responses, and the status of the Community. X's official help notes that direct Community URLs can expose public Community context, while participation and joining depend on current account and membership rules.

Why use X Community Profile?

Manual profile review is practical for a few Communities, but a structured Dataset improves consistency when a team needs to compare many profiles or repeat the same review later. Numeric IDs and retrieval timestamps provide durable reference points even when names or descriptions change. Named fields also reduce transcription errors and make filtering easier.

The output supports screening questions such as: Which Communities focus on a topic? Which have open or restricted joining? Which creators are associated with them? How do current membership totals compare? What rules and sensitive-content signals need human review? The Actor supplies evidence for those questions without claiming to measure engagement, sentiment, influence, conversion, or future growth.

Results can be scheduled and joined to other data sources. A repeated snapshot may show directional profile changes, but comparisons should use consistent intervals and preserve original timestamps. A change in membership is an observed difference, not proof of causation.

Who is X Community Profile for?

Audience researchers can assemble Community shortlists by topic, description, and scale. Partnership teams can add creator and join-policy context before deciding whether contact is relevant and appropriate. Social strategists can monitor public profile changes across a defined set. Trust and safety reviewers can use descriptions, rules, topics, and is_nsfw as preliminary signals that still require content review.

Developers and data teams can consume the stable JSON shape through Apify storage and APIs. Journalists and academic researchers can retain the Community ID and retrieval time as part of a reproducible research note. The Actor is not suitable for identifying private attributes, building a full membership graph, automating unsolicited outreach, or replacing platform-native moderation tools.

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

Apify supports REST calls, client libraries, Tasks, schedules, webhooks, and integrations. Keep the API token in a secret or environment variable and send the same input object used in Console:

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

Wait for a terminal SUCCEEDED status, then read the default Dataset ID from the run and paginate items as needed. A robust consumer handles zero-row success, failed runs, timeouts, and a Dataset count smaller than the input list.

After connecting the Apify MCP server, an MCP-compatible client can discover the Actor's schema and submit:

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

MCP availability depends on Actor visibility, account plan, token permissions, and client configuration. If tool execution is refused, confirm access in Apify Console and use the authenticated REST API or CLI. Do not expose tokens or private Dataset content in prompts, logs, or support messages.

How much does X Community Profile cost?

The Actor uses pay-per-event pricing. Check the live pricing panel because plan tiers and rates can change.

Event	Free-tier rate or illustration
Actor usage	$0.00001 per usage event; count varies
Actor start	$0.01000
Successful profile result	$0.00300 each

For a smallest illustrative success with one result and 200 usage events, the calculation is (200 × $0.00001) + $0.01000 + $0.00300 = $0.01500. Actual resource use can differ, and paid plan tiers may reduce the per-result price. Submitted items do not determine the final charge by themselves: start and usage events may occur even when no result is written.

Use a one-result test, review charge details, and set a maximum total charge where supported. Do not describe $3 per 1,000 as the entire run cost because starts and variable usage are separate.

How does X Community Profile compare with alternatives?

Opening X manually gives the richest immediate context and is best for qualitative review of a small number of Communities. X Community Profile is better when you need a consistent record shape, batch input, timestamps, Dataset storage, scheduling, or API access. It complements rather than replaces manual review.

General social listening tools may search posts, estimate engagement, or aggregate mentions, but they often do not preserve this exact Community profile schema. Full browser automation can be customized for other views but adds maintenance and validation work. This Actor offers a narrower contract with documented inputs, output fields, and per-event pricing.

Choose according to the decision: use X for current visual context and participation, this Actor for structured profile collection, and a separately validated post or listening product when the research question concerns conversations rather than Community identity.

What are the limits and troubleshooting steps?

If input validation fails, confirm community is an array containing 1–1,000 strings. Use direct Community URLs or digit-only IDs. Remove profile URLs, post URLs, text labels, and unsupported values. At least one valid ID must remain.

If a run succeeds with fewer rows than expected, compare the Dataset IDs with the submitted list. Some Communities may be unavailable or may not return a complete profile. Retry a single known example to separate an identifier-specific issue from a broader platform issue. Review terminal status and logs before retrying a large batch.

If API or MCP calls fail, check the token, Actor access, JSON encoding, memory, timeout, plan, and refreshed tool schema. Upstream availability can change without a code change. Do not use repeated aggressive retries.

Data is a point-in-time public snapshot. Values can be empty, changed, or unavailable, and the Actor cannot guarantee coverage, uptime, completeness, commercial suitability, or a particular outcome.

Frequently asked questions

Does it download Community posts? No. The Dataset contains profile fields only.

Can I obtain all members or moderators? No. members_facepile is a featured-avatar sample, not a directory.

Can one run combine URLs and IDs? Yes, if every entry is a string and the list stays within 1–1,000 items.

Why is community_tags empty? The Community response may not contain trending hashtags at retrieval time. Empty is a valid value.

Can I track growth? Store repeated snapshots and compare member_count with timestamps. The Actor does not calculate growth or explain changes.

Does an open join policy mean outreach is permitted? No. Join settings do not create consent or override law, X rules, or anti-spam obligations.

Related TrueFetch Actors

• X User Profile for public profile and account context around a relevant creator.
• Reddit Community Profile for comparing community identity and scale across another platform.
• Telegram Profile for structured public Telegram entity context.

Support and last updated

Use the Actor's Issues tab in Apify Console or contact TrueFetch support. Include a sanitized input, run ID, expected result, actual result, and a short log excerpt. Never publish an Apify token or sensitive Dataset content.

For platform behavior, consult X's official Communities help and moderator playbook. X Community Profile is an independent Actor and is not endorsed by X Corp. Use results lawfully, avoid harassment or discriminatory profiling, and verify high-impact decisions with current first-party evidence.

Last updated: July 23, 2026. The live schema, price panel, run details, Dataset, and X documentation are authoritative if this page becomes outdated.