TikTok: why zero posts?

The handle or hashtag is private, empty, or does not exist. Private accounts expose nothing publicly. Hashtags with no recent posts return an empty feed rather than an error. Confirm the profile loads in a logged-out browser. If it does not render there, it is not collectable.

TikTok: why fewer posts than limit?

The feed ran out before the limit was reached. Short posting histories and aggressive pagination cutoffs on less active tags. Expected — you are charged per post returned. Widen the tag or collect several related tags if you need volume.

TikTok: why metrics null?

The metric was not exposed on the public view. Share and comment counts in particular are inconsistently rendered. Null means not exposed; zero means genuinely zero. Treat null and zero as distinct. Averaging them together silently understates engagement.

TikTok: why author fields empty?

The post was collected from a feed view that omits author details. Hashtag feeds carry less author metadata than profile feeds do. Collect by handle rather than by tag when author detail matters for your use.

Reference · TikTok

TikTok data errors

Post collection is the most volatile of the three sources, and nearly every gap traces back to account privacy or a hashtag with no recent activity.

Get API key All API error codes

4 entries · returned with HTTP 200 · not transport failures

TikTok results reflect what the public web view exposes at collection time. Private, removed, and region-restricted content is not reachable, and no parameter changes that.

Metric fields are typed as nullable on purpose — a null view count means the number was not exposed, which is different from zero views.

Collection

The pull returned less than expected, or nothing.

zero postsdata

The handle or hashtag is private, empty, or does not exist.

Cause: Private accounts expose nothing publicly. Hashtags with no recent posts return an empty feed rather than an error.
Fix: Confirm the profile loads in a logged-out browser. If it does not render there, it is not collectable.

fewer posts than limitdata

The feed ran out before the limit was reached.

Cause: Short posting histories and aggressive pagination cutoffs on less active tags.
Fix: Expected — you are charged per post returned. Widen the tag or collect several related tags if you need volume.

Field gaps

Posts came back and individual fields are empty or null.

metrics nulldata

The metric was not exposed on the public view.

Cause: Share and comment counts in particular are inconsistently rendered. Null means not exposed; zero means genuinely zero.
Fix: Treat null and zero as distinct. Averaging them together silently understates engagement.

author fields emptydata

The post was collected from a feed view that omits author details.

Cause: Hashtag feeds carry less author metadata than profile feeds do.
Fix: Collect by handle rather than by tag when author detail matters for your use.

Practices that prevent most of this

Null is not zero

Metric fields distinguish absent from empty deliberately. Collapsing the two produces engagement averages that are quietly wrong.

Check logged out

If content does not render for a signed-out browser, it is not publicly reachable and no collection will find it.

More references

API error codesEvery error code the SenseCollect API returns, what causes it, and how to fix it. Eight codes, their HTTP statuses, and the retry rules for each.Google Maps data errorsWhy a Google Maps pull returns fewer rows than expected, and why phone, email, or website comes back empty. Each cause with the parameter that fixes it.Amazon review data errorsWhy an Amazon review pull returns fewer reviews than the product shows, and why review dates or ratings come back empty. Causes and fixes.