TikTok API

TikTok Following API

List the accounts a TikTok user follows (handle, display name, follower count, bio) by username.

POST/v1/run/tiktok.following
Uptime
100.00%
30d · 1 call
Requests
1
30d · weekly, last 12 wks
Response
2.2s
median · 30d

Try it

Make your first request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `nextCursor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
  "data": {
    "following": [
      {
        "bio": "A short example description of this item.",
        "displayName": "Alex Rivera",
        "followers": 12500,
        "handle": "alex_rivera",
        "id": "a1b2c3d4",
        "region": "CA",
        "videos": 248
      }
    ],
    "nextCursor": "example"
  },
  "found": true
}
Response interface
interface TiktokFollowingResponse {
  data: {
    following: {
      bio: string;
      displayName: string;
      followers: number;
      handle: string;
      id: string;
      region: string;
      videos: number;
    }[];
    nextCursor?: string | null;
  } | null;
  found: boolean;
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

Request, response, and price

Last verified 2026-09-16 · uptime and latency measured over 30d
POST /v1/run/tiktok.following
curl -X POST https://api.getanyapi.com/v1/run/tiktok.following \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"handle":"stoolpresidente"}'
FieldTypeExample value
Request body
handlestring"stoolpresidente"TikTok username without the leading @ (e.g. "stoolpresidente").
cursorstringPagination cursor from a previous response.
requireCursorbooleanDeprecated; send `requireFields: ["nextCursor"]` instead, which does exactly the same thing. Set true if you intend to page through results, so the request is only served by a source that can return a nextCursor. Omit it and routing is unchanged, with the cheapest source serving. This can raise your price: when the cheapest source cannot page, a source that can serves, and you are quoted and charged its price. It stays accepted so callers that already send it keep working.
requireFieldsarrayOptional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `nextCursor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Response
dataobject
data.followingcan requireobject[]
data.following[].biocan requirestring
data.following[].displayNamestringPopulated whenever the provider has data for the entity.
data.following[].followerscan requireinteger
data.following[].handlestringPopulated whenever the provider has data for the entity.
data.following[].idstringPopulated whenever the provider has data for the entity.
data.following[].regionstringPopulated whenever the provider has data for the entity.
data.following[].videoscan requireinteger
data.nextCursorcan requirestringOpaque cursor for the next page of followed accounts, or null when this lane has no more. Pass it back as cursor to continue.
foundboolean
Price
Price per requestUSD$0.0012
Price /1k reqUSD$1.20

FAQ

About the TikTok Following API

The AnyAPI TikTok Following API returns TikTok following data as normalized JSON from one POST call to /v1/run/tiktok.following. List the accounts a TikTok user follows (handle, display name, follower count, bio) by username. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of TikTok following calls through AnyAPI succeeded, with a median response time of 2.2 seconds across 1 measured calls.

It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

List the accounts a TikTok user follows (handle, display name, follower count, bio) by username. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of TikTok following calls through AnyAPI succeeded, with a median response time of 2.2 seconds across 1 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.