Publishing API
YouTube publishing API with one SocialClaw workspace.
Start the YouTube OAuth flow from SocialClaw, then store the connected channel in the same workspace used by the CLI and API. SocialClaw supports channel video uploads with privacy settings and follow-up inspection.
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.
- YouTube channel stored in the SocialClaw workspace
- YouTube requires one video per post.
- Provider-specific settings such as privacyStatus, notifySubscribers, madeForKids
- 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 YouTube
Start the YouTube OAuth flow from SocialClaw, then store the connected channel in the same workspace used by the CLI and API.
Inspect account capabilities and settings
Read the current settings surface, including privacyStatus, notifySubscribers, madeForKids, before generating the final payload.
Validate before apply
Validation should happen before create-run or apply. YouTube requires one video per post.
Inspect the resulting run or post
Reconciliation currently supports YouTube video lookup. Analytics snapshots are available, but YouTube provider-native analytics fetchers are not implemented yet.
CLI and HTTP examples
Example commands and requests for this route.
CLI flow
YouTube publishing API
socialclaw login --api-key <workspace-key> --base-url https://getsocialclaw.com
socialclaw accounts connect --provider youtube --open
socialclaw accounts capabilities --provider youtube --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
HTTP API flow
Hosted SocialClaw endpoints
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":"youtube"}' \
"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.
- Community posts, Shorts-specific workflows, playlists, and live-stream flows are not supported.
- YouTube currently supports one video asset per post.
- Non-post interaction steps are not implemented.
Related routes
Related integrations and use cases.
Frequently asked questions
What account type does the YouTube publishing API route use?
YouTube uses the YouTube channel route in SocialClaw. Start the YouTube OAuth flow from SocialClaw, then store the connected channel in the same workspace used by the CLI and API.
What media rules apply to the YouTube publishing API route?
YouTube requires one video per post. SocialClaw uploads the video to YouTube during publish.
What should the workflow inspect before applying YouTube posts?
Inspect settings such as privacyStatus, notifySubscribers, madeForKids and capabilities. Community posts, Shorts-specific workflows, playlists, and live-stream flows are not supported.
Run the YouTube publishing API workflow in SocialClaw
Connect the account once, validate before publish, and keep everything in one workspace.