reference creatortrack tiktok app setup 20260715T155812

TikTok for Developers portal reorganized: there is no longer a separate "Display API" product to add, its scopes are now granted directly once Login Kit is added.

  • App: name CreatorTrack, platform Web only (https://creatortrack.ai), ToS https://creatortrack.ai/terms, Privacy https://creatortrack.ai/privacy.
  • Product: Login Kit only (OAuth door).
  • Scopes required (must match lib/social/oauth.ts ~line 197): user.info.basic (bundled automatically with Login Kit), user.info.profile, user.info.stats, video.list.
  • Deliberately skipped: Content Posting API / posting scopes (CreatorTrack is read-only/draft-only by doctrine; posting scopes trigger TikTok's heavy manual audit).
  • Login Kit redirect URI: https://app.creatortrack.ai/api/social/connect/callback.
  • Sandbox: add the Gus the Bass TikTok account as a Target User so it can authorize before TikTok's production review completes.
  • Credentials land in ~/.forge-secrets/creatortrack-social.env as TIKTOK_CLIENT_KEY / TIKTOK_CLIENT_SECRET; once that file exists the Connect TikTok button goes live and TikTok becomes platform three in the [[creatortrack_social_meta_ingest]] pipeline.

Why: the portal UI no longer shows a "Display API" product, which could confuse a future session re-doing or debugging this setup; the exact scope/redirect-URI values are load-bearing and easy to get wrong. How to apply: reference before revisiting TikTok app config, debugging OAuth scope/redirect errors, or verifying the Connect TikTok flow.

[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.65, mode staged]