X Community Details API for Members & Rules

{
  "community": {
    "id": "1500000000000000000",
    "name": "Tesla Fans",
    "description": "A community for Tesla enthusiasts",
    "banner_url": "https://xquik.com/example",
    "created_at": "2025-01-15T12:00:00Z"
  }
}

{
  "error": "invalid_input",
  "message": "Invalid input. Check the request body."
}

{
  "error": "unauthenticated",
  "message": "Authentication required. Provide a valid API key or bearer token."
}

{
  "error": "insufficient_credits",
  "message": "Insufficient credits. Top up or subscribe to continue."
}

{
  "error": "not_found",
  "message": "Resource not found."
}

{
  "error": "x_api_unavailable",
  "message": "X data source temporarily unavailable. Try again later."
}

{
  "error": "rate_limit_exceeded",
  "message": "Too many requests. Try again later.",
  "retryAfter": 60
}

{
  "error": "x_api_unavailable",
  "message": "X data source temporarily unavailable. Try again later."
}

GET

communities

{id}

info

X Community Details API for Members & Rules

curl --request GET \
  --url https://xquik.com/api/v1/x/communities/{id}/info

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://xquik.com/api/v1/x/communities/{id}/info"

	req, _ := http.NewRequest("GET", url, nil)

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

{
  "community": {}
}

Use the X communities API to resolve one community. Then read its members, moderators, rules, or tweets. Keep its numeric ID for later requests.

Validate an X Community Before Extraction

Check community details for every numeric community ID. Confirm the community name, description, creator, join policy, rules, and banner before requesting members or tweets. This prevents exports from using the wrong X community. Keep the returned community ID as a string. Store the creator and moderator details separately from the member count. Membership totals can change while the community identity remains stable. Use the rules and join policy to give analysts the correct context. They describe how the Twitter community operates. They do not replace member rows, moderator profiles, or community tweets. After validation, choose the smallest matching route. Fetch member profiles for audience review. Fetch moderators for governance review. Fetch recent tweets to review posts and engagement. Use saved extraction jobs to produce CSV, JSON, or XLSX output.

Choose the Right Twitter Community API

Start with community details when the numeric ID needs validation. Then choose the route that matches the records you need.

Community details

Get the name, description, creator, rules, policies, and banner. Keep member and moderator counts with the record.

Community members

Retrieve member profiles with usernames, bios, verification, follower counts, and cursor pagination.

Community tweets

Retrieve recent tweets, authors, replies, reposts, likes, quotes, media, and cursor pages.

Keyword search

Search one community for matching tweets. Keep the query and cursor with each page.

Moderator profiles

Retrieve the smaller moderator roster without treating every member as a moderator.

Saved exports

Run a community extraction to save CSV, JSON, or XLSX output.

Use member routes for profile rows. Use tweet routes for posts and engagement counts. Use extraction jobs to save CSV, JSON, or XLSX output.

Choose Community Metadata

Use this route for community metadata, rules, policies, and counts. It returns one community record, not member profiles or tweet rows. Use member and tweet routes for those collections.

1 credit per call · All plans from $0.00012/credit · Direct MPP: USD 0.00015 per call

curl https://xquik.com/api/v1/x/communities/1234567890/info \
  -H "x-api-key: xq_your_api_key_here" | jq

const communityId = "1234567890";
const response = await fetch(`https://xquik.com/api/v1/x/communities/${communityId}/info`, {
  headers: { "x-api-key": "xq_your_api_key_here" },
});
const data = await response.json();
const community = data.community;
const communityRecord = {
  community_id: community.id,
  community_name: community.name ?? null,
  description: community.description ?? null,
  member_count: community.member_count ?? null,
  moderator_count: community.moderator_count ?? null,
  join_policy: community.join_policy ?? null,
  invites_policy: community.invites_policy ?? null,
  is_nsfw: community.is_nsfw ?? null,
  creator_id: community.creator?.id ?? null,
  creator_username: community.creator?.username ?? null,
  banner_url: community.banner_url ?? null,
  created_at: community.created_at ?? null,
  primary_topic_name: community.primary_topic?.name ?? null,
  rule_count: community.rules?.length ?? 0,
};

process.stdout.write(JSON.stringify(communityRecord, null, 2));

import json
import requests

response = requests.get(
    "https://xquik.com/api/v1/x/communities/1234567890/info",
    headers={"x-api-key": "xq_your_api_key_here"},
)
data = response.json()
community = data["community"]
community_record = {
    "community_id": community["id"],
    "community_name": community.get("name"),
    "description": community.get("description"),
    "member_count": community.get("member_count"),
    "moderator_count": community.get("moderator_count"),
    "join_policy": community.get("join_policy"),
    "invites_policy": community.get("invites_policy"),
    "is_nsfw": community.get("is_nsfw"),
    "creator_id": (community.get("creator") or {}).get("id"),
    "creator_username": (community.get("creator") or {}).get("username"),
    "banner_url": community.get("banner_url"),
    "created_at": community.get("created_at"),
    "primary_topic_name": (community.get("primary_topic") or {}).get("name"),
    "rule_count": len(community.get("rules") or []),
}

print(json.dumps(community_record, indent=2))

Use GET /x/communities/{id}/info when a workflow needs one durable community profile row before member exports, moderator review, content routing, or CRM enrichment. Store community_id, community_name, description, member_count, moderator_count, policy fields, creator, banner_url, created_at, primary_topic_name, and rule_count.

Qualify a Community Before Collecting Profiles or Tweets

Read community metadata before starting a member or tweet export. This check prevents a copied community ID from sending results into the wrong project. Confirm community.id and community.name first. Save both values with the planned member or tweet export. Names can change, while the numeric ID anchors later member and tweet pages. Review description and primary_topic for research relevance. Keep this classification separate from tweet text. Community metadata describes the space, while tweet routes return individual posts. Check join_policy and invites_policy before planning member collection. Do not infer either policy from member counts. Store the returned values exactly, including missing values. Use member_count to estimate roster size. Use moderator_count only for staffing context. Neither count replaces the paginated member or moderator routes. Review is_nsfw before sharing banners, descriptions, or tweets. Follow the receiving system’s content rules. Keep API responses unchanged. Capture every community rule with its ID, name, and description. Preserve the returned order. Do not merge several rules into one undocumented summary. Finish the qualification record with these decisions:

Continue to member profiles, moderator profiles, tweets, or keyword search.
Stop because the community ID or subject is incorrect.
Require a reviewer before handling sensitive community content.
Refresh metadata later because a required field is unavailable.

This route qualifies the community. Collection routes return member profiles and community tweets.

Create a Community Qualification Manifest

Create one manifest before starting member, moderator, or tweet collection. Use the returned community ID as its stable key. Record these community facts:

Record the community name and description.
Record member and moderator counts.
Record join and invitation policies.
Record primary topic and content-sensitivity state.
Record the creator profile and banner URL when returned.
Record every rule ID, name, and description.

Add a retrieval timestamp in UTC. Expect community names, counts, rules, and policies to change. The timestamp explains which metadata guided later collection. Keep planned collection work in a separate manifest section. Name the exact routes for members, moderators, unfiltered tweets, or keyword matches. Include the intended page size, search query, and output format when applicable. Keep member profiles and tweets in their own exports. Link those exports by community ID and manifest ID. Stop when the returned community ID differs. Require a review when the name or topic conflicts with the project brief. Record the decision instead of silently selecting another community.

Use Community Metadata to Choose the Next Route

The member route returns paginated profile rows. See Community Members. The member count only estimates the expected roster size. Use Community Moderators for moderator profiles. The moderator count does not expose those usernames or user IDs. Use Community Tweets for the unfiltered community timeline. Preserve community ID and cursor with every page. Use Community Search for matching tweets. Preserve the exact keyword expression and sort mode with every result. Keep the creator object for ownership context. Require route evidence before exporting that profile as a member or moderator.

Detect Community Metadata Drift

Compare manifests by stable community ID. Never join them by community name. Report name, description, topic, policy, rule, and sensitivity changes separately. A member-count change does not prove a policy change. Track community rules and tweets independently. Store both retrieval times and both returned values. Preserve absent fields. Never invent policy or count defaults. Refresh this endpoint before long-running exports. Attach the newest manifest ID to every new collection job. Keep earlier manifests immutable for audits.

Path parameters

string

required

Community ID (numeric string).

Headers

string

Full account key. Sessions and OAuth also work.

string

Bearer xq_your_guest_key_here authenticates paid_reads guest keys. Direct MPP uses the Payment ... credential. Get it from the WWW-Authenticate: Payment challenge.

Response

200 OK

object

Community details. Community object fields:

string

Community ID.

string

Community name. Omitted if unavailable.

string

Community description. Omitted if empty.

number

Total member count. Omitted if unavailable.

number

Total moderators. Omitted if unavailable.

string

Join policy (e.g. Open). Omitted if unavailable.

string

Invitation policy. Omitted if unavailable.

boolean

Whether the community is marked sensitive. Omitted if unavailable.

object

Creator profile with id, username, verified, and optional name. Omitted if unavailable.

string

Banner image URL. Omitted if unavailable.

string

ISO 8601 creation timestamp. Omitted if unavailable.

object

Primary topic with id and name fields. Omitted if unavailable.

object[]

Community rules, each with id, name, and description. Omitted if unavailable.

{
  "community": {
    "id": "1234567890",
    "name": "Web Developers",
    "description": "A community for web developers",
    "member_count": 15000,
    "moderator_count": 5,
    "join_policy": "Open",
    "created_at": "2024-01-15T00:00:00.000Z",
    "primary_topic": { "id": "1", "name": "Technology" },
    "rules": [
      { "id": "1", "name": "Be respectful", "description": "Treat all members with respect." }
    ]
  }
}

400 Invalid community ID

{ "error": "invalid_community_id" }

The community ID is empty or invalid.

401 Unauthenticated

{ "error": "unauthenticated" }

Missing or invalid API key.

402 Payment required

Account keys get account options; guest keys get guest top-up only. Anonymous calls get a direct MPP WWW-Authenticate: Payment challenge. They also get a guest wallet creation action. No checkout starts automatically. Confirm any payment action.

404 Community not found

{ "error": "not_found" }

The community could not be resolved. Check the community ID.

502 X API unavailable

{ "error": "x_api_unavailable" }

The read service returned an error. Retry after a short delay.

429 Rate Limit Exceeded

{ "error": "rate_limit_exceeded", "retryAfter": 60 }

Your tier rate limit was exceeded. Wait for the Retry-After header before retrying.

424 Dependency Failed

{ "error": "x_api_unavailable" }

Opted-in normalized v1 calls return 424 when the read service fails.

Next steps: Community Members to list members, or Community Tweets to browse posts.

{
  "community": {
    "id": "1500000000000000000",
    "name": "Tesla Fans",
    "description": "A community for Tesla enthusiasts",
    "banner_url": "https://xquik.com/example",
    "created_at": "2025-01-15T12:00:00Z"
  }
}

{
  "error": "invalid_input",
  "message": "Invalid input. Check the request body."
}

{
  "error": "unauthenticated",
  "message": "Authentication required. Provide a valid API key or bearer token."
}

{
  "error": "insufficient_credits",
  "message": "Insufficient credits. Top up or subscribe to continue."
}

{
  "error": "not_found",
  "message": "Resource not found."
}

{
  "error": "x_api_unavailable",
  "message": "X data source temporarily unavailable. Try again later."
}

{
  "error": "rate_limit_exceeded",
  "message": "Too many requests. Try again later.",
  "retryAfter": 60
}

{
  "error": "x_api_unavailable",
  "message": "X data source temporarily unavailable. Try again later."
}

X Community Details API for Members & Rules

curl --request GET \
  --url https://xquik.com/api/v1/x/communities/{id}/info

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://xquik.com/api/v1/x/communities/{id}/info"

	req, _ := http.NewRequest("GET", url, nil)

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

{
  "community": {}
}

​Validate an X Community Before Extraction

​Choose the Right Twitter Community API

Community details

Community members

Community tweets

Keyword search

Moderator profiles

Saved exports

​Choose Community Metadata

​Qualify a Community Before Collecting Profiles or Tweets

​Create a Community Qualification Manifest

​Use Community Metadata to Choose the Next Route

​Detect Community Metadata Drift

​Path parameters

​Headers

​Response

​200 OK

​400 Invalid community ID

​401 Unauthenticated

​402 Payment required

​404 Community not found

​502 X API unavailable

​429 Rate Limit Exceeded

​424 Dependency Failed

Validate an X Community Before Extraction

Choose the Right Twitter Community API

Choose Community Metadata

Qualify a Community Before Collecting Profiles or Tweets

Create a Community Qualification Manifest

Use Community Metadata to Choose the Next Route

Detect Community Metadata Drift

Path parameters

Headers

Response

200 OK

400 Invalid community ID

401 Unauthenticated

402 Payment required

404 Community not found

502 X API unavailable

429 Rate Limit Exceeded

424 Dependency Failed