TikTok publishing API with one SocialClaw workspace.
Connect the TikTok account through the SocialClaw OAuth flow, then keep the target available for future schedules through the same workspace API key. SocialClaw supports TikTok video posts through the explicit TikTok provider.
What SocialClaw supports for this workflow
A quick overview of what this workflow supports.
What the payload needs
The main fields and constraints to account for.
- TikTok user account stored in the SocialClaw workspace
- TikTok requires one video per post and does not support image-only TikTok posts in the current flow.
- Provider-specific settings such as privacyLevel, duetEnabled, commentEnabled, stitchEnabled
- Workspace API key auth and post or run inspection after apply
How the workflow runs
Connect the account, validate the post, then publish.
Authenticate the workspace
Use the workspace API key with the CLI or hosted HTTP API so the publishing workflow stays attached to the same customer workspace.
Connect TikTok
Connect the TikTok account through the SocialClaw OAuth flow, then keep the target available for future schedules through the same workspace API key.
Inspect account capabilities and settings
Read the current settings surface, including privacyLevel, duetEnabled, commentEnabled, stitchEnabled, before generating the final payload.
Validate before apply
Validation should happen before create-run or apply. TikTok requires one video per post and does not support image-only TikTok posts in the current flow.
Inspect the resulting run or post
TikTok reconciliation is not implemented yet. Analytics snapshots are available, but TikTok provider-native analytics fetchers are not implemented yet.
CLI and HTTP examples
Example commands and requests for this route.
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider tiktok --open
socialclaw accounts capabilities --provider tiktok --json
socialclaw validate -f schedule.json --json
socialclaw apply -f schedule.json --idempotency-key launch_1 --json
socialclaw runs inspect --run-id <run-id> --json
curl -sS \
-H "Authorization: Bearer $SC_API_KEY" \
"https://getsocialclaw.com/v1/keys/validate"
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"tiktok"}' \
"https://getsocialclaw.com/v1/connections/start"
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d @schedule.json \
"https://getsocialclaw.com/v1/posts/validate"
curl -sS \
-X POST \
-H "Authorization: Bearer $SC_API_KEY" \
-H "Content-Type: application/json" \
-d @schedule.json \
"https://getsocialclaw.com/v1/posts/apply"
Current limitations
A few practical limits to keep in mind.
- TikTok video is the only supported media type in the current SocialClaw flow.
- Posts require a public video URL or SocialClaw-hosted video URL.
- Non-post interaction steps are not implemented.
Related routes
Related integrations and use cases.
Frequently asked questions
What account type does the TikTok publishing API route use?
TikTok uses the TikTok user account route in SocialClaw. Connect the TikTok account through the SocialClaw OAuth flow, then keep the target available for future schedules through the same workspace API key.
What media rules apply to the TikTok publishing API route?
TikTok requires one video per post and does not support image-only TikTok posts in the current flow. TikTok pulls a public video URL, including a SocialClaw-hosted video URL.
What should the workflow inspect before applying TikTok posts?
Inspect settings such as privacyLevel, duetEnabled, commentEnabled, stitchEnabled and capabilities. TikTok video is the only supported media type in the current SocialClaw flow.
Connect the account once, validate before publish, and keep everything in one workspace.