The Setupe API for your apps and AI agents. One request, every channel.

Post to every channel with one API call

Three steps, about five minutes.

curl "https://setupe.com/api/automation/v1/accounts" \
  -H "Authorization: Bearer $SETUPE_API_KEY"

{
  "ok": true,
  "data": [
    { "id": 12, "provider_key": "instagram",
      "display_name": "Northbeam Coffee", "username": "northbeam.coffee" },
    { "id": 15, "provider_key": "linkedin",
      "display_name": "Northbeam Coffee", "username": "" }
  ]
}

curl "https://setupe.com/api/automation/v1/me" \
  -H "Authorization: Bearer $SETUPE_API_KEY"

{
  "ok": true,
  "workspace_owner_user_id": 1,
  "team_id": 4,
  "permissions": ["posts:write", "accounts:read"]
}

Authentication and permissions

Send your key on every request as Authorization: Bearer spauto_…. The X-Automation-Key header works too. A key belongs to the workspace it was created in. Revoke it any time from the same Developer page. Call the API from a server or script, not from a web page, because the key is a secret.

Base URL: https://setupe.com/api/automation/v1. Every response is JSON with "ok": true or "ok": false and a message.

POST /posts

Creates one post per account in account_ids. The Idempotency-Key header is required: 8 to 255 characters with no spaces, such as a UUID. Reuse the same key when you retry. A repeat returns the first response with Idempotency-Replayed: true.

Post status codes: 1 draft, 2 processing, 3 scheduled, 4 published, 5 failed.

Webhooks

Add a webhook URL on the Developer page and pick the events you want. Setupe sends a JSON POST each time one happens. Each webhook has its own signing secret.

import crypto from "node:crypto";

function verify(rawBody, headers, secret) {
  const ts = headers["x-automation-timestamp"];
  const expected = "sha256=" + crypto
    .createHmac("sha256", secret)
    .update(ts + "." + rawBody)
    .digest("hex");
  const given = headers["x-automation-signature"] || "";
  return given.length === expected.length &&
    crypto.timingSafeEqual(Buffer.from(given), Buffer.from(expected));
}

{
  "event": "post.published",
  "occurred_at": "2026-11-20T09:00:04+00:00",
  "post": {
    "id": 9041, "status": 4, "status_key": "published",
    "caption": "Meet our autumn blend. Out tomorrow.",
    "account_id": 12, "provider_key": "instagram",
    "remote_post_id": "17985…", "url": "https://www.instagram.com/p/…",
    "error": null
  },
  "account": { "id": 12, "username": "northbeam.coffee", "provider_key": "instagram" }
}

Delivery: answer with any 2xx status within 20 seconds. If your server times out, returns 408 or 429, or returns a 5xx error, Setupe tries again after 30 seconds, then after 2 minutes, for 3 attempts in total. Redirects are not followed, so use the final URL.

What the API supports on each network

Accounts are connected in the Setupe dashboard through our own approved apps. There is no developer app for you to register and no review to pass on each network.

Media goes in as public links in media_urls, up to 10 per post. Use links that do not expire before the post goes out. Each network still applies its own limits on text length and file size.

MCP server for AI assistants

Setupe runs a hosted Model Context Protocol server at https://setupe.com/mcp. Add it to Claude, ChatGPT, Cursor or any MCP client, sign in to Setupe once with OAuth, and ask in plain words: "schedule this for Tuesday at 9 on Instagram and LinkedIn" or "how did last week's posts do?".

// Settings → Connectors → Add custom connector
Name: Setupe
URL:  https://setupe.com/mcp

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "setupe": { "url": "https://setupe.com/mcp" }
  }
}

claude mcp add --transport http setupe https://setupe.com/mcp

Safe by default: the assistant only sees the workspaces you approve when you sign in, and you can disconnect it any time from the Developer page in Setupe.

Built for AI agents

Connect through the MCP server, or give your agent the REST endpoints as tools. Because every post needs an Idempotency-Key, an agent that retries never posts twice. Keep the agent on drafts with a posts:write key, and let a person publish from the Setupe calendar.