Build on Social Media Digital Marketer
A clean REST API, an MCP server for AI assistants, a CLI for scripts and CI, and webhooks for the events that matter. Wire your own tools into the same publishing engine the app runs on.
Everything you need to build
The scheduler, the publishing engine and the analytics, all reachable from your own code, your terminal or an AI assistant.
REST API
Create, schedule and queue 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 schedule, queue and report on 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.
CLI
Schedule, queue and check post status from your terminal, a script or a CI job, with the same workspace key and the same rate limits.
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, queue or publish now, one endpoint
- Track status through to publish or retry
# Schedule a post to Bluesky (beta)
curl -X POST https://api.{your-domain}/v1/posts \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"channel": "bluesky",
"caption": "Founder Q&A this Thursday",
"media": ["asset_9f2a"],
"schedule_at": "2026-09-24T19:00:00Z"
}'
# Or the same thing from the CLI
smdm posts schedule --channel bluesky --at 2026-09-24T19:00Z \
--text "Founder Q&A this Thursday" --media asset_9f2aQuestions from builders
Who can use the API?
During the beta, the API, MCP server and CLI are open to beta workspaces; plans are not priced yet. 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?
Only what you ask it to schedule, with the permissions of its token. In a workspace that requires approval, everything queued over MCP, the API or the CLI waits for a person with the right role.
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, MCP and CLI 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
The API, MCP server and CLI are open during the beta. Bring your own tools and agents.