TikTok Followers List API

TikTok Followers List

Features

• Multi-account collectionCollect followers for one or more public usernames, with results_limit applied independently to each submitted account.
• Bounded feed traversalTraverse supported follower pages internally until the per-account limit, an unavailable next page, or the collection ceiling is reached.
• Normalized profile recordsReturn follower ID, username, display name, biography, avatar reference, profile URL, and supported public metrics in a consistent profile shape.
• Retained source contextKeep the normalized submitted handle in extra.input_username for the retained follower record.
• Task-level duplicate controlSuppress repeated follower identities across the task by normalized ID or profile URL before results are saved and paginated.

Parameters

How to Use

Submit known public handles, wait for the asynchronous task, and page through the saved profile records.

1. Trim whitespace, remove optional leading @ characters for your own deduplication, and choose public TikTok usernames.
2. POST usernames and a per-username results_limit from 20 through 2,000 to /v1/tiktok/followers-list.
3. Save task_id and poll /v1/tasks/{task_id}; queued, running, and retrying are normal intermediate states.
4. After success, read data.results.items and pass next_cursor to the same task endpoint while has_more is true.

curl -X POST "https://api.socq.ai/v1/tiktok/followers-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 follow next_cursor while has_more is true

Best Use Cases

• Public audience sampling: Build a bounded sample of publicly visible follower profiles for qualitative audience review.
• Creator discovery queues: Collect follower usernames and profile links that can seed manual review or a later TikTok Profiles enrichment task.
• Recurring list research: Save timestamped samples from the same public accounts to observe changes in the identities available during each collection.
• Profile directory inputs: Transform public follower-list entries into consistent identity, biography, avatar, and metric fields for internal directories.

Pro Tips

• Normalize case and remove a leading @ before client-side deduplication; @name and name can otherwise trigger equivalent source lookups.
• Treat results_limit as a per-username ceiling: two usernames at the default 100 produce an estimate of 200 results, not 100.
• Keep extra.input_username, but do not use this endpoint for exact common-follower analysis because task-level deduplication retains one source context per follower identity.
• Use the follower username, not the numeric id, when passing a returned account to an endpoint that accepts TikTok usernames.
• Do not submit next_cursor in a new collection request; it only pages through results already saved for the same successful task.
• Handle metrics as nullable and created_at as null because upstream follower rows do not always expose those fields.
• Expect fewer records for private, restricted, unavailable, or very large accounts, and treat avatar references as source URLs that may expire.

Related APIs