Reference tiktok oauth consent required no system token

URL: https://mkdocs.justinsforge.com/memory/general/reference_tiktok_oauth_consent_required_no_system_token/

Learned 2026-07-15 while wiring up Gus's TikTok connection in CreatorTrack's social ingest pipeline. TikTok OAuth involves two distinct credentials that are easy to conflate: (1) app credentials (client key/secret), which only prove the app is registered and allowed to ask for given scopes, and (2) a user access token, created only when the account owner clicks "Authorize" on TikTok's real consent screen. Configuring scopes and validating app credentials does nothing on its own; a video.list/user.info.stats read still returns nothing until the Connect flow is manually completed by the target account.

Why: Meta (Instagram/Facebook) has a pre-authorized shortcut, a Business Manager system-user token, so once that token exists, no further human click is ever needed to read data. TikTok has no equivalent: even reading your own account's stats (not posting) requires the OAuth consent click, and this holds true even in Sandbox mode with your own account registered as the target user. Assuming TikTok would behave like Meta (token alone = access) caused confusion mid-session.

How to apply: when staging a new TikTok connection (per-brand or per-account), budget one manual "Connect" click per account regardless of whether it's a read-only ingest use case; don't expect app-credential setup alone to unlock data access, and don't schedule TikTok ingestion work assuming it can run headless like the Meta system-user pipeline does.

[Claude Code]