Upload videos to YouTube on a schedule with your own title, description and visibility, from a script, a CI job or an AI agent. Connect the channel once with Google sign-in.
Base URL https://api.so-me.studio/v1 · Auth X-API-Key · socialMedia: YOUTUBE
Send one of these values as postType. Every post needs text, and photos or videos are attached by fileId from your media library.
VIDEO
One video file. YouTube treats a vertical video of up to 3 minutes as a Short, so there is no separate Shorts type.
Upload the media, then create the post. Leave out scheduledAt to publish right away.
POST /v1/media/presign-upload adds the file to your media library and returns a fileId and a presigned uploadUrl.
curl -X POST https://api.so-me.studio/v1/media/presign-upload \
-H "X-API-Key: $SOME_API_KEY" \
-H "Content-Type: application/json" \
-d '{"files":[{"filename":"build-time.mp4","mimetype":"video/mp4","size":209715200}]}'
# → [{ "fileId": "…", "uploadUrl": "https://…", "fileSrc": "…", "s3Key": "…" }]PUT the bytes to uploadUrl with exactly the Content-Type you declared. The URL is valid for one hour.
curl -X PUT "$UPLOAD_URL" \
-H "Content-Type: video/mp4" \
--upload-file ./build-time.mp4POST /v1/posts with the fileId. The response is the post with status SCHEDULED, and it publishes at scheduledAt through a queue that retries on failure.
curl -X POST https://api.so-me.studio/v1/posts \
-H "X-API-Key: $SOME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"socialMedia": "YOUTUBE",
"postType": "VIDEO",
"text": "How we cut our build time in half",
"fileIds": ["<fileId>"],
"scheduledAt": "2026-11-08T16:00:00Z",
"metaData": {
"title": "How we cut our build time in half",
"description": "Caching, parallel jobs and one surprising flag.",
"visibility": "public"
}
}'accountId is optional when the workspace has one YouTube account. Otherwise pass an id from GET /v1/accounts.
Files attached with fileIds are checked against the YouTube limits below before anything is queued. A file that breaks a rule returns 400 with a report per file.
The fields that change how a post is published on YouTube.
| Field | What it does |
|---|---|
| metaData.title | The video title. YouTube allows 100 characters, so longer titles are cut. Falls back to text. |
| metaData.description | The video description. Falls back to text. |
| metaData.visibility | private, unlisted or public (privacyStatus works as an alias). Set it explicitly: an invalid or conflicting value fails before anything is uploaded. |
| firstComment | A comment posted under the video once it is live, up to 10,000 characters. |
Social media studio checks each file against these limits before it publishes. They are our configured limits, not a promise from YouTube: GET /v1/media/rules returns the live table, and POST /v1/media/validate checks a file without posting it.
Post type VIDEO
Publishing is asynchronous. Subscribe to post.published and post.failed, or poll GET /v1/posts/:id until postStatus is POSTED or FAILED.
curl -X POST https://api.so-me.studio/v1/webhooks/subscriptions \
-H "X-API-Key: $SOME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/hooks/social",
"categories": ["post"],
"events": ["post.published", "post.failed"]
}'
# The response includes the secret that signs every delivery.POST /hooks/social
X-Webhook-Event: post.published
X-Webhook-Signature: <hex HMAC-SHA256 of the raw body>
{
"event": "post.published",
"category": "post",
"timestamp": "2026-11-03T15:00:07.412Z",
"data": { "postId": "…", "platform": "YOUTUBE" }
}Every delivery is signed with HMAC-SHA256 in X-Webhook-Signature. post.failed fires after the last retry; fix the cause and call POST /v1/posts/:id/retry. A first comment reports on its own with post.first_comment_posted or post.first_comment_failed.
The same API key drives an MCP server with 200+ tools and a CLI, so an agent can post to YouTube without hand-written HTTP calls.
Add the server to Claude, Cursor or any MCP client with your API key. OAuth works too. For YouTube, the agent calls these tools with the same fields as the REST request:
{
"mcpServers": {
"so-me-studio": {
"url": "https://api.so-me.studio/mcp",
"headers": { "X-API-Key": "sk_live_…" }
}
}
}Install it with npm i -g @social-media-scheduler/cli. It uploads local files for you and prints JSON, so a script or a CI job can schedule a YouTube post in one command.
so-me posts:create --platform YOUTUBE --post-type VIDEO \
-m ./build-time.mp4 \
-c "How we cut our build time in half" \
-s 2026-11-08T16:00:00Z \
--metadata '{"title":"How we cut our build time in half","visibility":"public"}'API, CLI and MCP access is included on every paid plan: Lite, Creator, Standard, Advanced and Lifetime. See plans and limits
Yes. Upload a vertical video of up to 3 minutes as postType VIDEO. YouTube classifies it as a Short; there is no separate Shorts setting.
Yes. Social media studio accepts YouTube videos up to 350 MB each, well below the YouTube limit. Compress long or high-bitrate videos before you upload them.
Yes. Set metaData.visibility to private or unlisted. The value must be private, unlisted or public.
No. You connect the YouTube account once in the Social media studio dashboard through the YouTube sign-in. Its tokens are stored encrypted and refreshed on our side, and your code only sends your Social media studio API key in the X-API-Key header.
No. It returns as soon as the post is queued. Publishing runs in a worker that retries on failure, so listen for post.published and post.failed, or poll GET /v1/posts/:id.
The REST API, the CLI and the MCP server are included on every paid plan: Lite, Creator, Standard, Advanced and Lifetime. Lite, Creator, Standard and Advanced start with a 7-day trial (card required), and Lifetime is a one-time payment.
Stop juggling tabs, draft, customize, and publish to 20 platforms from a single calendar.