postborne
EN
Sign in to Studio

POSTBORNE / DEVELOPERS

YOUR OWN FLOW.
AN OPEN STRUCTURE.

Manage your content from your own tools.
The Postborne API and MCP use the same publishing flow.

Explore the structure
SAME FOUNDATION. DIFFERENT ENTRY POINTS.

PREPARE ONCE.
MANAGE IT YOUR WAY.

The API and MCP work with your workspace’s records and the permissions you choose. Manage your keys and AI connections from the Connection Center.

Available actions depend on your workspace permissions and connected social accounts.
Connection Center

Open the OpenAPI contract 

curl -X POST "$POSTBORNE_API_URL/v1/posts" -H "Authorization: Bearer $POSTBORNE_API_KEY" -H "Content-Type: application/json" -H "Idempotency-Key: campaign-20261028-0001" -d '{"text":"The next idea.","destinations":["youtube"]}'
POSTBORNE API · YOUR ACCOUNT AND PERMISSIONS
API CONTRACTYOUR DATA. SCOPED AUTHORIZATION CHECKS.
GET/v1/accountsConnections and what they can actually do
POST/v1/media/uploadsLarge file upload in parts, straight to private storage
POST/v1/mediaVerified file transfer from a local tool
POST/v1/postsA draft in your workspace
POST/v1/publications/:id/scheduleSet the date, then give fresh approval
POST/v1/publications/:id/checkThe real YouTube processing result
01

Access you can control.

Choose the scope of each API key and revoke access whenever you want.

02

Same job, same record.

Web and MCP use the same draft revision, publishing approval and activity record.

03

A real path for files.

Upload large videos in parts straight to private storage and use them by file ID.