
TikTok Scraper
Pricing
Pay per event

TikTok Scraper
Extract data from TikTok videos, hashtags, and users. Use URLs or search queries to scrape TikTok profiles, hashtags, posts, URLs, shares, followers, hearts, names, video, and music-related data. Export scraped data, run the scraper via API, schedule and monitor runs or integrate with other tools.
4.4 (23)
Pricing
Pay per event
461
Total users
44K
Monthly users
10K
Runs succeeded
98%
Issues response
1.4 days
Last modified
42 minutes ago
Some TikTok videos has video URLs but can't download
Closed
I looked into the run that created that key-value store, and the video URLs of the first 378 results work, but everything after doesn't. What I found is that the URLs are generated before the video is actually downloaded, so if there is something wrong with downloading I will have an URL without the actual video. such as https://api.apify.com/v2/key-value-stores/ci8eK3V07d8HM5WUM/records/video-tacobellqw-20250604013149-7511900725190921515 and https://api.apify.com/v2/key-value-stores/ci8eK3V07d8HM5WUM/records/video-dreamweave-20250604022705-7511915018024242462 and https://api.apify.com/v2/key-value-stores/ci8eK3V07d8HM5WUM/records/video-chrisjonez-20250604023921-7511918198095138078.

Hi, thanks for opening this issue!
It looks like the requests have all started to get blocked after some time all at once. Perhaps it was some temporary outage on TT or increased blocking. You are right with the URL generation for the videos, that could also be the cause of why we are being blocked, maybe they are reset after some specific time?
We will investigate and fix this. In the meantime, please rely on running the scraper in smaller batches, which will still be extracted fine :)
I will keep you updated here, thanks!
openinterx
I would like to know the recommended maximum length for field "Videos with this hashtag","Number of videos per hashtag", "profile or search","Usernames","Search queries","Video URLs".

I would generally say like a 1000, but only with 1 start URL per run. And just run multiple smaller independent runs :)
Anyway, we've released a fix for this now, which should make sure it doesn't crash again. But we will first need to properly test it, before closing this issue and considering it done :)

Hi again, we've tested it again and are happy to say it is fixed indeed. If anything else comes up, please let us know again, we appreciate the feedback!