WEIR

Twitter List API in 2026: Endpoints, Limits and Cost

Lookup, members, posts and owned Lists: every Twitter List API read with page sizes, rate limits and October 2026 prices, plus a real NASA List call.


Published · Updated · 6 min read

Cover image: One List lookup, real output

The Twitter List API is the group of X API v2 endpoints that read a List's details, members and posts from its numeric id.

This guide is for developers who need X (Twitter) Lists in code. You get each read endpoint with its limits and price as of October 2026, then the same reads on Weir with real output. We run Weir.

Look up any public List with one call:

curl -s https://api.weirapp.io/v1/x/lists/4143408 \
  -H "Authorization: Bearer $WEIR_API_KEY"
  1. Find the List idThe digits after /i/lists/ in its URL.
  2. Look up the ListName, owner and member count.
  3. Page the membersUp to 100 accounts a call.
  4. Read the postsThe List's timeline, or a search with listId.

Which Twitter List API endpoints does X offer?

X's v2 API reads Lists through four core endpoints, per its docs on 22 October 2026:

Endpoint Returns Per page Requests per 15 min
GET /2/lists/:id One List 1 75
GET /2/lists/:id/members Member accounts 1-100 900
GET /2/lists/:id/tweets The List's posts 1-100 900
GET /2/users/:id/owned_lists Lists a user owns 1-100 15

max_results sets the page size, and it defaults to 100. Each page hands you a pagination_token for the next.

A lookup returns only id and name unless you ask for more with list.fields. The extras are description, owner_id, private, follower_count, member_count and created_at.

An app-only bearer token reads public Lists. A private List needs its owner's sign-in, and X's docs list 403 as the error otherwise.

Other reads cover the Lists a user belongs to, follows or pins, and the accounts that follow a List.

What does the X List API cost?

X prices reads per resource returned. Its pricing page lists these rates as of October 2026:

$0.005per List read
$0.005per post read
$0.010per user read
$0.001per owned read, such as your own Lists

The page doesn't name the members or List posts endpoints. Members come back as user objects and posts as posts, so we priced them at those rates.

X usually charges a resource once per UTC day, and pay-per-use stops at 3 million post reads a month. Here is one realistic job, priced both ways:

One 500-member List and 1,000 of its posts, October 2026
X API, pay-per-useabout $10.01
Weir, $5 packabout $0.30
Weir, $1,000 packabout $0.15

On Weir that job is about 1,520 credits:

  • The lookup: 3 credits.
  • The members: 500 credits, plus 6 calls, counting the empty one that usually ends a walk.
  • The posts: 1,000 credits, plus about 11 calls at X's page size.

It also fits inside Weir's 5,000 free monthly credits. Price your own job with the X API cost calculator.

Get a List's details with Weir

Weir's three List endpoints take a plain API key and return X's data in camelCase. We looked up @NASA's public List "NASA Centers" on 22 October 2026, through Weir's MCP server. Trimmed:

{
  "id": "4143408",
  "name": "NASA Centers",
  "description": "NASA has 10 centers http://www.nasa.gov/about/sites",
  "url": "https://x.com/i/lists/4143408",
  "createdAt": "2009-12-02T22:41:02.000Z",
  "memberCount": 11,
  "subscriberCount": 861,
  "owner": { "username": "NASA", "verified": true, "followersCount": 92311171 }
}

It cost 3 credits: 2 for the List and 1 for the call. A private or missing List returns 404, which costs nothing.

subscriberCount is X's follower count for the List. memberCount tells you the members bill before you start.

Get Twitter list members by API

GET /v1/x/lists/{id}/members returns up to 100 accounts per call, in X's order. We asked for one:

{
  "data": [
    {
      "username": "VisitNASA",
      "name": "NASA Visitor Centers",
      "followersCount": 3325,
      "statusesCount": 10,
      "protected": false,
      "createdAt": "2012-02-10T21:30:05.000Z"
    }
  ],
  "meta": { "nextCursor": "v2.Zp8cNHnH…" }
}

That cost 2 credits. A member costs 1 credit, so ask for 100 per call and the call credit spreads over more results.

Each member has 16 fields, such as description, location and pinnedPostIds. Our guide to exporting List members writes them all to a CSV.

Get tweets from a List by API

On X, GET /2/lists/:id/tweets lets you set max_results from 1 to 100. Weir's GET /v1/x/lists/{id}/posts takes only a cursor: X picks the page size, up to about 100 posts.

data[]  id, text, url, lang, createdAt, conversationId, inReplyToId,
        author, likeCount, retweetCount, replyCount, viewCount,
        quoteCount, bookmarkCount, media, entities, article,
        quotedPost, retweetedPost
meta    nextCursor (null after the last page)

This function reads a List's timeline and stops at a page cap:

export async function listPosts(id, maxPages = 3) {
  const posts = [];
  const url = new URL(`https://api.weirapp.io/v1/x/lists/${id}/posts`);
  const headers = { Authorization: `Bearer ${process.env.WEIR_API_KEY}` };
  for (let page = 0; page < maxPages; page++) {
    const r = await fetch(url, { headers });
    if (!r.ok) throw new Error(`Weir answered ${r.status}`); // 402: out of credits
    const { data, meta } = await r.json();
    posts.push(...data);
    if (!meta.nextCursor) break; // null is the only stop
    url.searchParams.set("cursor", meta.nextCursor);
  }
  return posts;
}

We ran it against a local stand-in for the API. It stopped on a null cursor, stopped at three pages on an endless one, and threw on a 402.

For a smaller bill, search the List instead. POST /v1/x/search takes listId with a limit, filters like minLikes, and sinceId for new posts only. Our Python tweets tutorial shows the paging.

When not to use Weir

  • You need someone's owned Lists. Weir has no endpoint for them; X's owned_lists does it.
  • Member exports on a tight budget. TwitterAPI.io lists $0.0015 per List call of 20 members, as of October 2026. That's less per member than any Weir pack.
  • You manage Lists. Creating Lists or adding members takes X's own API, because Weir is read-only.
  • The List is private. Weir reads public Lists only, and it isn't licensed by X, so access can change.

FAQ

Is the Twitter List API free?

No. X bills its List reads from prepaid credits, at $0.005 per List as of October 2026. Weir gives you 5,000 free credits a month, which covers about 4,950 List members.

How do I get tweets from a Twitter List with the API?

Call X's GET /2/lists/:id/tweets with max_results up to 100, or Weir's GET /v1/x/lists/{id}/posts. Follow the token or cursor each page returns. On Weir, a search with listId lets you pick a smaller page.

Can the X API read private Lists?

Yes, if you sign in as the List's owner. An app-only token gets a 403 from X. Weir can't read them at all: it answers 404 for a private List.

How do I find a Twitter List ID?

Open the List on x.com and copy the digits after /i/lists/ in the address bar. NASA Centers, for example, lives at x.com/i/lists/4143408.

What's the difference between List members and followers?

Members are the accounts inside the List. Followers subscribe to read its timeline. X's API reads both, and Weir returns the members plus a subscriberCount.

Sources

All checked on 22 October 2026. X's pages were read as Markdown from docs.x.com.