Integration Walkthrough

TikTok OAuth + Upload API Walkthrough

This page shows live OAuth consent, connected account status, and a creator-controlled Upload API inbox flow so sound selection happens natively in TikTok.

OAuth Config JSON

Readiness

OAuth Config

Client Key-

Client Secret-

Redirect URI-

Default Scopes-

Backend Session Workers

Session Health Worker-

Browser Pool-

TikTok Accounts Found0

This page runs on the backend directly so your team can validate OAuth and uploads without opening the full Hive UI.

Step 1: Connect TikTok Account (OAuth)

Account label (optional) Existing TikTok account (optional update target) Proxy (optional)

Preferred path for TikTok Content Posting API. This captures OAuth tokens for Upload API usage.

OAuth Session

State-

Statusidle

Result-

Last Error-

{}

Step 2: Review Connected TikTok Accounts

ID	Username	Status	Proxy	OAuth Scope	Token Expiry	OpenID
No TikTok accounts loaded yet.

Step 3: Upload API Inbox Flow

TikTok account Local MP4 path on server machine (for demo recording) Optional caption/metadata generation mode

Recommended flow: use Upload API inbox and let creators finish the post in TikTok, including sound selection.

Fallback option: manual export renders final assets and a publish checklist so your team can post manually when needed.

Run Output

Last actionidle

Run dir-

TikTok post mode-

{}

Walkthrough Notes

Suggested demo sequence

Show this page URL and readiness panel (client key/secret + redirect URI configured).
Click Start TikTok OAuth, complete consent in popup, return to this page.
Show the newly connected TikTok account in the accounts table with scopes.
Run Upload to TikTok Inbox with a sample MP4 path.
Show successful upload result/status and explain final post + sound selection occurs in TikTok app.

Why this flow is production-friendly

Explicit user consent via TikTok OAuth (PKCE).
Uses official Content Posting Upload API scope (`video.upload`).
Creator retains final control in TikTok before publishing.
Matches the app domain/backend where the integration actually runs.

Rotate the client secret if it was ever exposed outside your local environment.