Submit a TikTok username and retrieve its collected video records after the collection task finishes
TikTok Account Info
Collect public profile details, audience metrics, and verification signals for one or more TikTok accounts
Overview
TikTok profile pages mix identity, audience size, verification, and contact clues in a layout that is hard to compare across accounts. This app turns those public profiles into a consistent record set so research, partnership, and monitoring teams can work from the same identifiers, metrics, and timestamps.
The value is the joined profile snapshot: displayed name, account ID, public URL, follower and like figures, privacy and verification flags, bio text, and collection time stay together for each submitted username. That makes it easier to qualify creators, compare audience scale, and keep a watch list current without reconstructing profiles by hand.
Data notes
The data comes from the public TikTok profile associated with each submitted username. One record is produced for each submitted username when the source returns a profile or a no-data marker. Duplicate submitted usernames are removed across collected pages. Audience counts, bio text, commerce attributes, location, region, and timestamps retain the source text; a source value can be unavailable and appear empty. Follower count, Follow count, Following, Like count, and Video count are kept as source text rather than normalized numbers. Collected at is preserved as supplied, without inferring a timezone. Follow count and Following can carry the same source value, and Bio and Intro can repeat the same text. Private, banned, and login-only accounts are outside the coverage.
What the results look like
Each record represents the public profile collected for one submitted TikTok username.
| Account name | Account ID | Profile URL | Submitted account | No data |
|---|---|---|---|---|
| Nio | 6893678385759912962 | https://www.tiktok.com/@niogitsune | niogitsune | No |
| demo.account | Yes |
Additional values include Avatar URL, Bio, Bio link, Business ID, Commerce info, Collected at, Follower count, Follow count, Following, Has email, Intro, Language, Like count, Location, Private account, Region, Source keyword, User status text, User status, Verified, Video count, and YouTube linked.
Use cases
- Qualify partnership targets by comparing Account name, Account ID, and Follower count across a watch list.
- Map public presence by lining up Profile URL, Bio link, Location, and Region for accounts you already monitor.
- Separate empty outcomes from usable profiles by checking No data together with Submitted account before using Like count or Video count.
- Distinguish public versus restricted profiles by reading Private account, Verified, and User status together with Account name.
Scope and boundaries
Each run accepts 1 to 200 TikTok usernames and returns at most one public profile record per username when data is available.
- Good for
- When you need a current public profile snapshot for specific TikTok accounts
- When you need displayed audience size, verification, privacy, and public contact clues in one record
- Do not use for
- When you need videos, comments, or search results rather than account-level profile information
- When you do not have a TikTok username to collect
Failure handling
Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.
- 1If no profile data is returned, verify the username and confirm the account is still public
- 2Retry later after rate limiting, temporary unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4If authentication fails, verify the API Key configured for the execution environment
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
- TikTok username list
itemsRequiredarray<object>The TikTok usernames to collect. Submit 1 to 200 items; each item needs one username.Itemsup to 200 itemsExample[{"account":"niogitsune"}]
Output
Field structure of a single record, generated from the output.schema in manifest.json.
- Submitted account
task_itemstringThe username submitted for this recordExampleniogitsune - No data
no_databooleanWhether this submitted username returned no public profileExamplefalse - Source keyword
keywordstringThe source keyword associated with the collected accountExampleniogitsune - Account ID
account_idstringThe TikTok account identifier returned for the profileExample6893678385759912962
Sample data
Generated from output.schema. Fields without a sample value use structural placeholders.
{
"task_item": "niogitsune",
"no_data": false,
"keyword": "niogitsune",
"account_id": "6893678385759912962",
"account_name": "Nio",
"account_avatar_url": "https://p16-common-sign.tiktokcdn-us.com/tos-maliva-avt-0068/447a24696d4a4decab543181ac90bdd5~tplv-tiktokx-cropcenter:720:720.jpeg?dr=9640&refresh_token=724beb04&x-expires=1788069600&x-signature=YlUb%2BXGVJC8OkIjs2jyEWNIDTF8%3D&t=4d5b0474&ps=13740610&shp=a5d48078&shcp=81f88b70&idc=useast8",
"account_signature": "Cosplayer, pop culture enthusiast, not a professional VA. Ko-Fi in bio 🫶",
"bio_link": "https://linktr.ee/niogitsune",
"biz_id": "niogitsune",
"commerce_user_info": "{\"commerceUser\":false,\"category\":null,\"categoryButton\":null}",
"crawl_time": "2026-08-28T14:42:15",
"fans_count": "27691",
"follow_count": "2648",
"following": "2648",
"heart_count": "1247162",
"intro": "Cosplayer, pop culture enthusiast, not a professional VA. Ko-Fi in bio 🫶",
"is_mail": false,
"is_private": false,
"is_verified": false,
"is_youtube": false,
"language": "en",
"location": "<location>",
"original_url": "https://www.tiktok.com/@niogitsune",
"publish_content_count": "126",
"region": "<region>",
"user_status": "0",
"user_status_text": "<user_status_text>"
}Integration
This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.
With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/tiktok-account-info",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)
detail.access.mcp.composeHint
Pricing
Charged once per submitted run, regardless of how many records are returned.
Charged by the number of records successfully returned. Failed runs are not charged.
Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.
View creditsTry it now
Fill in the parameters and run. Results come from a real call.