get-followers-ids

GET followers/ids

Returns a cursored collection of user IDs for every user 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 5,000 user IDs 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.

This method is especially powerful when used in conjunction with GET users / lookup, a method that allows you to convert user IDs into full user objects in bulk.

Resource URL¶

https://api.x.com/1.1/followers/ids.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.		`noradio`
cursor	semi-optional	Causes the list of connections to be broken into pages of no more than 5000 IDs at a time. The number of IDs returned is not guaranteed to be 5000 as suspended users are filtered out after connections are queried. 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`
stringify_ids	optional	Some programming environments will not consume Twitter IDs due to their size. Provide this option to have IDs returned as strings instead. More about Twitter IDs.	`false`	`true`
count	optional	Specifies the number of IDs attempt retrieval of, up to a maximum of 5,000 per distinct request. The value of `count` is best thought of as a limit to the number of results to return. When using the count parameter with this method, it is wise to use a consistent count value across all requests to the same user's collection. Usage of this parameter is encouraged in environments where all 5,000 IDs constitutes too large of a response.		`2048`

Example Request¶

GET https://api.x.com/1.1/followers/ids.json?cursor=-1&screen_name=andypiper&count=5000

$ curl --request GET 
--url 'https://api.x.com/1.1/followers/ids.json?screen_name=twitterdev' 
--header 'authorization: Bearer <bearer>'

$ curl --request GET 
  --url 'https://api.x.com/1.1/followers/ids.json?screen_name=twitterdev' 
  --header 'authorization: OAuth oauth_consumer_key="consumer-key-for-app", 
  oauth_nonce="generated-nonce", oauth_signature="generated-signature", 
  oauth_signature_method="HMAC-SHA1", oauth_timestamp="generated-timestamp", 
  oauth_version="1.0"'

$ twurl /1.1/followers/ids.json?screen_name=twitterdev

Example Response¶

{
    "ids": [
        455974794,
        947576438684872705,
        850839346009780224,
        958850376630910976,
        889483959943536640,
        966094285119606784,
        1020583045,
        948604640811212801,
        967155179614240768,
        554514802,
        14873932,
        963916668731904000,
        970763391181746178,
        966091392631140358,
        .
        .
        .
        5000 ids later,
        .
        .
        .
        813143846,
        958604886735716353,
        402873729,
        958603486551330817,
        913076424897994753,
        820967329068707840,
        958593574932762624,
        958589381102665728,
        958573223737724929,
        889474485694410752
    ],
    "next_cursor": 1591087837626119954,
    "next_cursor_str": "1591087837626119954",
    "previous_cursor": 0,
    "previous_cursor_str": "0"
}