Skip to main content
GET
/
x
/
communities
/
tweets
Search community tweets (query)
curl --request GET \
  --url https://xquik.com/api/v1/x/communities/tweets \
  --header 'x-api-key: <api-key>'

Documentation Index

Fetch the complete documentation index at: https://docs.xquik.com/llms.txt

Use this file to discover all available pages before exploring further.

Requested result counts are upper bounds for paid authenticated calls. When remaining credits cannot cover the full page or ID list, Xquik returns fewer results. If zero paid results are affordable, it returns 402 insufficient_credits.
1 credit per tweet returned · All plans from $0.00012/credit
curl -G https://xquik.com/api/v1/x/communities/tweets \
  --data-urlencode "q=machine learning" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq
The Node.js & Python snippets shape one durable row per matching community tweet instead of printing the full response page. Persist the final next_cursor row when has_next_page is true, then pass it back as cursor with the same q & queryType.

​
Direct community tweet search handoff

Use GET /x/communities/tweets when a monitoring job, research queue, moderation review, social listening workflow, or agent needs tweets across X communities by keyword. Store search_query, query_type, tweet_id, text, author_id, author_username, author_name, author_followers, author_verified, author_profile_picture, created_at, engagement counts, & media_urls for each row. Keep has_next_page & next_cursor with the export checkpoint so the next run can continue the same community search without duplicating earlier rows. Set queryType=Latest for recent queues or backfills. Set queryType=Top for relevance-ranked review.

Search row checkpoint

Store search_query, query_type, has_next_page, and next_cursor with the tweet rows so the next run resumes the same search.

Sort mode

Use Latest for recent collection and Top for relevance-ranked review. Keep the same queryType when you pass a cursor.

Default page

Direct calls use the default paid tweet page size. Treat the returned tweets.length as the row count returned for this page.

Saved export

Use community_search with searchQuery when the workflow needs a saved job with CSV/JSON/XLSX output.

​
Query parameters

​
q
string
required
Search query for community tweets.
​
queryType
string
Sort order. Top returns most relevant tweets, Latest returns most recent. Defaults to Latest.
​
cursor
string
Pagination cursor from a previous response. Omit for the first page.

​
Which community search route?

Cross-community search

Use GET /x/communities/tweets for keyword searches across communities.

Community search route

Use GET /x/communities/search when your integration already uses that route name. It accepts the same q, queryType, and cursor shape.

Known community posts

Use GET /x/communities/{id}/tweets for posts from one known community ID.

Bulk community jobs

Use Create extraction with community_search or community_post_extractor when the workflow needs a saved export.

​
Headers

​
x-api-key
string
required
Your API key. Session cookie authentication is also supported.

​
Response

​
tweets
object[]
Array of matching community tweets.
​
has_next_page
boolean
Whether more results are available.
​
next_cursor
string
Cursor for the next page. Pass as the cursor query parameter.
{
  "tweets": [
    {
      "id": "1893456789012345678",
      "text": "Interesting ML discussion in this community",
      "createdAt": "2026-02-24T10:00:00.000Z",
      "likeCount": 200,
      "retweetCount": 35,
      "replyCount": 15,
      "viewCount": 8500,
      "author": {
        "id": "987654321",
        "username": "mlresearcher",
        "name": "ML Researcher",
        "followers": 25000,
        "verified": true,
        "profilePicture": "https://pbs.twimg.com/profile_images/example.jpg"
      }
    }
  ],
  "has_next_page": true,
  "next_cursor": "DAACCgACGE..."
}
Next steps: Community Search for an alternative search endpoint, or Search Tweets for general tweet search.
Last modified on May 25, 2026