One X community

A community's record: its name, description, membership count and rules, as X publishes them.

This is a live read: it goes to the platform at request time, returns cache_age_s = 0, and is metered against a separate live-per-minute bucket on top of your tier. It needs the scrape:live scope (Live scrape): Read from the platform itself rather than from the catalog: a profile or channel on any of the seven platforms, and on X the whole content layer - timelines, posts, replies, quotes, threads, followers, search, lists and communities.

curl "https://crmsolid.com/data-api/v2/x/communities/1493446837214187523" \
  -H "Authorization: Bearer psk_live_..."

const res = await fetch("https://crmsolid.com/data-api/v2/x/communities/1493446837214187523", {
  headers: {
    Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
  },
});

if (!res.ok) {
  const { error } = await res.json();
  throw new Error(`${error.code}: ${error.message} (${error.request_id})`);
}

const { data, meta } = await res.json();

import os

import requests

res = requests.get(
    "https://crmsolid.com/data-api/v2/x/communities/1493446837214187523",
    headers={"Authorization": f"Bearer {os.environ['CRM_SOLID_DATA_API_KEY']}"},
    timeout=30,
)
res.raise_for_status()

payload = res.json()
data, meta = payload["data"], payload["meta"]

Keys look like psk_live_... for production keys, psk_test_... for test keys and are minted in the panel.

Community id

1493446837214187523

Community name

Build in Public

Community member count

218,402

Community is nsfw

no

{
  "data": {
    "community_id": "1493446837214187523",
    "community": {
      "name": "Build in Public",
      "member_count": 218402,
      "is_nsfw": false
    }
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42,
    "cache_age_s": 0
  }
}

• 401Unauthorizedunauthorized | invalid_key

  No key was presented, or the key is unknown, revoked or expired.

• 402PaymentRequiredpayment_required | subscription_inactive

  The key is valid but the plan behind it cannot serve the call: the included requests are spent and overage is switched off, capped or unfunded (payment_required), or the billing period lapsed and was not renewed (subscription_inactive). Retrying does not help; paying does. The X-Plan-* headers on this response say how far past the line you are.

  Carries X-Plan, X-Plan-Limit, X-Plan-Overage, X-Plan-Period-End, X-Plan-Remaining.

• 403Forbiddenforbidden_scope | forbidden_ip

  The key is valid but not allowed to make this call: it lacks the scope, or the request came from an address outside the key's allowlist.

• 404NotFoundnot_found

  The addressed resource does not exist.

• 422InvalidRequestinvalid_request

  A parameter is malformed, out of range or mutually exclusive with another. `details` names the offending fields.

• 429RateLimitedrate_limited | quota_exceeded

  Either the burst ceiling for the current minute or the daily quota is spent. Distinguish with the code: rate_limited clears within the minute, quota_exceeded does not clear until 00:00 UTC.

  Carries Retry-After, X-Quota-Limit, X-Quota-Remaining, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-Request-Id.

• 500InternalErrorinternal_error

  Something failed on our side. Internals are never leaked; quote the request id.

• 503Unavailableupstream_timeout | upstream_error | not_configured

  The request could not be served right now. BRANCH ON error.code, not on the status: 'upstream_timeout' means a source was too slow (this is what a catalog query hitting its 15-second statement timeout returns, so it is reachable from any endpoint that reads the corpus, not only the live-scrape ones) and the same call is worth retrying with backoff - narrowing it with a smaller limit, a filtered scope or a less popular account makes it far less likely; 'upstream_error' means a source was unreachable, so back off further; 'not_configured' means the capability has no backing service in this deployment, and retrying will never help.

Every response carries X-Request-Id and meta.request_id. Quote it in support requests.

Live reads count against the live column as well as the ordinary one, so a burst of them runs out of the live bucket first. Every response reports where you stand in X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and the X-Plan headers.

• GET/x/users/{handle}One X profile, live
• GET/x/users/{handle}/aboutX's About this account panel
• GET/x/users/{handle}/tweetsAn account's timeline
• GET/x/users/{handle}/mediaAn account's media timeline
• GET/x/users/{handle}/mentionsPosts mentioning an account
• GET/x/users/{handle}/followersFollowers, newest first
• GET/x/users/{handle}/verified-followersVerified followers only
• GET/x/users/{handle}/followers/idsFollower ids in bulk
• GET/x/users/{handle}/followingWho an account follows
• GET/x/users/{handle}/relationshipDoes one account follow another
• GET/x/tweets/{id}One post
• GET/x/tweetsPosts by id, batched
• GET/x/tweets/{id}/repliesDirect replies to a post
• GET/x/tweets/{id}/threadThe whole conversation
• GET/x/tweets/{id}/quotesQuote posts of a post
• GET/x/tweets/{id}/retweetersWho reposted a post
• GET/x/search/tweetsAdvanced post search
• GET/x/search/usersPeople search
• GET/x/lists/{id}/tweetsA list's timeline
• GET/x/lists/{id}/membersWho is on a list
• GET/x/communities/{id}/membersA community's members
• GET/x/communities/{id}/moderatorsA community's moderators
• GET/x/communities/{id}/tweetsA community's posts
• GET/x/trendsWhat is trending, by location

Reference path: /data-api/reference/x-communities-get