π Feature description
TikTok Direct Post API requires a very strict UX flow that is currently not implemented in Postiz.
At the moment, Postiz uses a generic post composer that does not comply with TikTok Content Posting Guidelines.
Missing key elements include:
- Creator info display (nickname, posting limits, constraints)
- Dynamic privacy selection from TikTok API
- Interaction toggles (Comment, Duet, Stitch)
- Commercial content disclosure (Your Brand / Branded Content)
- Required consent declaration before publishing
- Preview and explicit user confirmation
- Publishing status tracking
Because of this, applications for TikTok Direct Post API are rejected during audit.
π€ Why is this feature needed ?
This feature is required to successfully pass TikTok's Content Posting API audit.
In my use case, I tried to enable TikTok Direct Post through Postiz, but the application was rejected with the reason:
"Your application did not follow our UX Guidelines"
TikTok explicitly requires a structured UX flow where users:
- clearly see which account they are posting to
- manually select privacy and interaction settings
- explicitly consent before publishing
- have full control and awareness of the content
Without implementing this UX:
- TikTok integration cannot be approved
- Direct posting to TikTok is effectively unusable in production
This is not just a UX improvement, but a blocking requirement for the integration to work.
βοΈ How do you aim to achieve this?
I suggest introducing a dedicated TikTok posting flow instead of using the generic composer.
The flow could be:
- Fetch creator_info from TikTok API
- Render dynamic UI based on response:
- show creator nickname
- load privacy options (no default selection)
- enable/disable interaction toggles
- Add commercial content section:
- toggle ON/OFF
- "Your Brand" / "Branded Content" selection
- validation rules
- Add consent declaration (dynamic based on content type)
- Show preview before publishing
- Require explicit user confirmation before upload
- Track publishing status via polling or webhook
This could be implemented as:
- a provider-specific UI for TikTok
- or an extensible system for platform-specific constraints
ποΈ Additional Information
I tried applying for TikTok Direct Post API using the current Postiz implementation, but the audit failed.
TikTok guideline reference:
https://developers.tiktok.com/doc/content-sharing-guidelines#required_ux_implementation_in_your_app
The issue is not related to API usage itself, but strictly to missing UX requirements.
This means that even with correct backend integration, approval will always fail without these UI changes.
I believe this is a critical gap for anyone trying to use TikTok with Postiz.
π Have you spent some time to check if this feature request has been raised before?
Are you willing to submit PR?
None
π Feature description
TikTok Direct Post API requires a very strict UX flow that is currently not implemented in Postiz.
At the moment, Postiz uses a generic post composer that does not comply with TikTok Content Posting Guidelines.
Missing key elements include:
Because of this, applications for TikTok Direct Post API are rejected during audit.
π€ Why is this feature needed ?
This feature is required to successfully pass TikTok's Content Posting API audit.
In my use case, I tried to enable TikTok Direct Post through Postiz, but the application was rejected with the reason:
"Your application did not follow our UX Guidelines"
TikTok explicitly requires a structured UX flow where users:
Without implementing this UX:
This is not just a UX improvement, but a blocking requirement for the integration to work.
βοΈ How do you aim to achieve this?
I suggest introducing a dedicated TikTok posting flow instead of using the generic composer.
The flow could be:
This could be implemented as:
ποΈ Additional Information
I tried applying for TikTok Direct Post API using the current Postiz implementation, but the audit failed.
TikTok guideline reference:
https://developers.tiktok.com/doc/content-sharing-guidelines#required_ux_implementation_in_your_app
The issue is not related to API usage itself, but strictly to missing UX requirements.
This means that even with correct backend integration, approval will always fail without these UI changes.
I believe this is a critical gap for anyone trying to use TikTok with Postiz.
π Have you spent some time to check if this feature request has been raised before?
Are you willing to submit PR?
None