Developers

Multi Post Social API Documentation: Posts, Channels, Analytics, Webhooks

Updated October 27, 2026 · Multi Post Social guide

Overview and base URL

All requests go to the versioned base URL below over HTTPS. Request and response bodies are JSON. Times are ISO 8601 strings in UTC. Lists are paginated with a cursor. Every response includes a request id header you can quote to support.

Base URL (planned):  https://api.multipostsocial.com/v1
Content-Type:        application/json
Pagination:          ?limit=50&cursor=<next_cursor from the previous response>

The API mirrors the product’s data model: a workspace has channels; a post belongs to one channel and shares a group id with its sibling versions created in the same composer session; ideas live on the Create board; analytics are read per channel and per post.

Authentication

Create an API key in Settings under API keys. Keys are scoped to one workspace and shown once; only the prefix is stored afterwards. Send the key in the Authorization header. Keys can be revoked at any time, and each key has a label so you can tell Zapier from your own script in the activity log.

Authorization: Bearer mps_live_7f3a...        # one key per integration
X-Workspace: ws_01h...                        # optional when a key spans several workspaces (Agency plans)

Never put a key in client-side code or a public repository. Use environment variables, and rotate a key you suspect has leaked from the same settings screen. The security guide explains how keys and sessions are protected.

Endpoints

Request and response examples

Create a post for two channels and add it to each channel’s queue:

POST /v1/posts
{
  "channel_ids": ["ch_instagram_01", "ch_linkedin_01"],
  "text": "Three small changes that made our Monday planning shorter.",
  "overrides": {
    "ch_linkedin_01": { "text": "Three changes that made our Monday planning 20 minutes shorter. Details below." }
  },
  "media_ids": ["med_9a1"],
  "first_comment": "#contentplanning #smallbusiness",
  "tags": ["Tips"],
  "action": "queue"              // "queue" | "schedule" | "now" | "draft"
}

201 Created
{
  "group_id": "grp_7k2",
  "posts": [
    { "id": "post_a1", "channel_id": "ch_instagram_01", "status": "queued", "scheduled_at": "2026-11-03T09:00:00Z" },
    { "id": "post_a2", "channel_id": "ch_linkedin_01",  "status": "queued", "scheduled_at": "2026-11-03T08:00:00Z" }
  ]
}

Read analytics for the last 30 days:

GET /v1/analytics/overview?from=2026-10-01&to=2026-10-31

200 OK
{
  "range": { "from": "2026-10-01", "to": "2026-10-31" },
  "totals": { "posts": 42, "impressions": 184320, "reach": 149100, "engagements": 6210, "clicks": 2890 },
  "engagement_rate": 3.37,
  "by_channel": [ { "channel_id": "ch_instagram_01", "impressions": 98400, "engagement_rate": 4.1 } ]
}

Errors

{
  "error": { "code": "validation_error", "message": "Text exceeds the X limit of 280 characters",
             "errors": [ { "field": "overrides.ch_x_01.text", "message": "312 of 280 characters" } ] },
  "request_id": "req_01hz..."
}

Rate limits per plan

Limits are counted per workspace across all keys. Responses include the remaining budget in headers. When you hit a limit the API returns 429 with a Retry-After header; back off and retry. The numbers below are the same as on the pricing page.

X-RateLimit-Limit-15m: 100
X-RateLimit-Remaining-15m: 97
X-RateLimit-Limit-30d: 7500
Retry-After: 120            # only on 429

Webhooks

Register an HTTPS endpoint and receive a signed POST when an event happens. Each delivery includes an event type, the object, a timestamp and a signature header computed with your webhook secret. Verify the signature before you trust a payload. Deliveries are retried with backoff for 24 hours, and the dashboard shows the last 50 deliveries per endpoint.

POST https://example.com/hooks/mps
X-MPS-Signature: t=1730000000,v1=5f1a...
{
  "id": "evt_01hz...", "type": "post.published", "created_at": "2026-11-03T09:00:04Z",
  "data": { "post": { "id": "post_a1", "channel_id": "ch_instagram_01", "network_url": "https://..." } }
}

MCP server for AI agents

The Model Context Protocol server lets an AI agent such as a desktop assistant or a chat model use your workspace through typed tools, with the same key and the same permissions as the API. A typical session: the agent reads last month’s analytics, drafts a week of posts in your tone, creates them as drafts, and you approve them in the dashboard. Publishing directly is possible only when the workspace setting Allow agents to schedule is on; otherwise the agent can only create drafts and approval requests.

{
  "mcpServers": {
    "multi-post-social": {
      "url": "https://mcp.multipostsocial.com",        // planned
      "headers": { "Authorization": "Bearer mps_live_..." }
    }
  }
}

SDKs and versioning

The API is versioned in the path. Breaking changes get a new version and the old one stays available for at least 12 months with notices in the changelog. Additive changes, such as new fields, arrive without a version bump, so parse responses leniently. Official SDKs for JavaScript and Python are planned; until then, any HTTP client works and the examples above are complete. Status of the API and each network connection is on the status page.