For AI agents: a documentation index is available at /llms.txt. Every guide and example is also available as markdown by adding .md to its URL.
Introduction
The Schedulin API is a REST API for scheduling and publishing content across every major social platform from a single integration. Connect your channels once in the dashboard, then draft, schedule, and publish posts, manage media and tags, pull post analytics, and receive webhooks programmatically.
Base URL
All requests go to:
https://api.schedulin.app
Endpoints are versioned under /v0 (for example GET /v0/posts).
How it works
- JSON over HTTPS — requests and responses are JSON.
- Workspace-scoped keys — each API key can only access the workspace it was created in.
- Channels are "social accounts" — connected accounts are exposed at
/v0/social-accounts.
NOTE
The API is built for developers and AI agents alike. Every endpoint is described in the machine-readable , which you can use to generate clients or drive tool calls.
Ways to call it
- Official SDKs — TypeScript (
npm i @schedulin/sdk), Python (pip install schedulin), Go, PHP, and Ruby, generated from the OpenAPI spec. See the Quick Start. - MCP server —
https://mcp.schedulin.app/mcplets AI agents schedule posts as tool calls. See OAuth for App Clients. - CLI —
npx @schedulin/clito script the API from your terminal. See the CLI guide. - Plain HTTP — it's a standard REST API; any HTTP client works.
Next steps
- Quick Start — make your first authenticated request.
- Authentication — how API keys work.
- CLI — drive the API from your terminal.
- Your First Post — connect a channel and publish.
- Supported Platforms — which networks you can post to and what each one requires.
- API Reference — every endpoint, schema, and response.