Skip to main content

Introduction

TikTok Public pulls publicly visible creator-account data — profile statistics and per-video performance — for TikTok handles the customer designates as monitoring targets. The customer supplies no TikTok credential; the connection runs through a platform-managed proxy that aggregates public TikTok data. The connector is intended for competitive monitoring, influencer analytics, and brand-mention tracking on TikTok creators the customer does not own. Because TikTok’s official API does not permit monitoring accounts the customer does not control, this connector uses a platform-managed public-data proxy for that use case. As a public-data connector, engagement metrics and audience breakdowns are standardized so widgets can aggregate alongside owned-account sources without additional configuration. To connect this data source, see How to connect TikTok Public to Adriel.

Data refresh strategy

Architecture data

The list of monitored TikTok handles is configured per data source by the customer. Multiple handles can be tracked per data source, and the handle is the unit of monitoring — per-video metrics are fetched for the videos that resolve under each tracked handle. Changes to the monitored handle list take effect on the next scheduled refresh.

Reports data

This connector follows a simple-cache pattern: every day, for each collection, data is refetched and the cache is overwritten. The default refresh runs once daily at 5:00 PM (UTC). Public TikTok data is exposed as snapshot-style counts — followers, total likes, video counts — rather than a historical daily time series, so cached values accumulate from the day the monitored handle is first added. A manual cache refresh is also available, limited to once per calendar day.

Architecture levels

Creator (handle) → Video

Metrics

How to read the columns Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like stats.playCount is the literal platform field name. Italic text describes how a value is produced when it doesn’t map cleanly to a single API field.

Video performance

Video metadata

Creator statistics

Creator metadata

Breakdowns

Video

Creator

Limitations

  • 90 videos per handle — Adriel caps fetching at the 90 most recent public videos per handle per refresh cycle. Metrics are available for those videos only.
  • Snapshot semantics, not a time series — public counts (followers, total likes, video count) are captured at refresh time and stored as daily snapshots. Historical values for periods before the monitored handle was added are not available.
  • Username changes require recreation — if a monitored creator changes their TikTok handle, any data source linked to the old handle must be recreated.
  • Private or deleted accounts stop updating — if a monitored creator switches the account to private or deletes it, new data stops arriving. Data already in the cache remains queryable until the situation changes.
  • Shared, aggregate usage cap — the third-party proxy subscription has aggregate limits that span all customers using the connector. Heavy concurrent load may surface as throttling or temporarily stale data; contact support if throttling is suspected.
  • Narrower than TikTok Organic — public scraping exposes only the metrics TikTok shows on the public web. There is no access to audience demographics, traffic sources, or impression breakdowns that a creator’s own analytics surface.

API references

  • The connector reads public TikTok data through a platform-managed RapidAPI proxy (host tiktok-api23.p.rapidapi.com, base URL https://tiktok-api23.p.rapidapi.com/api/). The RapidAPI subscription is managed by Adriel; the customer never supplies a TikTok credential.
  • RapidAPI — the gateway through which public TikTok data is aggregated.

See also