REST endpoints, an npm-installed CLI and signed webhooks for scheduling, publishing and analytics across 20 social platforms. Built for backends, automations and AI agents.
Predictable JSON endpoints for posts, drafts, media, analytics, inbox and biolinks.
Generate an API key in Settings → API Keys and send it in the X-API-Key header. The same key works for REST, CLI and MCP.
Per-workspace, per-minute request quotas plus a monthly call cap. Exceed it and the API returns 429 Too Many Requests, no guesswork.
Subscribe to post.published, post.failed, account.disconnected and more. Signed payloads.
Install once with npm i -g @social-media-scheduler/cli for shells, CI pipelines and cron, same API key, JSON output everywhere.
Connect Claude, Cursor and other AI coding agents to your workspace via Model Context Protocol.
Sign up for a free account, then head to Settings → API Keys and generate a key. The same key works for both the REST API and the CLI.
Access, prices, and quotas depend on your current plan. See the pricing page for current plans and the API limits table for API call, rate, and webhook quotas.
Same workspace, three interfaces. The REST API is for any backend service. The CLI installs with npm i -g @social-media-scheduler/cli for shells, CI and cron. The MCP server lets AI agents (Claude, Cursor, Hermes) call your workspace as native tools.
Access, prices, and quotas depend on your current plan. See the pricing page for current plans and the API limits table for API call, rate, and webhook quotas.
Yes. Subscribe to post.published, post.failed, social.account_disconnected, subscription.plan_changed and 140+ more events via POST /v1/webhooks/subscriptions. Payloads are signed with HMAC-SHA256.
Out of the box: JavaScript/TypeScript (fetch + Node), Python (requests + httpx), curl. The OpenAPI spec is published so you can generate a client in any language.
Stop juggling tabs, draft, customize, and publish to 20 platforms from a single calendar.