Public TikTok data, field by field

TikTok User Profile API

Use the GoAnyAPI TikTok User Profile API to look up a public account by full profile URL or username. Read identity, bio, avatar, verification fields and available account counts.

1 credits per non-empty successful request; empty results and failures are free.

GETExample response
https://api.goanyapi.com/api/v1/tiktok/user-profile?url=https%3A%2F%2Fwww.tiktok.com%2F%40spidey.glow
Visual

Run a request to see the visual result

The response is organized into metrics, lists and tables that match the JSON on the right.

Run a request to see the response here

Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.

Read a profile without mixing identity and statistics

The TikTok User Profile API turns a known public account into a structured profile record. A developer can display the account’s name, bio and avatar; an editor can verify which account a saved profile link identifies. The response separates identity in data.user from account counts in data.stats and data.statsV2. Read those objects together, without treating the profile itself as a list of published videos. The API documentation explains the accepted inputs and complete field definitions. In the Tester, the visual summary and JSON are two views of the same saved example or query result.

Input → account identity → public counts

For example, supply the full profile URL https://www.tiktok.com/@spidey.glow or the username spidey.glow, without the leading @. Choose one input. When a nonempty result is returned, match data.user.uniqueId to the intended username and read data.user.nickname as its display name. Read biography text from data.user.signature. Account-level follower and video counts belong under data.stats or data.statsV2, not under data.user. The example shows an input format, not a new request or a claim about the account’s current figures. If your next task is simply to list its public videos, send the same URL or username directly to the User Posts API. A profile lookup is optional.

Account identifiers · data.user.id, data.user.uniqueId
The account ID and username are separate fields; neither is the display nickname. Retain returned identifiers without rounding large values. Keep the input and returned identity with your own record so that a later display-name change is not mistaken for another account.
Display name and bio · data.user.nickname, data.user.signature
Use the nickname as the display label and the signature as the returned biography. A bio describes what the account has chosen to say about itself. It is useful for a profile card, but is not independently verified evidence about the person or organization.
Avatar variants · data.user.avatarThumb, data.user.avatarMedium, data.user.avatarLarger
These fields can provide different avatar image sizes. Use an available variant appropriate to your interface and handle an unavailable image without inventing a replacement account photo. Returned image addresses should not be treated as permanent assets.
Account flags · data.user.verified, data.user.privateAccount
Read each flag as returned, preserving false as a value distinct from missing or null. A verification flag is an account attribute, not a GoAnyAPI assessment of suitability. A privacy flag does not grant access to private posts.
Public counts · data.stats and data.statsV2
Look for followerCount, followingCount, videoCount and available likes-related counts here. For example, the follower path is data.stats.followerCount, or its returned counterpart in the second object. Do not add parallel counts together or infer missing statistics from the profile text.
Returned identifier · data.user.secUid
This may be present as an account identifier in the result. It is not a public input for the current User Posts API. Keep it only if your own record needs the returned field; finding it is not a prerequisite for querying posts.
Values and settlement
JSON retains the returned keys and values, including empty values. A visual dash does not mean zero followers. data.creditsUsed reports the charge for this request and data.remainingCredits the settled balance. A partially populated profile is not automatically an empty result.

Profile scope and independent requests

Supply url or username, never both. Use a full HTTPS profile URL; short sharing links are unsupported. Usernames contain letters, digits, periods or underscores, without @. This endpoint has no pagination. A successful nonempty profile request uses its own current configured rate, shown in the Tester; resolving the URL adds no extra fee. Empty results and failures are free. If you separately request posts, that request uses the posts API’s own rate and result rules. You do not need to pay for a profile request first. A real query requires a valid GoAnyAPI API key and sufficient credits.

What you can build from the profile

A public account card

Developers can combine the returned nickname, bio, avatar and available counts in their interface. The API provides the fields; your application decides how to display missing values and where to retain a record.

A dated account record

Editors can save a profile response with their own observation time. Comparing saved records is a separate operation; this lookup does not return a growth chart, automatically store history or schedule future checks.

A separate content view

Use User Posts directly when you need videos rather than profile fields. An account’s video count is a public statistic, not a guarantee that paging through available posts will retrieve that exact number of records.

Frequently asked questions

No audience age, geography or interest breakdown is established by these public profile fields. A username, bio or follower count cannot be used as a substitute for audience data.

Do not assume a fixed representation or complete overlap. Inspect the actual values returned in JSON and handle absent, empty, numeric or string values as appropriate. The second object is not an extra group of followers to add.

Use the supported username or full profile URL. A display nickname is not the username, and the returned numeric account ID and secUid are not alternative public lookup inputs for this endpoint.

No. The profile contains account details and available counts. The User Posts API is a separate, directly usable lookup with its own pagination and billing. Neither endpoint promises access to private, deleted or unavailable content.

RELATED APIS

Explore the account’s content separately

Use Video Details for one known video, User Posts for an account’s available public videos, and Hashtag Details for a known tag’s public description and counts.