Now that lists have up to 5,000 members, can we have a lists/members/ids method?


#1

A long standing challenge with Twitter lists has been pulling a complete list of members for a list (especially if you’re only interested in the user IDs). This can be achieved at the moment using a cursor and pagination, but for bigger lists this can take a large number of API calls and burn through a sizable chunk of rate limit allocation.

Now that lists can have up to 5,000 members, this is an even bigger problem.

The friends/ids and followers/ids methods solve this for large friend/follower graphs, by serving back just the user IDs. Now that lists are so much larger, can we have a lists/members/ids method that solves the same case for lists?