Collect public X profiles followed by one or more usernames, returning identity, biographies, account signals, visible counters, and source-account context.

X Following List API

Following relationships
Profile context
Per-account limits
0.5 credits / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

X Following List

X Following Lists are publicly visible account relationships showing which profiles a source account follows, with identity, biographies, links, images, account status, counters, and creation details. These records support interest-network research, account discovery, relationship mapping, and profile dataset enrichment.

Features

  • Multi-account following collectionAccept one or more public X usernames and apply a separate bounded following-list collection to every source account.
  • Profile identity and contextReturn followed-account IDs, usernames, display names, canonical URLs, biographies, websites, locations, avatars, banners, and account creation times.
  • Account signals and public countersCombine visible verification, protection, messaging, pinned-post, and automation signals with follower, following, post, media, and like counts.
  • Normalized source-aware recordsKeep each saved profile in a consistent public structure with collected_at and extra.input_username for source traceability.

Parameters

ParametersRequiredDescription
usernamesRequiredRequired array of non-empty public X usernames. Values may include or omit a leading @.
results_limitOptionalMaximum followed profiles requested per username. Defaults to 200 and accepts multiples of 200 from 200 through 2000.

How to Use

Submit public source usernames, then read the normalized followed-profile records from the completed asynchronous task.

  1. Prepare one or more public X usernames, with or without a leading @, and choose a per-username results_limit that is a multiple of 200 from 200 through 2000.
  2. POST usernames and results_limit to /v1/x/following-list, then retain the returned task_id.
  3. Poll GET /v1/tasks/{task_id} while the task is queued, running, or retrying, and stop when it succeeds or fails.
  4. After success, read data.results.items and continue requesting the task with next_cursor while data.results.has_more is true.
curl -X POST "https://api.socq.ai/v1/x/following-list" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"usernames":["@X"],"results_limit":200}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and pass next_cursor while data.results.has_more is true

Best Use Cases

  • Interest-network research: Connect each retained source username with followed profile identities, biographies, links, and locations to examine the public interests around known accounts.
  • Account discovery from seed profiles: Use names, biographies, images, verification signals, and visible counters to review candidate accounts found through a source profile's public following list.
  • Relationship-list enrichment: Add stable IDs, canonical profile URLs, public account metadata, counters, and collection times to existing username-based relationship records.

Pro Tips

  • Trim leading @ characters and deduplicate source usernames case-insensitively before submission so equivalent handles do not repeat source-account work.
  • Size results_limit per username in increments of 200; with several sources, plan for up to usernames × results_limit records before list endings and task-level deduplication.
  • When building a many-to-many graph, do not assume one saved row per source-profile pair because a repeated followed profile can be deduplicated and retain only one extra.input_username value.
  • Treat an empty or short list as a public-visibility outcome, and allow optional images, status signals, and counters to remain nullable in downstream records.
  • Do not interpret returned order as relationship age, interaction strength, or endorsement because the response exposes collection order rather than those signals.

Use these APIs when you need a different type of public X data.

  • Twitter Tweet Scraper APIRetrieve public post text, authors, engagement, media, hashtags, mentions, and conversation relationships from x.com or twitter.com status URLs.
  • Twitter Profile Scraper APIRetrieve public account identity, biographies, avatars, cover images, account status, and visible audience statistics by username.
  • Twitter User Tweets Scraper APICollect recent public posts, authors, media, hashtags, mentions, and engagement by username with replies excluded.
  • Twitter Search APIFind public posts by search expression with latest or top ordering and a configurable result limit.
  • X Followers List APICollect public follower account identities and visible profile metrics for one or more X usernames.
  • X Post Quotes APICollect public quote posts for known status URLs with commentary, authors, engagement, media, timestamps, and source-post context.
  • X Post Replies APICollect public replies from X post URLs with selectable ordering, reply text, authors, visible engagement, media, and parent-post context.
  • X Post Retweeters APICollect a task-level unique set of normalized public profiles for accounts that reposted known X or Twitter status URLs.
  • X Trends APICollect current public X trend snapshots for known numeric WOEIDs with source rank, query, description, and location context.

X Following List APIFAQ