TikTok Profile Videos Scraper API — Public Videos & Stats

TikTok Profile Videos Scraper exports available public creator videos with captions, engagement counters, publish times, hashtags, music, covers and author metadata. Use it for creator research or campaign reporting, not standalone profiles or follower lists.

No full-history guarantee: maxVideos: 0 removes the requested per-creator count bound, but collection remains subject to source visibility, page caps, timeouts, run budgets and the Free-plan preview. Private, deleted, unavailable and missing-play-count posts are not returned.

Free-plan preview: At most the first 50 normalized creator inputs, a per-creator request cap of 50 (including maxVideos: 0), and 50 saved rows total. This developer restriction does not apply to paid plans; input, page, runtime and budget limits still do.

Quick start

Illustrative input; these creators are not asserted to return data at run time:

{
  "creators": [
    "mrbeast",
    "@khaby.lame",
    "https://www.tiktok.com/@zachking"
  ],
  "maxVideos": 10,
  "dataSource": "auto",
  "maxConcurrency": 2,
  "maxRequestRetries": 2,
  "requestTimeoutSecs": 45
}

Supply a non-empty array of usernames, @handles or profile URLs; empty entries are ignored. No search, hashtag, direct-video-input or media-download mode is implemented. Export the dataset as JSON, CSV or Excel.

No TikTok login, user cookies or user-supplied TikWM key is required. Apify account/API authentication is still required. TikWM is an independent provider, not a first-party accuracy guarantee.

Input fields

Field	Default	Actual behavior
creators	required	Non-empty array of handles/profile URLs; each target is normalized to a creator URL. Avoid repeats and alternative forms of the same creator.
maxVideos	0	Maximum per creator, integer minimum 0, no schema maximum. 0 requests beyond a finite count target, not unlimited guaranteed output.
dataSource	auto	auto, tikwm or browser.
maxConcurrency	2	1–8 creators/pages in parallel. HTTP starts also have a run-wide pacing gate.
maxRequestRetries	2	0–5 browser retries; HTTP uses this value capped at three retries after the initial request.
requestTimeoutSecs	45	10–180 seconds for browser navigation. HTTP attempts have a fixed 30-second timeout. Browser handler timeout is 240 seconds.
proxyConfiguration	Apify DEFAULT	Browser-only non-residential pool. useApifyProxy: false disables it; residential groups/custom URLs are ignored.

Extraction modes

• auto: TikWM HTTP first. Successful creator results are written; failed creators receive browser recovery.
• tikwm: HTTP only, with no browser or proxy. If any creator fails, the run fails even if another creator already produced saved rows.
• browser: TikTok public-page browser extraction, including embedded data, captured list responses, signed pagination and bounded scroll recovery.

Browser recovery uses direct egress or Apify DEFAULT, ignoring residential/custom settings. Proxy setup failure continues with direct egress. Access blocks and regional restrictions can still prevent results.

Output and numeric semantics

One saved row represents a qualifying public video with an ID and numeric playCount. Available fields include:

Fields	Interpretation
id, url, text	Video ID, canonical video URL and caption.
createTime, createTimeUnix	Source publish time as UTC ISO text and Unix seconds. Missing values can be omitted.
durationSeconds, width, height	Source media duration in seconds and dimensions, when available.
cover, dynamicCover	Source thumbnail URLs; availability and longevity are not guaranteed. No files are downloaded.
playCount, diggCount, commentCount, shareCount, collectCount	Source-provided plays, likes, comments, shares and saves. Other counters can be omitted when absent/unparseable.
hashtags, music	Caption/source hashtags and optional music ID, title, author and original-sound flag.
isPinned	Source pin flag; missing pin information defaults to false.
authorUsername, authorNickname, authorId, authorVerified	Available author metadata, not verified ownership or a complete creator profile.

Counters are converted source values, not audited totals; browser counters may be rounded. No row-level precision/source label exists. Missing play counts skip the post; explicit source zero is allowed. Other null/non-finite fields are omitted.

Video-ID deduplication is per creator, not run-wide: repeated HTTP creator inputs can save and charge duplicate rows. Sorting covers only the captured subset, not complete/latest history. There is no collection timestamp per row; retain the run time and mode for comparisons.

Current pricing and billing

Current effective event prices in USD:

Apify plan	Per saved video row	Per 1,000 rows
FREE	$0.00250	$2.50
BRONZE, SILVER, GOLD, PLATINUM, DIAMOND	$0.00050	$0.50

The FREE plan is not a zero-priced event tier. Saved rows use apify-default-dataset-item; there is no custom per-profile charge in the implementation. Empty creators and skipped missing-play-count videos do not create placeholder result rows. Saved partial results remain billable when a later target or run fails.

apify-actor-start costs $0.00005 per GB of allocated memory, minimum one event per run. The current default allocation is 1,024 MB; higher memory can need more startup events. Startup can apply even without results. Apify platform usage is billed separately to the running user, including compute, storage, transfer and applicable non-residential proxy usage. Retries, browser recovery and empty/failed runs still consume resources. Event prices are not all-inclusive totals. Check the Pricing tab for your plan.

No downstream Apify Actor or separate request/custom event is configured; HTTP scans and browser recovery still consume platform usage.

Reliability and limits

• HTTP: up to 35 posts/page, 300 pages/creator, with 1.1-second request-start pacing. Empty/stalled feeds or provider limits can stop it earlier.
• Browser: 300 signed iterations, stated profile-count targets and a 240-second handler timeout. Zero-capture scroll recovery is capped at 80 iterations. Partial capture does not prove completeness.
• maxVideos is per creator. Browser candidates are trimmed before missing-play-count rejection, so delivered rows can be below target. Plan/budget limits can reduce them further.
• No usable creator or zero qualifying rows fails the run. tikwm also fails on any failed creator; auto/browser can succeed with partial data. Inspect logs. At output limits, pre-truncation counts can exceed actual saved rows.
• Deleted/private/empty accounts, access blocks and regional restrictions may produce no results. Zero results do not independently establish why content is unavailable. No private-content or access-control bypass is supported.

FAQs

Can I export full history? No completeness guarantee is made. maxVideos: 0 requests available source pagination within finite page, runtime, budget and plan limits.

Does it download MP4 files or return full profile statistics? No. The output is video metadata with available author fields and cover links, not media storage or a complete profile-statistics row.

Are engagement counters exact? They are third-party-source/web values. Browser counters may be rounded, optional counters may be missing, and the output has no precision label.

Related Actors from funny_ground

• TikTok Scraper — mixed profiles, tags, searches and direct URLs, with optional media downloads.
• TikTok Comments Scraper — public comments and first-level replies for known videos.
• TikTok Hashtag Stats — aggregate hashtag lookup rows rather than creator videos.

Collect and use public data in accordance with applicable laws and platform terms.