Basic Auth has been deprecated.
August 31, 2010
Basic Auth has been deprecated. All applications must now use OAuth. Read more »
x
Don't fret! @twitterapi is here to help! Feel free to reach out to us directly, or via our Twitter Development Talk group.
The switch to OAuth is a good thing! You, as the application developer,
- don't have the burden of keeping potentially damaging credentials for your users (especially considering that a lot of people use the same password for multiple services);
- don't have to worry about the user changing their password — a user can change his or her password and the OAuth "connection" to your app will still work;
- don't have to worry about other applications masquerading as your application as only your application can set the byline with your application name;
- will eventually have access to more trusted APIs from Twitter that will only be available to "trusted" OAuth-enabled applications; and
- will be contributing to the web of trust between users, service providers, and applications.
Choose your authorization path.
List the lists the specified user has been added to.
URL
http://api.twitter.com/version/:user/lists/memberships.format
Supported request methods
GET
Parameters
Optional
-
cursor
Breaks the results into pages. A single page contains 20 lists. Provide a value of -1 to begin paging. Provide values as returned in the response body's next_cursor and previous_cursor attributes to page back and forth in the list.
- http://api.twitter.com/1/twitterapidocs/lists/memberships.xml?cursor=12893764510938