Social platforms

Get X Community by ID · Twitter / X API

GET/x/communities/{id}
$min $0.001

Return a single X Community by its ID, including name, description, member count, and other public metadata. Useful for resolving a Community's profile before pulling its Posts or members.

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/x/communities/{id} \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

idpathrequired
X resource id.
community.fieldsquery
Overview

This operation is part of the Twitter / X API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs Twitter / X public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Look up public Twitter / X data for agents that need reliable open-web context.
  • Give an AI agent a stable Twitter / X data source without building a per-platform integration.
  • Normalize Twitter / X responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
  • The `billing.records_charged` field reports the charged billable-record quantity for the successful response.
  • A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 1 credit ($0.001) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields in the data object

A successful Get X Community by ID call returns one data object with these fields.

idstring
namestring
descriptionstring
created_atstring
member_countnumber
accessstring
join_policystring
Related endpoints

More Twitter / X operations

Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.