Self-hosted TikTok publishing: what can actually go live?

If your scheduler works but TikTok rejected the app for internal use, check eligibility before spending another week changing the upload code.

Checked against the platform's official documentation on 2026-10-30. These rules change; confirm against the docs before relying on them.

Three checks before public publishing

1. App eligibility. TikTok requires Direct Post clients to serve a wide audience. Utilities limited to accounts you or your team manages are excluded by its Intended Use rules.
2. Creator authorization. The destination account must authorize the app with video.publish. A successful OAuth callback confirms a connection, not audit approval.
3. Direct Post audit. An unaudited client is restricted to SELF_ONLY, private creator accounts and five posting users per 24 hours. Public posting requires the audit.

These requirements come from TikTok’s Content Sharing Guidelines and Direct Post setup guide. A scheduler’s support for a TikTok provider does not establish your developer app’s eligibility or audit status.

Choose a route that fits your use case

Keeping your workflow self-hosted

You can keep n8n, your prompts and video generation on your own infrastructure, then send the finished media to a hosted publishing API. The publisher operates its own TikTok app and token lifecycle. Connecting to it does not grant approval to your developer app.

QPost supports this route through REST and MCP. Its TikTok app is audited. You connect your own TikTok account and use a QPost API key from your workflow. The file passes through QPost’s media hosting; publication still depends on the account’s available privacy settings, TikTok’s limits and content review.

Check a draft before enabling automation

1. Connect one destination account and create a QPost API key.
2. Send a video with draft=true. Verify the stored video, caption and destination before publishing.
3. Configure the required privacy, commercial and AI-content disclosures for the actual post.
4. After publication, check per-platform status until it reaches PUBLISHED or a reported failure. An accepted request can still be processing.

For the exact private-post error and audit checklist, see why TikTok API uploads are private. For API fields, see the QPost reference.