X Twitter Followers and Followings Scraper

Retrieve either followers or followings for one or more X/Twitter accounts. Provide usernames, numeric user IDs, or both. Each run collects exactly one relationship type: followers or followings.

What this Actor returns

The Actor writes one Dataset item for each related account. If one X API page returns 200 users, the Actor stores up to 200 Dataset items.

Each Dataset item includes source-account metadata plus the raw X API user object:

{
  "source_user_id": "44196397",
  "source_screen_name": "elonmusk",
  "requested_identifier": "elonmusk",
  "relationship_type": "followers",
  "user": {
    "id_str": "1278722158970068993",
    "screen_name": "example",
    "name": "Example User"
  }
}

The user object is not simplified or remapped. It is stored as returned by the X followers/followings endpoint.

Input

• screenNames: X/Twitter usernames without @.
• userIds: numeric X user IDs stored as strings.
• relationshipType: exactly followers or followings.
• maxItemsPerUser: maximum Dataset items for each source account. Use 0 to request all available pages in the current run.

At least one value must be provided in screenNames or userIds. You can provide both; duplicate source accounts are processed once.

Followers example

{
  "screenNames": ["elonmusk"],
  "relationshipType": "followers",
  "maxItemsPerUser": 1000
}

Followings example

{
  "userIds": ["44196397"],
  "relationshipType": "followings",
  "maxItemsPerUser": 10
}

Pagination and limits

Each X API request asks for up to 200 users. The Actor follows cursors automatically and stores results page by page.

• maxItemsPerUser: 10 stores at most 10 users per source account.
• maxItemsPerUser: 0 attempts to fetch every available page in the current run.
• Large accounts can hit X rate limits, Actor runtime limits, or higher platform usage costs.
• Protected, unavailable, or rate-limited accounts may return partial or no data.

Already stored Dataset items are preserved if a later page fails.

Credentials and privacy

X credentials are loaded from private Actor storage and are not part of the public input. Raw auth_token, ct0, cookies, local credential files, and login files are not written to the Dataset.

Use public relationship data lawfully and follow X, Apify, and applicable privacy requirements.