TikTok User Search Scraper - Creator Profiles
Pricing
from $5.00 / 1,000 profile scrapeds
TikTok User Search Scraper - Creator Profiles
Search TikTok users by keyword and extract public creator profiles with handles, bios, follower counts, verification, avatars and profile URLs. No login or cookies needed.
Pricing
from $5.00 / 1,000 profile scrapeds
Rating
0.0
(0)
Developer
Khadin Akbar
Maintained by CommunityActor stats
0
Bookmarked
9
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
What is TikTok User Search Scraper - Creator Profiles?
TikTok User Search Scraper - Creator Profiles accepts public keyword queries for TikTok users and creators, then returns one normalized creator profile per dataset record. It is built for audiences who start with a brand, niche, or person name and want structured fields such as username, profileUrl, nickname, bio, followerCount, verified, avatarUrl, privateAccount, and scrapedAt. The outcome is a clean, provider-backed shortlist of public creator profiles that can be reviewed by people or passed into AI workflows.
Best fit and connected workflows
This actor fits workflows that begin with a keyword search and end with a public creator shortlist.
It is a strong routing choice when you want to:
- Discover TikTok creators by topic, brand, niche, or name.
- Build lead lists from public creator profiles.
- Filter discovery with
minFollowerCount,verifiedOnly, orexcludePrivateAccounts. - Feed selected public profiles into downstream enrichment.
- Give AI agents a compact dataset with stable fields and clear provenance.
Connected workflow paths:
- Search first, then enrich public creator profiles with related feed or video actors.
- Search a brand or niche, then sort results by follower count or verification.
- Search public names or public figure terms, then review profile URLs and identity fields.
- Search multiple keywords, then use
maxTotalProfilesandmaxProfilesPerQueryto keep the run focused.
Practical scenario
Maya is planning a skincare outreach list. She enters skincare creator as the search query and sets minFollowerCount to 10000. The dataset returns rows with username, profileUrl, nickname, bio, verified, followerCount, privateAccount, and provider.
Maya reviews the bios for topical fit, checks follower counts for audience size, and looks at verification status for brand-safe screening. Her next action is to open the returned profile URLs and pass the selected creators into a downstream enrichment workflow.
Input
| Field | Type | Purpose |
|---|---|---|
searchQueries | array of strings | Required. One query per line for keyword, brand, niche, or person-name search. |
providerOrder | string | Chooses which public-data provider is tried first. |
maxProfilesPerQuery | integer | Caps saved creator profile rows per query. |
maxPagesPerQuery | integer | Safety cap for provider pagination per query. |
maxTotalProfiles | integer | Caps the full run across all queries. |
minFollowerCount | integer | Keeps profiles at or above a follower threshold. |
verifiedOnly | boolean | Returns profiles that are verified or have a provider verification label. |
excludePrivateAccounts | boolean | Skips profiles marked private by TikTok or the provider response. |
trim | boolean | Requests smaller provider payloads when supported. |
includeRawData | boolean | Attaches the original provider item to each dataset row. |
Example input
{"searchQueries": ["beauty creator","soccer coach"],"maxProfilesPerQuery": 20,"maxPagesPerQuery": 2,"maxTotalProfiles": 40,"minFollowerCount": 5000,"verifiedOnly": false,"excludePrivateAccounts": false,"trim": false,"includeRawData": false}
Output
Each dataset item is one normalized TikTok user profile row.
| Field | Type | Purpose |
|---|---|---|
recordType | string | Record category for this actor's rows. |
searchType | string | Search surface used for the row. |
provider | string | Public-data provider that returned the result. |
query | string | Search query that produced the row. |
resultPosition | integer | Position in the normalized saved list for the query. |
page | integer | Provider page number that returned the profile. |
cursor | string, number, null | Provider pagination cursor when available. |
userId | string, null | TikTok numeric user ID when returned. |
userSecUid | string, null | TikTok secure user ID when returned. |
username | string, null | TikTok handle from the search result. |
profileUrl | string, null | Canonical public TikTok profile URL. |
nickname | string, null | Display name from the search result. |
bio | string, null | Profile bio, signature, or search description. |
bioLink | string, null | Public bio link when returned. |
verified | boolean, null | Verification flag from TikTok or provider metadata. |
customVerify | string, null | Provider verification label or reason. |
verificationType | integer, null | Verification type code when returned. |
avatarUrl | string, null | Largest available profile avatar URL. |
avatarThumbUrl | string, null | Smaller profile avatar URL when available. |
followerCount | integer, null | TikTok follower count. |
followingCount | integer, null | Number of accounts followed. |
heartCount | integer, null | Total likes across the profile's videos when returned. |
videoCount | integer, null | Number of videos posted when returned. |
privateAccount | boolean, null | Private-account flag from TikTok or provider. |
commerceAccount | boolean, null | Commerce or shop-related flag when returned. |
language | string, null | Language code when available. |
region | string, null | Region or account region when available. |
scrapedAt | string | ISO 8601 timestamp when the row was saved. |
rawResult | object, null | Original provider item when includeRawData is enabled. |
Example output record
{"recordType": "user","searchType": "users","query": "beauty creator","resultPosition": 1,"page": 1,"cursor": 10,"userId": "6881290705605477381","userSecUid": "MS4wLjABAAAAqB08cUbXaDWqbD6MCga2RbGTuhfO2EsHayBYx08NDrN7IE3jQuRDNNN6YwyfH6_6","username": "taylorswift","profileUrl": "https://www.tiktok.com/@taylorswift","nickname": "Taylor Swift","bio": "This is pretty much just a cat account","verified": true,"customVerify": "Verified account","verificationType": 0,"avatarUrl": "https://p16-amd-va.tiktokcdn.com/avatar.jpeg","avatarThumbUrl": "https://p16-amd-va.tiktokcdn.com/avatar_thumb.jpeg","followerCount": 33800000,"followingCount": 0,"heartCount": 267837265,"videoCount": 88,"privateAccount": false,"commerceAccount": false,"language": "en","region": "US","scrapedAt": "2026-07-09T12:00:00.000Z"}
How it works
This actor uses public-data providers for TikTok user search. The live contract lists the primary data provider as the primary provider and the fallback data provider as a fallback option, with provider order controlled by providerOrder. It returns normalized creator profile rows to the default dataset and writes run-level diagnostics to RUN_SUMMARY in the key-value store. It is provider-backed, uses no TikTok cookies, and is available as an Apify Actor usable through Apify MCP.
The dataset includes a standard overview view for creator profiles and a profile IDs view that exposes username, userId, userSecUid, profileUrl, avatarUrl, customVerify, provider, and query.
Pricing
This actor uses Pay per event pricing with Apify platform usage included. Live pricing values are shown in the actor's Pricing tab.
Charged events in the live contract:
- Actor start: charged once per run, scaled by allocated memory.
- Profile scraped: charged for each normalized TikTok user profile record saved to the dataset.
Example in words: if a run saves twenty profile records, the execution includes one actor start event and twenty profile scraped events.
Apify platform usage such as storage and compute follows your Apify account and execution settings. For the current live Pricing tab values, check the actor page in Apify Console before running.
Use with AI agents (MCP)
This actor is designed for use through Apify MCP. It provides a focused tool for public TikTok user search and returns structured creator profile rows that AI agents can read, summarize, filter, and route into downstream steps.
Actor identity: khadinakbar/tiktok-user-search-scraper
Search TikTok users for the keyword "skincare creator". Return up to 15 public profiles, highlight usernames, profile URLs, bios, verification flags, and follower counts, and summarize the rows from the dataset.
Output interpretation:
- Each dataset row represents one normalized public TikTok user profile.
queryshows which search term produced the row.resultPositionshows the row order within that query.providerandpagehelp trace provenance through provider search.scrapedAtshows when the row was normalized and saved.rawResultis present whenincludeRawDatais enabled.
Scope and provenance:
- This actor searches TikTok users by public keyword.
- It returns creator profile metadata from the provider response, not TikTok videos, comments, or feeds.
- Each row retains source provenance through provider fields and optional
rawResult.
Pagination and cost guidance:
maxPagesPerQuerycontrols provider pagination.maxProfilesPerQuerycaps saved rows per query.maxTotalProfilescaps the whole run.- These settings help shape event volume because
profile-scrapedis the primary charged event.
Apify API example
import { ApifyClient } from 'apify-client';const client = new ApifyClient({token: process.env.APIFY_TOKEN,});const run = await client.actor('khadinakbar/tiktok-user-search-scraper').call({searchQueries: ['beauty creator'],maxProfilesPerQuery: 10,maxPagesPerQuery: 1,maxTotalProfiles: 10,minFollowerCount: 0,verifiedOnly: false,excludePrivateAccounts: false,trim: false,includeRawData: false,});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Best results and outcome guidance
Use short, specific queries when you want a focused creator shortlist. Combine query terms with minFollowerCount when you want a size threshold, and use verifiedOnly when the workflow benefits from verification-aware discovery. Set excludePrivateAccounts to keep the dataset centered on public creator candidates. Keep maxProfilesPerQuery and maxTotalProfiles aligned with the number of search terms so the run stays controlled and the resulting dataset stays easy for humans or agents to review.
Continue the workflow
- Then use TikTok Comments Scraper - Replies & Authors to continue from TikTok User Search Scraper - Creator Profiles discovery into engagement data for the selected records.
- Then use TikTok Video Scraper - Details & Creator Feeds to continue from TikTok User Search Scraper - Creator Profiles discovery into content data for the selected records.
Design note
I found that the dataset contract includes a dedicated profileIds view with username, userId, userSecUid, profileUrl, avatarUrl, customVerify, provider, and query, which makes identity handoff to downstream workflows explicit.
FAQ
When should I use this actor instead of a profile or video scraper?
Use this actor when the starting point is a keyword search for TikTok users and the desired result is a shortlist of public creator profiles. Use a profile or video scraper after discovery when you already have a profile URL or want profile-level enrichment.
How do I connect discovery results to enrichment?
Use the returned profileUrl or username fields as the handoff into downstream creator-feed or video workflows. The related actors below fit that pattern.
Which fields are most useful for creator review?
Common review fields are username, profileUrl, nickname, bio, verified, followerCount, privateAccount, and provider. For identity workflows, userId and userSecUid are also available when returned.
Can I limit the search to public creator candidates?
Yes. Set excludePrivateAccounts to true for public-only discovery. You can also combine it with verifiedOnly for a narrower shortlist.
Does this actor work with Apify MCP?
Yes. It is an Apify Actor usable through Apify MCP and returns structured output that agents can read and route into other steps.
Responsible use
This actor is intended for public TikTok profile metadata. Use the returned data in line with applicable laws, platform terms, privacy rules, and outreach regulations. Keep outreach respectful and use the data in ways that fit your organization's policies.