Build on Social Media Digital Marketer
A clean REST API, an MCP server for AI assistants, and webhooks for the events that matter. Wire your own tools, integrations and agents into the same publishing engine the app runs on.
Everything you need to build
The publishing engine, the analytics and the agent, all reachable from your own code or an AI assistant.
REST API
Create and schedule posts, read analytics and manage channels over a clean JSON API. Everything the app does, your code can do.
MCP server
Connect Social Media Digital Marketer to Claude or ChatGPT over the Model Context Protocol, so an AI assistant can plan, draft and queue posts in a conversation.
Webhooks
Subscribe to publish, failure and approval events. Your systems learn the moment a post goes live or needs attention, no polling.
OAuth
Ask a customer to connect their account with a standard OAuth flow and scoped tokens. Build tools and integrations on top of their workspace.
SDKs, coming soon
Typed clients for TypeScript and Python are in the works. Until they land, the API is plain HTTP and works from any language.
Rate limits
Sensible per-workspace limits with clear headers on every response, so you can back off gracefully and never guess where you stand.
One request to schedule a post
Authenticate with your workspace API key and schedule a post to any connected channel. The response comes back with an id and a status you can track through to publish.
- JSON in, JSON out, over plain HTTPS
- Schedule, draft or publish, one endpoint
- Track status through to publish or retry
# Schedule a post to Instagram (beta)
curl -X POST https://api.{your-domain}/v1/posts \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"channel": "instagram",
"caption": "Founder Q&A this Thursday",
"media": ["asset_9f2a"],
"schedule_at": "2026-09-24T19:00:00Z"
}'Questions from builders
Who can use the API?
API and MCP access are included on the Studio plan and above. Point your workspace API key at the base URL and you are live. The API is in beta while we finalise it against real integrations.
How do I authenticate?
Server-to-server calls use a workspace API key in the Authorization header. To act on behalf of another customer, use the OAuth flow to request scoped access to their workspace.
Can an AI assistant post on its own?
No. The MCP server lets an assistant plan, draft and queue, but every draft still waits for a human approval before it publishes. Approval is a product rule, not a setting you can turn off.
What events can I subscribe to?
Webhooks fire on publish, failure and approval. You receive a signed payload with the post, the channel and the reason, so your systems stay in sync without polling.
Is there a changelog?
Yes. API and MCP changes are noted in the product changelog. Because the developer surface is in beta, we flag breaking changes ahead of time.
Start building on the beta
API and MCP access are included on Studio and above. Bring your own tools and agents.