TikTok Data Scraper
Pricing
from $0.67 / 1,000 results
TikTok Data Scraper extracts public TikTok data at scale: profiles, videos, followers, comments and replies, hashtags, music, playlists and single-video details. Export to JSON, CSV or Excel, or use via API.
src/free_limits.py was the only one of this project's three TikTok actors missing the spec's dormant Option B (OWNER_TOKEN) branch entirely. Restored it exactly per .cursor/User-limlt.md §6.1, matching the sibling actors' structure: _open_quota_store() checks OWNER_TOKEN first and only falls back to Option A (the one that actually runs, unchanged) when it is unset — which is always, under the owner's current no-OWNER_TOKEN setup. Added apify-client to requirements.txt so Option B imports cleanly (it was previously omitted because nothing in the shipped code used it).limit_for() returns no numeric cap at all when any scrapeAll* toggle is on (scrapeAllUserResults, scrapeAllComments, scrapeAllReplies, scrapeAllHashtagVideos, scrapeAllMusicVideos, scrapeAllPlaylistVideos), and on a paid/unlimited run every affected category (videos, favourite_videos, following, the userUrls "search" category, comments/replies, hashtag/music/playlist videos) collected the ENTIRE category into memory before emitting a single row. Restructured every one of those call sites (plus paginate_item_list() itself, which already exposed an unused progress hook) to build + emit each page's records as soon as that page resolves; the numeric cap (or its absence) now only decides when to stop fetching more pages, never whether an already-fetched page is held back from the dataset. No cap value, pagination rule, or delivered row set/order changed.emit(): a push that returns a truthy ChargeResult but stores nothing (charged_count == 0, no event_charge_limit_reached flag — the real spend-limit signature on this platform) is now correctly treated as "nothing stored": it is not counted, the run stops cleanly, and a reserved free-plan quota unit for that entry is handed back instead of being silently spent on a row that was never written.src/log_style.py and wired the run's banner, input echo, plan line, free-limit notice and end-of-run summary through it instead of ad-hoc f-strings at those call sites..actor/input_schema.json to the project's closed input-emoji palette: removed the emoji from the schema's top-level title/description and from every categories enum title (none allowed there), and replaced every title/section-caption emoji that was outside the approved palette or on the explicitly banned variation-selector list (⏱️ ⚙️ 🛡️ 🌊 #️⃣ ↳ and others) with the matching palette emoji. Gave proxyConfiguration its own trailing collapsible section (🔒 Proxy configuration) per the proxy-field-UI rule; it previously inherited the "Advanced settings" section instead of having its own.user_playlists as a real, working category (removed as dead code in 0.2 because the old data source never implemented it; the new data source does).hdplay / hd_size (an HD no-watermark download link) — that was a value-add of the now-dead third-party mirror with no equivalent on TikTok's own guest surface. Not fabricated, not replaced — genuinely no longer obtainable.commerce_info, download_count and is_nff_or_nr are now null instead of a guessed default — none of the three are exposed by TikTok's logged-out web surface, and the previous placeholder values (defaulted booleans / 0) looked like real data but weren't.row_result (via push_data) and again under a separate result-item event. Only the single row_result charge per row remains.followers category now logs an honest, explicit warning when the underlying data source returns 0 results (previously a silent empty result with no explanation). following is unaffected.user_playlists category from the schema and code (it never called any endpoint).publishedAt (ISO-8601) and scrapedAt to every output record.videoUrl, profileUrl, hashtagUrl, musicUrl.hdplay), all 3 cover-image variants, the full music_info sound object, the commenter's bio/region/verified/follower-count snapshot, and the user_info profile's stats block + bio link + cross-platform handles (Instagram/Twitter/YouTube).exc_info=True) into the buyer-visible run log; replaced with neutral, non-leaking messages.user_playlists) and SEO.