TikTok Followers & Following Scraper

A TikTok handle goes in, and the accounts from that profile's following list come back as rows. Each row is the whole profile as the list shows it: display name, bio, avatar, region, verified flag and that account's own follower, following, video and like counts. You don't have to take the handles away and look every one of them up again.

Follower lists work the same way, but since August 2026 they need a cookie of yours. There's a section on that below. Read it before you set listType to followers.

What you get per row

uniqueId, userId, secUid, nickname, signature (the bio), avatar, verified, region, followerCount, followingCount, videoCount, likesCount, profileUrl, plus sourceProfile and listType so you know which list a row came from, and scrapedAt.

Input

{
  "profiles": ["tiktok", "https://www.tiktok.com/@nba"],
  "listType": "following",
  "maxItemsPerProfile": 200,
  "maxRunSeconds": 120
}

Field	Default	Notes
profiles	—	Handles, @handles, profile URLs or numeric user IDs.
listType	following	following, followers, or both. Read the next section before picking followers.
maxItemsPerProfile	100	Per source profile and per list type, 1 to 1,000.
maxRunSeconds	90	Wall-clock deadline, 10 to 180. The run stops paging and returns what it has.
sessionCookies	empty	Optional, see below.
fallbackToProxy / proxyConfiguration	off	Optional retry through your Apify proxy config after a direct failure.

Following works without a cookie. Followers currently doesn't.

This is the thing to know before you run it.

Following lists are the keyless path and the default. You need no account, no cookie and no API key.

Follower lists are not. As of 17 August 2026 the public source retired its follower endpoint, and TikTok's own follower endpoint answers a signed-out request with an empty body. A followers run without a cookie therefore returns an uncharged diagnostic row saying exactly that, instead of grinding through retries and billing you for nothing. To read follower lists, paste your own TikTok cookie into sessionCookies:

1. Sign in to TikTok in Chrome.
2. F12 → Application → Cookies → https://www.tiktok.com.
3. Copy sessionid and pass it as "sessionid=<value>". Adding sid_tt makes it last a bit longer.

Your cookie is sent only to TikTok's own endpoints, its value is never written to the log, and you can pass several so the run rotates between them.

The run's status line ends with sessionState, which tells you which path served the rows: keyless, ok, degraded or exhausted.

Other limits

• 1,000 rows per profile per list is the input ceiling. Accounts with millions of followers are not fully enumerable here, and no keyless tool is going to change that.
• The wall-clock deadline is real. At maxRunSeconds: 90 a big list will be cut off mid-way; raise it to 180 or lower maxItemsPerProfile if you want completeness over speed.
• Rows are deduplicated per source profile and list type before they're pushed, so both never bills you twice for someone who is in both lists.
• Private accounts and lists a signed-out visitor can't see return a diagnostic row, not an error.

Output

{
  "ok": true,
  "type": "relationship_profile",
  "uniqueId": "tiktokcreators",
  "userId": "6551237489917432832",
  "nickname": "tiktok creators",
  "signature": "The official account for TikTok Creators…",
  "verified": true,
  "region": "US",
  "followerCount": 8688599,
  "followingCount": 568,
  "videoCount": 1102,
  "likesCount": 33415006,
  "profileUrl": "https://www.tiktok.com/@tiktokcreators",
  "sourceProfile": "@tiktok",
  "listType": "following"
}

Run it with an empty profiles list and you get one labelled sample row. No request goes out and nothing is charged beyond the start fee.

Billing

$0.001 when a run starts, then $0.00035 per profile returned, which is $0.35 per 1,000. Flat on every plan.

Sample rows, diagnostic rows and duplicates are never charged. A run that finds nothing costs you the $0.001 start fee.

Responsible use

This only asks for relationship data TikTok already shows on a public profile. Don't use it to collect private account data, get around access controls, or break TikTok's terms or the privacy law that applies to you.