Schedule Threads posts from your code or AI agent: text, photos, video, carousels of up to 20 images, and multi-post chains that publish as replies.
Base URL https://api.so-me.studio/v1 · Auth X-API-Key · socialMedia: THREADS
Send one of these values as postType. Every post needs text, and photos or videos are attached by fileId from your media library.
TEXT
A text-only post.
IMAGE
One image.
VIDEO
One video, up to 5 minutes.
CAROUSEL
2 to 20 images in one post.
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":"roadmap.jpg","mimetype":"image/jpeg","size":1048576}]}'
# → [{ "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: image/jpeg" \
--upload-file ./roadmap.jpgPOST /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": "THREADS",
"postType": "IMAGE",
"text": "Our Q4 roadmap in one picture. Details below.",
"fileIds": ["<fileId>"],
"threadParts": [
{ "text": "October: faster exports and a new calendar view." },
{ "text": "November: team approvals on mobile." }
],
"scheduledAt": "2026-11-09T12:00:00Z"
}'accountId is optional when the workspace has one Threads account. Otherwise pass an id from GET /v1/accounts.
Files attached with fileIds are checked against the Threads 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 Threads.
| Field | What it does |
|---|---|
| threadParts | The posts that follow, published as a reply chain under the first one. Up to 24 parts of 500 characters, each with up to 20 fileIds. |
| firstComment | A reply posted under the post, or under the last part of the chain, once it is live. Up to 500 characters. |
| accountId | The Threads profile to post from. Optional when the workspace has only one. |
Social media studio checks each file against these limits before it publishes. They are our configured limits, not a promise from Threads: GET /v1/media/rules returns the live table, and POST /v1/media/validate checks a file without posting it.
Post type TEXT
Text only, no media
Post type IMAGE
Post type VIDEO
Post type CAROUSEL
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": "THREADS" }
}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 Threads without hand-written HTTP calls.
Add the server to Claude, Cursor or any MCP client with your API key. OAuth works too. For Threads, 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 Threads post in one command.
so-me posts:create --platform THREADS --post-type IMAGE \
-m ./roadmap.jpg \
-c "Our Q4 roadmap in one picture. Details below." \
--thread "October: faster exports and a new calendar view." \
-s 2026-11-09T12:00:00ZAPI, CLI and MCP access is included on every paid plan: Lite, Creator, Standard, Advanced and Lifetime. See plans and limits
Yes. Put the first post in text and the rest in threadParts. Each part is published as a reply to the one before it, so the chain reads in order.
From 2 to 20, up to 8 MB each, sent as postType CAROUSEL with their fileIds.
No. You connect the Threads account once in the Social media studio dashboard through the Threads 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.