X Community Posts API

X Community Posts

Features

• Read posts from the community you specifyStart from a community link to collect public discussions in that community, rather than the collection of posts published on one person’s profile.
• Apply a separate cap to every communityWhen you supply several community links, results_limit applies to each one and posts are collected in creation-time order, so your input specifies the collection size for each discussion space.
• Keep the message and its supporting details togetherEach post record contains its text, author information, publication time, media and available interaction counts, making it possible to review the message without losing who published it or when.

Parameters

How to Use

The request starts a background collection task, so its first response gives you a task ID rather than the finished data; use that ID to check progress and retrieve the results.

1. Copy the links of the communities you want to read and choose a per-community limit such as 20 or 100; use a community link rather than an individual post URL.
2. Before running the example, replace $SOCQ_API_KEY with your own API key or set that environment variable. Send the JSON input to POST /v1/x/community-posts with the Authorization header shown below, then save the task_id from the response.
3. Use GET /v1/tasks/{task_id} with the saved ID to check progress. queued means waiting, running means collection is in progress, and retrying means another attempt is underway. Wait for succeeded before reading the results; if the task is failed, read error_message for the reason.
4. When the task succeeds, read data.results.items: each item in this list describes one community post. An empty list means the task completed without returning any records.
5. If data.results.has_more is true, the next_cursor value is the marker for another page of saved results. Copy it unchanged into the cursor parameter of GET /v1/tasks/{task_id}?cursor=... and continue until has_more is false.

curl -X POST "https://api.socq.ai/v1/x/community-posts" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://x.com/i/communities/1493446837214187523"],"results_limit":20}'

Best Use Cases

• Prepare source material for a discussion digest: Organize the retrieved post text, author handles, links and times into a reading list that someone or a separate summarization tool can use to write a digest of those posts.
• Compare a post’s interaction counts across saved snapshots: Store post IDs and the returned counters with collection times, then match the same posts in later collections to calculate changes in the available counts yourself.
• Investigate a selected post’s surrounding conversation: Choose a post from the community results and pass its post URL to X Thread Context to read the available earlier posts and replies around that particular message.

Pro Tips

• When planning a batch, multiply the number of community links by results_limit to estimate the requested record count, then use the per-post rate rather than assuming the limit is shared by all communities.
• When repeating a collection, match posts by their IDs before appending them to your saved table, because a post can appear again in a later task.
• When keeping results from several communities, save the submitted community links with the task input; the standard post record does not guarantee a community ID that can replace that input context.

Related APIs