TikTok Following List API

TikTok Following List

Features

• Source-to-profile relationshipsCollect followed profile records for each submitted public username and retain the source handle in extra.input_username.
• Normalized followed identityReturn a stable user ID, username, display name, and canonical TikTok profile URL for each saved relationship member.
• Public profile contextInclude biography text, an avatar reference, and visible account metrics exposed with the followed profile.
• Per-user bounded collectionApply results_limit separately to each username while paging available list data and deduplicating saved profiles by stable identity.

Parameters

How to Use

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

1. Prepare one or more public TikTok usernames, with or without a leading @, and choose a results_limit from 20 through 2000 for each username.
2. POST the usernames and results_limit to /v1/tiktok/following-list, then save 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. Read data.results.items after success; when has_more is true, request the same task with next_cursor to load the next stored-result page.

curl -X POST "https://api.socq.ai/v1/tiktok/following-list" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"usernames":["@loganpaul"],"results_limit":100}'

# 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: Use source-account context with followed IDs, usernames, and biographies to examine the public interests around a known account.
• Creator discovery from seed accounts: Review display names, biographies, avatars, profile links, and visible metrics to assemble a profile candidate list from an account's public follows.
• Profile dataset enrichment: Add stable IDs, canonical URLs, public biographies, avatars, and visible account metrics to username-based profile records.

Pro Tips

• Strip a leading @ and deduplicate usernames before submission so equivalent handles do not trigger duplicate source-account work.
• Set results_limit for each username based on the depth you need; larger input lists can produce up to usernames × results_limit records before list endings and deduplication.
• Use id as the primary profile key, fall back to url when it is absent, and retain extra.input_username for source traceability.
• Treat empty or short results as a public-visibility outcome, then check account privacy and list availability before retrying.
• Do not interpret returned order as recency or relationship strength unless your downstream data explicitly supplies that signal.

Related APIs