TikTok Scraper — Videos, Profiles & Hashtags
Pricing
Pay per usage
TikTok Scraper — Videos, Profiles & Hashtags
Scrape TikTok profiles, videos, hashtag feeds, keyword search, comments, and TikTok Shop products without login. Residential proxy built-in — TikTok blocks datacenter IPs, most competitors fail silently. Probe-first stop-gate: zero charges if your run can't reach TikTok.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Vitalii Bondarev
Maintained by CommunityActor stats
0
Bookmarked
12
Total users
3
Monthly active users
10 days ago
Last modified
Categories
Features
Share
TikTok Scraper — Profiles, Videos, Hashtags, Search & Comments
Scrape TikTok at scale without a login. Six modes cover the full TikTok data surface: user profiles, video feeds, hashtag trending, keyword search, video comments, and TikTok Shop products. Residential proxy is built in — TikTok blocks datacenter IPs at the edge, so competitors that skip this fail in production.
Pay per result.
Why this actor beats the incumbents
| What breaks most TikTok actors | How this actor handles it |
|---|---|
| Datacenter IP blocks | Forces Apify RESIDENTIAL proxy; CORE probe validates on startup |
| Signer rot (X-Bogus re-obfuscated every 2–4 weeks) | Graceful degradation: CORE modes keep working when signer breaks; actor logs exact advice |
| Cold-start failures silently producing empty datasets | Probe-first stop-gate: actor aborts with actionable error before wasting your compute |
| DOM class-name scraping that breaks on every redesign | Rehydration JSON extraction (structural, not CSS-based) for CORE modes |
| No geo-validation | Cloud run on residential IP validates real-world reachability (TikTok geo-blocks certain countries) |
6 modes
CORE modes — no request signing, most stable
| Mode | Input field | What you get |
|---|---|---|
profile | usernames | Follower/following/like/video counts, bio, verified flag, avatar |
product | productIds | TikTok Shop PDP: title, price range, rating, sold count, images |
user_videos | usernames | First page of a user's videos from rehydration JSON; full pagination if signer is healthy |
CORE modes parse TikTok's server-side rehydration JSON embedded in the page HTML. No X-Bogus signature required. These modes remain functional even when the signer breaks.
SIGNED modes — require X-Bogus signature
| Mode | Input field | What you get |
|---|---|---|
hashtag | hashtags | Videos trending under a hashtag, ranked by TikTok's feed |
search | keywords | Keyword search results with ranking position |
comments | videoIds | Comments on a specific video, including reply thread info |
SIGNED modes call TikTok's internal API endpoints and require a valid X-Bogus HMAC signature. TikTok re-obfuscates the signing algorithm every 2–4 weeks.
Signer maintenance note: When TikTok rotates the algorithm, SIGNED modes will return a
signed_probe_failederror. CORE modes continue working. Seesrc/signer.pyfor the refresh procedure. The actor's probe-first gate tells you exactly which modes are affected before any records are charged.
Output fields
Profile record (mode=profile)
| Field | Description |
|---|---|
user_id | TikTok internal user ID |
sec_uid | Encrypted user identifier (used for API pagination) |
username | Handle (e.g. charlidamelio) |
nickname | Display name |
verified | Blue-check verified account |
follower_count | Follower count |
following_count | Following count |
heart_count | Total likes received across all videos |
video_count | Public video count |
bio | Profile bio text |
region | Account region code |
profile_url | https://www.tiktok.com/@{username} |
avatar_url | Avatar image URL |
Video record (mode=user_videos)
| Field | Description |
|---|---|
video_id | TikTok video ID |
author_username | Uploader handle |
description | Video caption (may include hashtags inline) |
hashtags | Extracted hashtag list |
duration | Duration in seconds |
play_count | View count |
like_count | Like count |
comment_count | Comment count |
share_count | Share count |
collect_count | Save/bookmark count |
created_at | ISO-8601 UTC post time |
video_url | https://www.tiktok.com/@{author}/video/{id} |
thumbnail_url | Cover image URL |
music_title | Background music title |
music_author | Background music artist |
is_ad | True if TikTok marked it as an ad |
Comment record (mode=comments)
| Field | Description |
|---|---|
comment_id | Comment ID |
video_id | Parent video ID |
author_username | Commenter handle |
text | Comment text |
like_count | Comment likes |
reply_count | Replies to this comment |
is_reply | True if this is a reply to another comment |
parent_comment_id | ID of parent comment (replies only) |
created_at | ISO-8601 UTC post time |
TikTok Shop product record (mode=product)
| Field | Description |
|---|---|
product_id | TikTok Shop product ID |
shop_id | Seller shop ID |
title | Product title |
description | Product description |
category | Product category |
brand | Brand name |
price_min | Lowest SKU price (USD float) |
price_max | Highest SKU price (USD float) |
currency | Price currency code (default: USD) |
discount_pct | Discount percentage, if active |
rating | Seller rating (0–5) |
review_count | Number of reviews |
sold_count | Units sold count |
image_urls | List of product image URLs |
product_url | https://www.tiktok.com/shop/pdp/{id} |
Search / hashtag result record (mode=search or mode=hashtag)
Same video fields as above, plus:
| Field | Description |
|---|---|
query | The search keyword or hashtag that produced this result |
rank | 1-based position in the result set |
All records include
| Field | Description |
|---|---|
parse_confidence | 0.0–1.0 parse quality score. 1.0 = all required fields found |
warnings | List of warning codes (empty = clean record) |
scraped_at | ISO-8601 UTC timestamp of the scrape run |
How to use
Scrape a user profile
{"mode": "profile","usernames": ["charlidamelio", "khaby.lame"],"maxResults": 10,"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"]}}
Scrape a user's recent videos
{"mode": "user_videos","usernames": ["mrbeast"],"maxResults": 50}
Search TikTok by keyword
{"mode": "search","keywords": ["viral recipe", "skincare routine"],"maxResults": 100}
Scrape a hashtag feed
{"mode": "hashtag","hashtags": ["fyp", "foodtok"],"maxResults": 200}
Scrape video comments
{"mode": "comments","videoIds": ["7123456789012345678"],"maxResults": 500}
Scrape a TikTok Shop product
{"mode": "product","productIds": ["1729386234567890"],"maxResults": 10}
Pricing
Pay-per-result (PPE) — you pay only for records successfully pushed to the dataset. Failed lookups, probe requests, and skipped items are never charged.
PPE event: tiktok-result
Reliability and proxy
TikTok performs aggressive geo-filtering and bot detection. Key facts:
- Datacenter IPs are blocked instantly. The actor defaults to
RESIDENTIALproxy and runs a connectivity probe before scraping anything. - Cloud geo-blocks are real. Some Apify cloud regions are blocked by TikTok. The startup CORE probe validates that your run's residential IP can actually reach TikTok — if it can't, the actor exits with a clear error and zero charges.
- Signer rot. TikTok re-obfuscates the X-Bogus signing algorithm every 2–4 weeks. When this happens, SIGNED modes (
hashtag,search,comments) return asigned_probe_failederror. CORE modes (profile,product,user_videosfirst page) continue working with no intervention. Monitor actor logs forSIGNED probe: FAILto know when a signer update is needed.
Not affiliated with TikTok or ByteDance. Data is retrieved from publicly accessible TikTok endpoints.
Integrations
Built for social-media analysts and content-intelligence teams pulling TikTok profiles, video feeds, hashtags, and comments at scale — the JSON/dataset output drops into the tools you already run, no glue code:
- n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
- Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
- MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
- API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.
See all Apify integrations.
Usage statistics
This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.
Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.
Only these fields are recorded:
- schema version, Actor name and build number;
- UTC start and finish hour (not a precise timestamp);
- run duration, number of results and time to the first result, each as a coarse range;
- whether the result was empty, the end status, and an error type from a fixed list;
- memory setting and counts of charged events;
- names of the input fields you set, never their values;
- the selected option for input fields that offer a fixed list of choices (for example a sort order).
We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.
Additional fields (Phase 2)
This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.
The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.
Run-outcome signals (v2)
To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:
- the result limit you asked for (a range, when the input has one) and what share of it was delivered;
- results delivered per input item you listed (a range);
- output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
- how the run was started (console, API, schedule, webhook, another Actor);
- how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
- if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
- a short code made from the names of the input fields you set, never their values.
Repeat-run fingerprint (v2)
When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.