Social platforms

Search members in an X Community · Twitter / X API

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

Search within an X Community's membership by query string and return matching members as a cursor-paginated list of profiles. Useful for finding specific people inside a large Community.

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

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

Parameters

idpathrequired
X resource id.
expansionsquery
tweet.fieldsquery
user.fieldsquery
media.fieldsquery
place.fieldsquery
poll.fieldsquery
pagination_tokenquery
next_tokenquery
max_resultsquery
Integer from 1 to 100.
queryqueryrequired
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

  • Search Twitter / X for public mentions, creators, posts, or topics matching a user query.
  • Feed ranked Twitter / X results into research, monitoring, and enrichment workflows.
  • 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

  • List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
  • The `billing.records_charged` field reports the charged billable-record quantity for the successful response.
  • If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

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 on each record in data

A successful Search members in an X Community call returns data as an array; each record carries these fields (12 of 14 shown — the docs list the full schema).

idstring
namestring
usernamestring
created_atstring
descriptionstring
locationstring
urlstring
profile_image_urlstring
profile_banner_urlstring
protectedboolean
verifiedboolean
verified_typestring
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.