Schedule text, photos, videos, Reels and Stories to the Facebook Pages you manage, from your code or AI agent, with one API key and no Meta app of your own.
Base URL https://api.so-me.studio/v1 · Auth X-API-Key · socialMedia: FACEBOOK
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 Page post.
IMAGE
One photo.
MULTIPLE_IMAGES
2 to 10 photos in one post. CAROUSEL is accepted as well.
VIDEO
One video, up to 4 hours.
REEL
One vertical video as a Reel, up to 90 seconds.
STORY
One photo or video as a Page Story.
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":"store-tour.mp4","mimetype":"video/mp4","size":26214400}]}'
# → [{ "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 ./store-tour.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": "FACEBOOK",
"postType": "REEL",
"text": "Our new store opens Saturday. A first look inside.",
"fileIds": ["<fileId>"],
"scheduledAt": "2026-11-07T10:00:00Z",
"firstComment": "Directions and opening hours: https://example.com/store"
}'accountId is optional when the workspace has one Facebook account. Otherwise pass an id from GET /v1/accounts.
Files attached with fileIds are checked against the Facebook 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 Facebook.
| Field | What it does |
|---|---|
| accountId | The Page to post to, as listed by GET /v1/accounts. Optional when only one Page is connected. |
| firstComment | A comment posted under the post once it is live, up to 8,000 characters. On videos and Reels it waits until Facebook has finished processing. |
Social media studio checks each file against these limits before it publishes. They are our configured limits, not a promise from Facebook: 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 MULTIPLE_IMAGES
Post type VIDEO
Post type REEL
Post type STORY
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": "FACEBOOK" }
}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 Facebook without hand-written HTTP calls.
Add the server to Claude, Cursor or any MCP client with your API key. OAuth works too. For Facebook, 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 Facebook post in one command.
so-me posts:create --platform FACEBOOK --post-type REEL \
-m ./store-tour.mp4 \
-c "Our new store opens Saturday. A first look inside." \
-s 2026-11-07T10:00:00ZAPI, CLI and MCP access is included on every paid plan: Lite, Creator, Standard, Advanced and Lifetime. See plans and limits
No. The Facebook API publishes to Pages, not to personal profiles, so Social media studio posts to the Pages you manage.
Upload a vertical 9:16 video of at least 540 × 960 px and up to 90 seconds, then send postType REEL with its fileId and a scheduledAt time.
No. You connect the Facebook account once in the Social media studio dashboard through the Facebook 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.