SocialClaw
Audience workflow

Use SocialClaw as a YouTube scheduler inside developer tooling.

SocialClaw fits developer tooling that needs hosted YouTube uploads, workspace API key auth, validation, apply, and inspectable publishing state without rebuilding channel auth and upload orchestration.

Account type YouTube channel One video upload per post
Best fit Developer tools YouTube community posts, Shorts-specific flows, playlists, and live-stream flows are not supported.

What SocialClaw supports for this workflow

A quick overview of what this workflow supports.

Dev-tool fit CLI and HTTP both work Developer tooling can use the CLI or call the hosted API directly with the same workspace key.
Media rule One video per post The current YouTube route uses one video asset and native video upload.
Settings privacyStatus, notifySubscribers, madeForKids The route keeps current YouTube upload settings visible before apply.
Inspection Run and post inspection Developer tools can inspect the resulting run or post state after apply.

What the payload needs

The main fields and constraints to account for.

  • Workspace API key auth
  • Connected YouTube channel
  • One public or SocialClaw-hosted video URL
  • Optional upload settings such as privacyStatus and madeForKids

How the workflow runs

Connect the account, validate the post, then publish.

Step 1

Authenticate the tooling with the workspace key

Use the workspace API key with either the CLI or HTTP API so the developer tool talks to the hosted SocialClaw service.

Step 2

Connect the YouTube channel and upload the video

Store the channel in the workspace, then upload the video or point at a public video URL.

Step 3

Validate before creating work

Validation confirms the one-video YouTube publish envelope and the current settings before apply.

Step 4

Apply and inspect the result

Create the scheduled YouTube upload and inspect the resulting run or post state after publish.

CLI and HTTP examples

Example commands and requests for this route.

CLI flow YouTube scheduler for dev tools
socialclaw login --api-key <workspace-key>
socialclaw accounts connect --provider youtube --open
socialclaw assets upload --file ./video.mp4 --json
socialclaw validate -f youtube-tooling-schedule.json --json
socialclaw apply -f youtube-tooling-schedule.json --idempotency-key yt_tool_1 --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.

  • YouTube community posts, Shorts-specific flows, playlists, and live-stream flows are not supported.
  • One video asset is required per post.
  • Non-post interaction steps are not implemented.

Related routes

Related integrations and use cases.

Frequently asked questions

Why does the YouTube route fit developer tools?

It exposes a hosted API and CLI for channel connection, asset upload, validation, apply, and inspection without requiring the tool to own upload orchestration.

What media rule applies to the YouTube route?

The route requires one video asset per post.

Which YouTube workflows are still unsupported?

Community posts, Shorts-specific flows, playlists, and live-stream flows are not supported.

Run the YouTube scheduler for dev tools workflow in SocialClaw

Connect the account once, validate before publish, and keep everything in one workspace.