TikTok Data Extractor avatar
TikTok Data Extractor

Pricing

from $2.00 / 1,000 results

Go to Store
TikTok Data Extractor

TikTok Data Extractor

Developed by

Clockworks

Clockworks

Maintained by Apify

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

553

Total users

28K

Monthly users

1.9K

Runs succeeded

>99%

Issues response

2.5 days

Last modified

a day 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

RU

Clarification Regarding CreateTime Field

Closed

robbie_uma opened this issue
25 days ago

I ran the TikTok Data Extractor on an account that had just posted a video, and I noticed that the createTime field exactly matches my local timezone. I’m trying to understand why this is happening.

Is the createTime returned in UTC and then automatically converted to my local timezone—either by Apify or the scraper detecting my timezone? Or is it possible that the timestamp reflects the account’s timezone instead?

Ultimately, I want to confirm whether the createTime value is consistent and reliable across different accounts, so I can always accurately determine when a video was posted, regardless of the timezone or location of the account being scraped

svpetrenko avatar

Hi, thanks for asking! I believe you refer to "create time" in the beautified table output - this one will convert timestamps to your local timezone. You can still access raw scraper data, e.g. by switching to the "JSON" view. There you will see createTimeISO - an ISO date, with a timezone portion at the end (that timezone should be UTC)

Let me know if you'd like to clarify something more by reopening this issue