Connect your code and your AI assistant
Schedule posts from your own code with the REST API, let an AI assistant work in your workspace through the hosted MCP server, and share any web page with the browser extension.
Built on open standards
REST API
Your first scheduled post from code
The API runs the same rules as the app: roles, account access, approvals and plan limits.
-
Create a key
The workspace Owner creates an API key in Settings > Security.
-
Read the spec
The OpenAPI document lists every operation and field.
-
List accounts
GET /api/v1/accounts returns the accounts the key reaches.
-
Create a post
POST /api/v1/posts shares now, schedules or queues.
-
Follow it
GET /api/v1/posts lists it in its Manage Posts tab.
MCP server
Let your AI assistant use the workspace
Connect an assistant that speaks the Model Context Protocol. It signs in through OAuth, and you choose the workspace on a consent page.
Your role applies
The assistant can do what you can do, and nothing more.
Remove it any time
Settings > Security lists every connected assistant with Remove.
Or use a key
Clients that cannot sign in can send an API key in a header.
REST API
Predictable for scripts
Keys carry scopes, lists page with cursors and creates can be retried safely.
GET /api/v1/openapi.json Scoped keys
9 scopes, from reading accounts to writing posts.
Cursor paging
Every list returns data and a next cursor.
Safe retries
Send an Idempotency-Key and a repeated create creates nothing.
Rate limits
120 requests a minute per key, announced in headers.
Uploads in parts
Large media upload in 8 MB parts, like the composer.
Marked as API
Posts made through the API show where they came from.
MCP tools
15 tools for your AI assistant
The assistant sees only the tools your scopes and your role allow.
Read accounts and posts, create posts and drafts, read queues and analytics.
- UserInfo
- AccountList
- GroupList
- CreatePost
- CreateDraft
- DraftList
- ViewDraft
- AccountQueued
- DeliveredPosts
- ErrorPosts
- UnscheduledPosts
- PendingReviewPosts
- ViewPost
- QueueTimes
- AnalyticsSummary
Get started
Everything is documented
The guides walk through keys, the MCP connection and the extension step by step.
$ curl -s https://<your-app>/api/v1/me -H "Authorization: Bearer apk_..."{"workspace":{"slug":"..."},"user":{"role":"Owner"},"plan":{"name":"Ultimate"}}$ curl -s "https://<your-app>/api/v1/posts?status=queued&limit=2" -H "Authorization: Bearer apk_..."{"data":[...],"nextCursor":"..."}
Guides for REST API, MCP server and extension
View all guidesQuestions
-
The REST API is part of Ultimate. The MCP server and the browser extension work on every plan and during the trial.
-
Its packages for Chrome, Edge and Firefox are built, but the store listings are not published yet. The extension page inside SocialApp links to each store once they are.
-
No. Keys in addresses end up in logs. Send the key in the Authorization header instead, or sign in with OAuth.
Get your team posting
Create your workspace and invite your team. New features arrive in it as soon as they are ready.
14-day free trial. No card needed.