Create image and video Pins on any of your boards, with a destination link, on a schedule from your code or your AI agent.
Base URL https://api.so-me.studio/v1 · Auth X-API-Key · socialMedia: PINTEREST
Send one of these values as postType. Every post needs text, and photos or videos are attached by fileId from your media library.
IMAGE
One image Pin.
VIDEO
One video Pin, up to 5 minutes.
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":"balcony-garden.jpg","mimetype":"image/jpeg","size":2097152}]}'
# → [{ "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 ./balcony-garden.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": "PINTEREST",
"postType": "IMAGE",
"text": "Small-space balcony garden: 12 plants that thrive in pots",
"fileIds": ["<fileId>"],
"scheduledAt": "2026-11-10T19:00:00Z",
"metaData": {
"boardId": "<board id>",
"link": "https://example.com/balcony-garden"
}
}'accountId is optional when the workspace has one Pinterest account. Otherwise pass an id from GET /v1/accounts.
Files attached with fileIds are checked against the Pinterest 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 Pinterest.
| Field | What it does |
|---|---|
| metaData.boardId | Required: the board the Pin is saved to. Without it the Pin fails at publish time. |
| metaData.link | The destination URL people open from the Pin. |
| text | The Pin title is the first 100 characters of text, and the full text becomes the Pin description. |
Social media studio checks each file against these limits before it publishes. They are our configured limits, not a promise from Pinterest: GET /v1/media/rules returns the live table, and POST /v1/media/validate checks a file without posting it.
Post type IMAGE
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": "PINTEREST" }
}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 Pinterest without hand-written HTTP calls.
Add the server to Claude, Cursor or any MCP client with your API key. OAuth works too. For Pinterest, 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 Pinterest post in one command.
so-me posts:create --platform PINTEREST --post-type IMAGE \
-m ./balcony-garden.jpg \
-c "Small-space balcony garden: 12 plants that thrive in pots" \
-s 2026-11-10T19:00:00Z \
--metadata '{"boardId":"<board id>","link":"https://example.com/balcony-garden"}'API, CLI and MCP access is included on every paid plan: Lite, Creator, Standard, Advanced and Lifetime. See plans and limits
Ask the MCP server: list_pinterest_boards returns the boards of a connected account, and create_pinterest_board makes a new one. The REST API has no boards route yet.
Yes. Put the URL in metaData.link, and the Pin opens it.
No. You connect the Pinterest account once in the Social media studio dashboard through the Pinterest 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.