TikTok profile following API

Call GET /v1/tiktok/profiles/{handle}/following with your Social Fetch API key (x-api-key). Pass the TikTok username as the path parameter, with or without a leading @. Read data.lookupStatus, then data.accounts and data.page. Continue with cursor from data.page.nextCursor while hasMore is true.

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth. Each paginated page is a separate billed request.

handle, displayName, bio, avatarUrl, profileUrl, optional platformUserId and secUid, verified, optional privateAccount, optional region and language, optional accountCreatedAt, and metrics (followers, following, posts). Optional details may carry extra TikTok-native fields that were not mapped into the canonical shape. With trim=true, some optional identity fields may be omitted.

When data.page.hasMore is true, pass data.page.nextCursor as the cursor query param on the next request. Keep the same handle across pages. There is no userId query param on this route (that shortcut exists on the followers sibling only). The cursor is opaque. TikTok may stop exposing a list before the aggregate count is reached, so an empty accounts page means the end of the list even if the previous page reported hasMore: true. Empty pages are billed like any other page, so stop as soon as you receive one; data.totalAccounts is null when TikTok does not return a count.

found means the following list could be returned for that handle. hidden means TikTok is not exposing who the account follows. private means the account is private. not_found means no public profile matched. Branch on lookupStatus before treating an empty accounts array as "follows nobody."

This route pages the outbound following graph under data.accounts (who the seed follows) — useful for affinity and competitor peer maps. Inbound followers are GET /v1/tiktok/profiles/{handle}/followers under data.followers. Aggregate following counts without the list are on GET /v1/tiktok/profiles/{handle} under data.metrics.

No. You authenticate to Social Fetch with an API key. The route reads publicly available following-list data when TikTok exposes it; it does not act on behalf of a logged-in TikTok user.

Yes. Teams page following for several seed handles, upsert each account by handle or platformUserId, then compute overlap (shared follows), filter on region / verified / metrics.posts, and deepen selected nodes with the profile or videos routes. Keep meta.requestId if you need support on a failed page.