TikTok Data Extractor
Pricing
from $2.00 / 1,000 results
TikTok Data Extractor
Extract data about videos, users, and channels based on hashtags or scrape full user profiles including posts, total likes, name, nickname, numbers of comments, shares, followers, following, and more.
4.8 (27)
Pricing
from $2.00 / 1,000 results
564
Total users
28K
Monthly users
1.8K
Runs succeeded
>99%
Issues response
1.9 days
Last modified
2 days ago
id | text | createDate | webVideoUrl | diggCount | shareCount | playCount | collectCount | commentCount |
|---|---|---|---|---|---|---|---|---|
743***45 | How to ***** scraping series! | 2024-11-10 | https://www.tiktok.com/@***/video/743***45 | 42 | 6 | 3182 | 41 | 3 |
744***21 | This is a must **** #leadgen #automations | 2024-12-17 | https://www.tiktok.com/@***/video/744***21 | 78 | 11 | 2434 | 118 | 0 |
747***58 | You need **** #scaleyourbusiness | 2025-02-19 | https://www.tiktok.com/@***/video/74***58 | 98 | 22 | 3883 | 109 | 1 |
The data above is synthetic and does not reflect real-world values. View full dataset
Actor is timing out since recent changes
Closed
The latest build seems to fix the internal Timeout error. However, now the crawling is taking a very long time or failing.
zognotadog
Hi will this be able to be fixed soon or do we need to migrate to a new scraper? This has not been working for 2 weeks.
Hi,
This timeout is not internal but rather set in the input of the actor run. You can find and increase it under Run options, as shown in the attached image.
zognotadog
Please can you re-open this issue. It was not related to my timeout. I am aware I have set a timeout. Is there another explanation as to why the scraper has jumped from executing in an average 10s to now over 2 minutes?
An 1100% unexplained increase in compute time should be an open issue.
Hi, thanks for specifying it, we'll investigate why it behaves like that and let you know what can be done.
Due to some changes on TikTok's side, profile scraping took extra time.
We recently updated the Actor and added a new field [EXPERIMENTAL!] Boost profile scraping in the input, which should make the Actor work at the same speed as before.
Hi again, I'm going to close the issue for now, as the problem has been fixed. The Actor should be working as swiftly as before. If anything else comes up, we'll be grateful for feedback!
