This snapshot, taken on
27/09/2010
, shows web content acquired for preservation by The National Archives. External links, forms and search may not work in archived websites and contact details are likely to be out of date.
 
 
The UK Government Web Archive does not use cookies but some may be left in your browser from archived websites.

Basic Auth has been deprecated.

Attention! 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.

GET statuses/followers

Home › Documentation › User Resources › statuses/followers

Returns the authenticating user's followers, each with current status inline. They are ordered by the order in which they followed the user, 100 at a time. (Please note that the result set isn't guaranteed to be 100 every time as suspended users will be filtered out.)

Use the cursor parameter to access earlier followers.

URL

http://api.twitter.com/version/statuses/followers.format

Supported formats

json, xml

Supported request methods

GET

Requires Authentication

false About authentication »

unless requesting it from a protected user; if getting this data of a protected user, you must auth (and be allowed to see that user).

Rate Limited

true About rate limiting »

Parameters

Optional

  • user_id The ID of the user for whom to return results for. Helpful for disambiguating when a valid user ID is also a valid screen name.
    • http://api.twitter.com/1/statuses/followers.json?user_id=12345
  • screen_name The screen name of the user for whom to return results for. Helpful for disambiguating when a valid screen name is also a user ID.
    • http://api.twitter.com/1/statuses/followers.json?screen_name=noradio
  • cursor Breaks the results into pages. This is recommended for users who are following many users. 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/statuses/followers.json?cursor=12893764510938
  • include_entities When set to either true, t or 1, each tweet will include a node called "entities,". This node offers a variety of metadata about the tweet in a discreet structure, including: user_mentions, urls, and hashtags. While entities are opt-in on timelines at present, they will be made a default component of output in the future. See Tweet Entities for more detail on entities.
    • http://api.twitter.com/1/statuses/followers.json?include_entities=true

Extended Discussion

The URL pattern /version/statuses/followers/:screen_name_or_user_id.format is still accepted but not recommended. As a sequence of numbers is a valid screen name we recommend using the screen_name or user_id parameter instead.

Related Documentation

This document last updated by themattharris on July 19, 2010