Publish text, image, multi-image and video posts to a LinkedIn profile or a Company Page you manage, on a schedule, from one REST endpoint. No LinkedIn developer app to register.
Base URL https://api.so-me.studio/v1 · Auth X-API-Key · socialMedia: LINKEDIN_PAGE | LINKEDIN
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 update.
IMAGE
One image with your text.
CAROUSEL
2 to 20 images in one multi-image post.
VIDEO
One native video.
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":"release-chart.png","mimetype":"image/png","size":734003}]}'
# → [{ "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/png" \
--upload-file ./release-chart.pngPOST /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": "LINKEDIN_PAGE",
"accountId": "<account id from GET /v1/accounts>",
"postType": "IMAGE",
"text": "We just shipped scheduled reports. Three charts show what changed.",
"fileIds": ["<fileId>"],
"scheduledAt": "2026-11-04T08:30:00Z",
"firstComment": "Release notes: https://example.com/changelog"
}'accountId is optional when the workspace has one LinkedIn account. Otherwise pass an id from GET /v1/accounts.
Files attached with fileIds are checked against the LinkedIn 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 LinkedIn.
| Field | What it does |
|---|---|
| socialMedia | LINKEDIN publishes to a personal profile, LINKEDIN_PAGE to a Company Page. |
| accountId | The profile or Page to post from, as listed by GET /v1/accounts. Needed when more than one is connected. |
| firstComment | A comment added under the post once it is live, up to 1,250 characters. Useful for a link or hashtags. |
Social media studio checks each file against these limits before it publishes. They are our configured limits, not a promise from LinkedIn: 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 CAROUSEL
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": "LINKEDIN_PAGE" }
}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 LinkedIn without hand-written HTTP calls.
Add the server to Claude, Cursor or any MCP client with your API key. OAuth works too. For LinkedIn, 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 LinkedIn post in one command.
so-me posts:create --platform LINKEDIN_PAGE -a <account-id> \
--post-type IMAGE -m ./release-chart.png \
-c "We just shipped scheduled reports." \
-s 2026-11-04T08:30:00ZAPI, CLI and MCP access is included on every paid plan: Lite, Creator, Standard, Advanced and Lifetime. See plans and limits
Yes. Connect the Page in the dashboard as one of its admins, then send socialMedia LINKEDIN_PAGE with that Page as accountId.
Yes. Send socialMedia LINKEDIN to publish on the member profile that was connected.
From 2 to 20 in a multi-image post: send postType CAROUSEL with their fileIds. Each image can be up to 5 MB.
No. You connect the LinkedIn account once in the Social media studio dashboard through the LinkedIn 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.