TikTok White-label Setup
TikTok usually takes more operational prep than LinkedIn, so this guide focuses on the shortest reliable path: get one app, one callback, and one creator account connected before you think about scale.
Fastest route to a first success: create the app in TikTok for Developers, add the callback URL shown on this page, paste the credentials into UniPost, then connect one real test account before you expand scope or review work.
At a glance
| Question | Answer |
|---|---|
| Create the app in | TikTok for Developers |
| UniPost credential card | TikTok |
| Client fields to copy | Client Key + Client Secret |
| Best for | Products that need customer TikTok connections and are ready for a more compliance-heavy setup than LinkedIn. |
| App review / approval | Expect more scrutiny than LinkedIn. Build time for audit / review into the rollout plan, not after engineering is done. |
Before you start
- A company-owned TikTok developer account.
- A creator account you can use for repeatable integration tests.
- A clear internal owner for TikTok review and policy follow-up.
- A rollout plan that starts with internal or pilot traffic before broad public launch.
Callback URLs to whitelist
Copy these exactly into the platform developer console. Redirect mismatches are the fastest way to burn time during setup.
https://api.unipost.dev/v1/oauth/callback/tiktokFirst working setup
1
Create the TikTok app with production ownership in mind
Do not build your rollout around a personal side account. TikTok setup tends to involve review follow-up, so start from the company-owned developer identity you expect to keep long term.
2
Add UniPost's TikTok callback before anything else
TikTok callback mismatches are an easy source of false negatives. Whitelist the exact callback URL first so every later test is measuring the real integration, not a routing typo.
3
Store the Client Key and Client Secret in UniPost
TikTok labels the public identifier as Client Key. In UniPost, paste that into the TikTok credential card along with the Client Secret, then save the pair before you attempt any user-facing tests.
4
Run one creator-account smoke test
Do one complete connect with a controlled creator account and verify that the consent surface shows your app. Resist the urge to broaden rollout before this single path is stable.
5
Prepare for review, not just for code-complete
Once the technical path works, line up screenshots, product descriptions, and ownership details so review work does not stall the launch after engineering signs off.
What to paste into UniPost
| TikTok app field | UniPost field | Notes |
|---|---|---|
| Client Key | Client Key | TikTok uses Client Key where many platforms say Client ID. |
| Client Secret | Client Secret | Save once in UniPost and rotate through your internal secrets process when needed. |
| Redirect URI allowlist | Callback URL below | Add before testing, not after the first failure. |
Save the credentials first, then start a fresh connection attempt. Troubleshooting an OAuth flow against stale credentials usually creates false leads.
Connect a TikTok account through your app
After your TikTok app credentials are saved, prove the customer-facing flow your own app will use: create an API key, choose the branded profile, create a Connect session, send the returned OAuth URL to your end user, then confirm UniPost recorded the managed TikTok creator account.
1
Step 1: create your first API key in the dashboard
Open UniPost in the same workspace where you saved the TikTok credentials, create an API key, and store it immediately. The first key must be created in the dashboard because there is no API key available yet to call POST/v1/api-keys.
2
Step 2: list profiles and copy the `profile_id` you will use for branding
Every workspace gets at least one profile. Start by listing profiles so you can grab the
id for the profile that should own your hosted Connect branding.3
Step 3: patch the profile branding that should show on hosted Connect
With the
profile_id in hand, update the logo, display name, and primary color. This is the fastest way to confirm your hosted Connect surface is reading your own branding instead of UniPost defaults.4
Step 4: create a TikTok Connect session for your app user
From your backend, create a Connect session with
platform set to tiktok, the branded profile_id, and your stable external_user_id. UniPost returns a hosted OAuth URL. Redirect your app user to that URL, or open it inside the connection flow in your own product, so they can authorize their TikTok creator account under your white-label app.5
Step 5: confirm the managed TikTok account is visible through the API
After the user completes OAuth, UniPost stores the connected TikTok creator account as a managed account tied to your
external_user_id. Verify it through the accounts API; the same user should also appear in the dashboard's Developer App Users view. Use the controlled creator account from your smoke test so account-type issues are easy to separate from API wiring issues.6
Step 6: use that managed account and profile in your first real API workflow
At this point you have the four values you need most often:
API_KEY, profile_id, external_user_id, and the connected TikTok account_id. From here, run a small end-to-end publish test so you know the white-label TikTok connection is usable, not just visible.Common blockers
| Blocker | What to do about it |
|---|---|
| Creator-account assumptions | Use a real creator account early so you discover any account-type issues while the setup surface is still small. |
| Review is part of the project | Treat TikTok review as part of the rollout timeline, not a post-launch admin chore. |
| Naming mismatch | TikTok says Client Key; UniPost mirrors that label in the dashboard so teammates do not paste the wrong field. |
Definition of done
- TikTok shows your app during consent.
- The callback returns successfully to UniPost.
- A test creator account is connected in the workspace.
- Your team has named an owner for TikTok review and ongoing credential maintenance.