Social Fetch
Get API key
X (Twitter) hub

X (Twitter) Community Tweets API

Pull the public post feed for an X community from its /i/communities/… URL — same JSON envelope as the rest of the Twitter tag.

GET /v1/twitter/communities/tweets

1 credit per successful request.

Try in playgroundFull API docs

About this endpoint

X Communities sit between a hashtag and a group chat: topic rooms with their own feed, member set, and permalink under `x.com/i/communities/{id}`. Brand and research jobs often care about what gets posted inside a room (product launches, sports leagues, crypto niches), not the room's about card alone. Scraping that feed means cookies, GraphQL shapes that change without notice, and empty responses that look like "no posts" when the client actually failed.

`GET /v1/twitter/communities/tweets` takes a required `url` query param (the community permalink) and returns public posts in the shared Social Fetch envelope. Branch on `data.lookupStatus` before you write. On `found`, read `data.tweets` — each row carries text, metrics, media, entities, and an author card when X exposes them. `found` can still return an empty `tweets` array when the community resolves but this response has no posts. On `not_found`, do not invent rows. Bill from `meta.creditsCharged`.

This route lists posts for a community you already have a URL for. Community metadata (name, description, member counts) is `GET /v1/twitter/communities`. Single-status enrichment is `GET /v1/twitter/tweets`. Keyword discovery across X is `GET /v1/twitter/search`. All use one Social Fetch API key — no X developer app for these public lookups.

X (Twitter) Community Tweets API FAQ

What does the X / Twitter Community Tweets API return?

A lookupStatus of found or not_found, plus data.tweets: an array of public posts for that community (text, metrics, media, entities, author when present). found may still include an empty tweets array. Each response uses the shared Social Fetch envelope with meta.requestId and meta.creditsCharged.

How do I list tweets from an X community?

Send GET /v1/twitter/communities/tweets with x-api-key and a required url parameter set to the community permalink (for example https://x.com/i/communities/1493446837214187523). Read data.lookupStatus, then data.tweets. Full parameters and examples are in the API docs.

How much does listing Twitter community tweets cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

Is this the same as GET /v1/twitter/communities?

No. GET /v1/twitter/communities returns community metadata for a URL. GET /v1/twitter/communities/tweets returns the post list for that community. Use the Twitter hub docs if your job needs both.

What if the community URL is private, deleted, or wrong?

Branch on data.lookupStatus. not_found means Social Fetch could not return a public tweet list for that url. Keep an empty store write and retain meta.requestId if you need support on a failed call.

Community tweets vs keyword search vs a single tweet lookup?

Use this route when you already have a community permalink and want posts inside that room. Use GET /v1/twitter/search for free-text discovery across X. Use GET /v1/twitter/tweets when you already have a status URL or id. They are separate marketplace operations.

Do I need an X developer app or Bearer token?

No. You authenticate to Social Fetch with an API key. The route reads public community posts; it does not act on behalf of a logged-in X user or require elevated X API access.

Other X (Twitter) endpoints