How to track a TikTok creator's videos and growth

The endpoint

Make the call

Put your key in FASTFETCHZ_KEY. The target below is a real one — it works as written.

curl "https://api.fastfetchz.com/v1/tiktok/videos-user-videos?target=khaby.lame" \
  -H "X-API-Key: $FASTFETCHZ_KEY"

What comes back

Trimmed to the fields that matter. The full payload carries more.

{
  "success": true,
  "service": { "platform": "TikTok", "name": "Videos / User Videos" },
  "credits_charged": 1,
  "data": {
    "videos": [
      {
        "aweme_id": "7381029384756102938",
        "desc": "no words needed",
        "create_time": 1782043200,
        "duration": 14,
        "statistics": {
          "play_count": 41283901,
          "digg_count": 5120384,
          "comment_count": 38271,
          "share_count": 210394,
          "collect_count": 91827
        },
        "music": { "title": "original sound", "author": "khaby.lame" },
        "share_url": "https://www.tiktok.com/@khaby.lame/video/7381029384756102938"
      }
    ],
    "has_more": true
  },
  "cursor": "1782043200000"
}

Getting more than one page

The video call returns 10 videos, a has_more flag and a cursor. Pass the cursor back for the next 10 and stop when has_more is false.

For ongoing tracking, do not re-walk the whole feed. Store aweme_id for everything you have seen, then pull page one on your schedule and stop as soon as you hit an ID you already have. A creator posting daily costs one call a day to stay current.

# Page 1 — 10 most recent videos
curl "https://api.fastfetchz.com/v1/tiktok/videos-user-videos?target=khaby.lame" \
  -H "X-API-Key: $FASTFETCHZ_KEY"
# -> { "data": { "videos": [ ... ], "has_more": true }, "cursor": "1782043200000" }

# Page 2
curl "https://api.fastfetchz.com/v1/tiktok/videos-user-videos?target=khaby.lame&cursor=1782043200000" \
  -H "X-API-Key: $FASTFETCHZ_KEY"

What it costs

Start with the profile call

Run the profile endpoint first. It is one call and one record: follower count, following count, total likes, video count, bio, verification and avatar. Those are the account-level numbers you put at the top of a creator card, and you need them before per-video numbers mean anything — 40 million views is a different story on a 200,000-follower account than on a 160-million-follower one.

curl "https://api.fastfetchz.com/v1/tiktok/profile?target=khaby.lame" \
  -H "X-API-Key: $FASTFETCHZ_KEY"
# -> follower_count, following_count, heart_count, video_count, signature

Growth is something you record, not something you fetch

There is no historical endpoint. Every call returns the numbers as they are right now, so a growth curve exists only if you store snapshots. Call the profile endpoint on a fixed schedule — daily is plenty for most creators, weekly for a large roster — write the counts with a timestamp, and derive the curve from your own rows.

Engagement rate is worth computing the same way: sum likes, comments and shares across the last 20 videos and divide by follower count. That single number filters a creator list faster than any follower threshold, and it is two calls per creator.

Be realistic about a large roster

Tracking is cheap per creator and expensive per thousand. A daily profile snapshot plus one video page is 2 calls a creator a day: 500 creators is 1,000 calls a day, about 30,000 a month. That is a real line item, so tier your roster — daily for the creators you are actively negotiating with, weekly for the watchlist.

Backfilling a prolific creator's entire feed is the expensive part, not the tracking. An account with 2,000 videos is 200 calls once. Do that backfill deliberately, and only for creators you have decided matter.

What you cannot get

Private accounts return nothing. You get no demographics — no age, gender or country breakdown of a creator's audience — because TikTok only shows that to the creator inside their own analytics. Anyone selling you audience demographics for an arbitrary handle is estimating it.

You also do not get deleted videos, drafts, or the view counts a video had last week. Public counts are current-state only.

Endpoints you will probably want next