Note: For strategic context, cost math, and end-to-end monitoring workflows, see the X List API guide on the blog.
Community availability: The API Reference lists Community endpoints, but their current data availability needs confirmation. Before building a new Community workflow, contact support to confirm which operations and results are available. The request examples below document the interface; they are not a live availability test.
Lists
An X List is a public collection of up to 5,000 accounts. Lists have two audiences:- Members: accounts added to the list by the curator.
- Followers (subscribers): users who subscribed to read the List timeline.
The List ID is the numeric value in the list URL:
https://x.com/i/lists/1234567890 means the ID is 1234567890.
Tip: Every account starts with 100 free requests (no card, no expiry), enough to pull a mid-sized List end to end. Test any endpoint without writing code in the API Playground.
Get List Members
GET /v3/list-members
Get List Followers
GET /v3/list-followers
Note the parameter name:
/list-followers takes list_link (URL or ID), while /list-members and /list-tweets take list_id (numeric ID only).
Get List Tweets
GET /v3/list-tweets
Returns recent tweets from all list members in a single chronological feed. This is the endpoint used in the Real-Time Monitoring workflow for tracking groups of accounts with a single request instead of polling each account separately.
Communities
The following request formats describe the Community endpoints in the API Reference. Confirm availability as noted above before relying on them. Community membership can be an audience-discovery signal when member data is available. It does not by itself establish recent activity.
The Community ID is the numeric value in the community URL:
https://x.com/i/communities/1966045657589813686 means the ID is 1966045657589813686.
Private Communities were not API-accessible.
Get Community Members
POST /v3/community-members
Returns compact member profiles (id, username, display name, avatar, verified, and protected status).
Get Community Tweets
POST /v3/community-tweets
Search Community Tweets
POST /v3/community-search-tweets
/check-community-member endpoint instead.
Exporting to CSV
User and tweet feeds from the Lists endpoints above can be exported with a single helper. For users:/list-members and /list-followers return profiles in users; /list-tweets returns tweet objects in tweets, with the author under user. Optional profile fields can be empty. When exporting tweets, flatten nested values explicitly, for example {"username": tweet["user"]["username"]}; a CSV writer does not resolve a dotted field name such as user.username.
Related
- X List API guide: strategy, cost math, use cases
- Real-Time Monitoring: polling patterns for
/list-tweets - Target Audience Discovery: using lists for audience research
- Marketing Campaign Verification: membership checks
- Optimizing API Usage: request batching and rate-limit handling