Authorization and creator info
Request the required access, then query the connected creator so the interface reflects current account capabilities and limits.
Required: account responseA creator-facing Direct Post requirements checklist
Direct Post is more than sending a file to an endpoint. The workflow must authorize the creator, query current account capabilities, display the returned privacy options, collect content and music disclosures, obtain informed consent, respect duration limits, and report the final platform status.
Evidence-led guidance · No view, monetization, or income guarantee
Quick answer
The TikTok Content Posting API Direct Post flow begins with authorization for the relevant scopes and a query for creator information. The response can determine the creator's nickname, available privacy levels, permitted interaction settings, and maximum video duration. A compliant interface should use those values rather than assume that every account can publish publicly or enable the same controls.
Before posting, the creator should see an editable title or caption, choose one of the privacy options TikTok returned, set the applicable interaction controls, and disclose whether the post promotes the creator or a third party. The workflow must also collect the music-rights confirmation and informed consent for Direct Post. Choices should not be silently preselected in a way that bypasses creator awareness.
For a recurring Series, configuration-stage confirmation can support later scheduled publishing when the product explains that behavior clearly and stores the relevant settings. At the release time, a completed render can publish automatically to the enabled TikTok account. The product should still expose scheduled, processing, published, or failed state and prevent duplicate submission.
Decision framework
Treat each group as a release condition. A connected account by itself is not enough.
Request the required access, then query the connected creator so the interface reflects current account capabilities and limits.
Required: account responseDisplay the privacy levels returned for that creator. Comments, Duet, and Stitch controls should follow the platform response rather than generic defaults.
Required: explicit choiceAsk whether the post promotes a brand, product, service, the creator, or a third party, and require confirmation that the user has rights to the music.
Required: accurate disclosureExplain the Direct Post action, collect informed consent, track the publish ID or result, surface failures, and avoid duplicate retries.
Required: visible outcomeReal completed example
The Hatton Garden Vault Breach is a finished vertical render suitable for a connected publishing workflow. Before this file can be sent through the TikTok Content Posting API, the creator-specific privacy, interaction, disclosure, rights, consent, schedule, and destination state must already be valid.
From decision to production
Create the Series first, then connect TikTok inside the same setup flow. FacelessReels keeps the creator choices, consent, saved schedule, generated video, submission state, and final platform result connected instead of treating the API as a separate technical project.
In practice
Public only when TikTok returns it for the account.
Creator or third-party promotion must be declared.
The user confirms rights to music in the video.
Scheduled Direct Post remains visible and traceable.
Operating workflow
The exact API implementation belongs in developer documentation. This sequence describes what the creator should experience.
Open the TikTok authorization flow, request the necessary permissions, and associate the returned creator identity with the user's account.
Fetch the current privacy options, interaction availability, creator identity, and maximum video duration before presenting publishing settings.
Let the creator edit post text, choose privacy, configure permitted interactions, and make the correct commercial-content disclosure.
Require music-rights confirmation and clear consent that the enabled Series will publish at its scheduled time.
Send the completed asset at the release window, record the platform response, show processing or failure, and retry safely when appropriate.
Deeper look · 01
The publishing interface should render the privacy-level options returned for the authorized creator. Some accounts may receive public publishing while others may only receive followers, mutual friends, or self-only choices. A third-party product should not fabricate a public option or rewrite a returned privacy value because the creator expected it.
Query creator information close enough to configuration or publication that the settings remain current. If a saved privacy choice is no longer available, stop the submission, explain the mismatch, and ask the creator to select from the current options. This is safer than silently downgrading or upgrading privacy.
Deeper look · 02
A Series can explain during setup that videos will be generated and automatically published at the selected recurring time. The creator chooses TikTok explicitly, reviews the account identity and post defaults, confirms rights and Direct Post behavior, and activates the destination. The resulting Connected Accounts toggle should remain enabled when the subscription creates the Series.
This does not remove platform-specific settings. Privacy, disclosure, interaction choices, duration, and other current requirements must remain valid. If a creator changes the Series to review mode, disables TikTok, or revokes access, later videos should not publish automatically.
Deeper look · 03
A successful API request may begin platform processing rather than prove the video is publicly available. Store the publish identifier, check the documented status flow, and show scheduled, submitted, processing, published, or failed states in the video workspace. The creator should not need to guess whether a missing post is still processing or needs attention.
Use idempotency and destination-level success checks before retrying. A network timeout can occur after TikTok accepted a request; blindly sending the same video again can create duplicates. The TikTok Content Posting API workflow should favor traceable recovery over repeated submissions.
Working table
This checklist is product-facing guidance, not a substitute for TikTok's current developer documentation and app review requirements.
| Requirement | Creator experience | Failure behavior |
|---|---|---|
| Creator information | Current account and capabilities are shown | Refresh before allowing incompatible settings |
| Privacy and interaction | Creator selects returned options | Do not invent or silently replace values |
| Disclosure, rights, consent | Explicit confirmations describe the post | Keep publishing disabled until complete |
| Status and retry | Submission state remains visible | Reconnect or retry without duplicate success |
Sources and current rules
Common questions
Yes. The interface should use the privacy options returned for the connected creator. Public publishing cannot be invented when TikTok does not return it.
Yes, when the product clearly explains scheduled Direct Post, the creator explicitly enables TikTok, and all current privacy, disclosure, rights, consent, duration, and connection requirements remain valid.
The Direct Post workflow should require the creator to confirm that they have rights to the music used in the video before publishing.
No. Connection authorizes access; the creator should explicitly enable the account as a destination for the Series.
No. The system should classify the failure, expose the status, refresh expired or incompatible settings, and use idempotency to prevent duplicate successful posts.
Connect the creator, use the capabilities TikTok returns, save accurate disclosures and consent, then track the final platform result.