BulkPublish for developers
Posting, scheduling, media, analytics, the Inbox and approvals are all available programmatically, on every plan, including the free one. Schedule and publish posts across 15 social networks, upload media, manage labels and recurring schedules, and read analytics, all over a documented REST API, official SDKs, or the hosted MCP server for AI agents.
Quickstart (five minutes)
- Create a free account. No card required.
- Connect a social channel in the app.
- Generate an API key: Settings → API Keys → Create key. Keys are self-serve on every plan.
- Make your first request:
curl https://app.bulkpublish.com/api/channels \
-H "Authorization: Bearer bp_your_key_here" Create and schedule a post:
curl -X POST https://app.bulkpublish.com/api/posts \
-H "Authorization: Bearer bp_your_key_here" \
-H "Content-Type: application/json" \
-d '{"content": "Hello from the API", "channels": [{"channelId": 1}], "status": "scheduled", "scheduledAt": "2026-12-01T09:00:00Z"}' Looking for one network? Each has its own API page with a working example, its options and limits: the social media API for every network, and the same as an assistant: the MCP pages.
Reference
- API reference: every endpoint, interactive, with example requests.
- OpenAPI 3.1 spec: machine-readable, and every operation has a unique
operationIdand declares the OAuth scope it needs. - GitHub: bulkpublish-api: spec, guides, examples, and changelog.
SDKs and clients
- Node.js:
npm install bulkpublish(npm, also viabrew tap azeemkafridi/bulkpublish) - Python:
pip install bulkpublish(PyPI) - No-code: n8n, Zapier, Make, IFTTT. See all integrations.
AI agents (MCP)
The hosted MCP server at https://mcp.bulkpublish.com/mcp exposes 55 tools (compose, schedule, publish, media, analytics) over Streamable HTTP with OAuth, so you can connect it to Claude, ChatGPT, Cursor, or any MCP client. The first time it connects, a sign-in page asks for one of your API keys. The MCP server guide walks through setup for each client. Machine-readable guidance for agents lives in llms.txt.
Auth, scopes, and limits
Server-to-server calls use API keys (Bearer bp_…). Apps acting for other BulkPublish users can use OAuth 2.1 with PKCE and request least-privilege scopes (posts:read, posts:write, media:read, media:write, analytics:read, channels:read, or full). Errors are structured JSON ({"error": {"message", "code"}}). The free plan is a full test environment: same API, real publishing, no card.
Help
Questions go to support@bulkpublish.com with "API" in the subject, or the Help Center.