The endpoints described in this section are the replacements of the v1.1 endpoints that allow you to lookup and manage follow relationships:
- GET followers/ids
- GET followers/list
- GET friends/ids
- GET friends/list
- POST friendships/create
- POST friendships/destroy
If you are currently using any of these endpoints, you can use our migration materials to start working with the new v2 versions.
Learn more about the new Twitter API v2: Early Access.
Following users is one of the most foundational actions on Twitter.
We offer two sets of endpoint groups to help you lookup, create, and delete follow relationships: follows lookup and manage follows.
The follows lookup endpoints enable you to explore and analyze relationships between users, which is sometimes called network analysis. Specifically, there are two REST endpoints that return user objects representing who a specified user is following, or who is following a specified user.
You can authenticate these endpoints with either OAuth 1.0a User Context or OAuth 2.0 Bearer Token. Also, you can request up to 1,000 users per request, and pagination tokens will be provided for paging through large sets of results.
The manage follows endpoints enable you to follow or unfollow users. Since you are making a request on behalf of a user, you must authenticate these endpoints with OAuth 1.0a User Context and use the access tokens associated with the user who you would like the follow/unfollow action to happen on behalf of.
You are limited to 400 follow actions per day on behalf of each authenticated user, and will be limited to 1,000 actions per day per App across all of your authenticated users. For example, if you have five authenticated users, you can follow 400 users per day (per user limit) with two of those users for a total of 800 actions, and will have to split the remaining 200 actions (per app) amongst the remaining three users. This limit does not apply to the unfollow endpoint, which has a separate limit of 500 actions per day (per app).