Please note

We recently released follows lookup, a set of Twitter API v2 endpoints that have similar functionality to this one. The new version is currently in development and serves adequate access for the majority of developers on our platform. While elevated levels of access are coming soon, developers in need of higher levels of access should continue to use this endpoint along with the Twitter API v2 version.

GET followers/list

Returns a cursored collection of user objects for users following the specified user.

At this time, results are ordered with the most recent following first — however, this ordering is subject to unannounced change and eventual consistency issues. Results are given in groups of 20 users and multiple "pages" of results can be navigated through using the next_cursor value in subsequent requests. See Using cursors to navigate collections for more information.

Resource URL¶

https://api.twitter.com/1.1/followers/list.json

Resource Information¶

Response formats	JSON
Requires authentication?	Yes
Rate limited?	Yes
Requests / 15-min window (user auth)	15
Requests / 15-min window (app auth)	15

Parameters¶

Name	Required	Description	Default Value	Example
user_id	optional	The ID of the user for whom to return results.		`12345`
screen_name	optional	The screen name of the user for whom to return results.		`twitterdev`
cursor	semi-optional	Causes the results to be broken into pages. If no cursor is provided, a value of `-1` will be assumed, which is the first "page." The response from the API will include a `previous_cursor` and `next_cursor` to allow paging back and forth. See Using cursors to navigate collections for more information.	`-1`	`12893764510938`
count	optional	The number of users to return per page, up to a maximum of 200. Defaults to 20.		`42`
skip_status	optional	When set to either `true`, `t` or `1`, statuses will not be included in the returned user objects. If set to any other value, statuses will be included.	`false`	`false`
include_user_entities	optional	The user object `entities` node will not be included when set to `false`.	`true`	`false`

Example Request¶

GET https://api.twitter.com/1.1/followers/list.json?cursor=-1&screen_name=twitterdev&skip_status=true&include_user_entities=false

Example Response¶

{
  "users": [
      {user-object},
      {user-object},
      {user-object}
  ],
  "next_cursor": 1489467234237774933,
  "next_cursor_str": "1489467234237774933",
  "previous_cursor": 0,
  "previous_cursor_str": "0"
}

For more detail, see the user-object definition.