Let AI manage your social media.
Or build it yourself with the API.

Connect Solnk to your AI client

Our Model Context Protocol server lets Claude, Cursor, and any MCP-compatible client connect to Solnk natively — no custom API wiring. Connect once, then publish to 9 platforms straight from your AI client.

https://mcp.solnk.com/mcp

{
  "mcpServers": {
    "solnk": {
      "command": "npx",
      "args": [
        "mcp-remote", "https://mcp.solnk.com/mcp",
        "--header", "Authorization: Bearer sk_..."
      ]
    }
  }
}

Clients with native remote-MCP support (e.g. Cursor) can add the server URL directly with an Authorization: Bearer header. Get your API key at Settings → API Keys.

How it works with AI

You talk. AI publishes.

Connect your social accounts in Solnk. Then just tell any AI what to post — it handles the API call, formatting, and delivery.

Works with

One request, nine platforms

Or let your AI write this call for you — either way it's the same endpoint.

curl -X POST https://api.solnk.com/api/v1/publishes \
  -H "Authorization: Bearer sk_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "content": "Just shipped our new feature!",
    "targets": [
      { "account_id": "acc_x_01" },
      { "account_id": "acc_linkedin_01" },
      { "account_id": "acc_threads_01" }
    ],
    "publish_mode": "immediate"
  }'

v1 reference

Every endpoint in one place

Posts, accounts, groups, approvals, and webhooks — fifteen endpoints cover the entire publishing surface. Each one carries a fine-grained scope.

What the API covers

Team-aware API

Two flavors of API keys

One token model, two intents. Pick the one that matches who is allowed to touch which accounts — the API enforces the rest.

Same sk_ prefix — the team scope is stored server-side at key creation. A team key carries its team context implicitly: no extra header, no team_id in the body.

curl https://api.solnk.com/v1/accounts \
  -H "Authorization: Bearer sk_xxx"

# Response is automatically scoped to that team's
# accounts. A request for an account in another team
# returns 403 — even if the key owner is a member of both.

Every post the API creates is stamped with its origin so you can attribute it back to a teammate or a workflow.

{
  "id": "post_01HXY…",
  "content": "Launch day!",
  "team_id": "team_01HXY…",
  "created_by": "user_01HXY…",
  "status": "scheduled"
}

Webhooks

Approval loops that close themselves

Subscribe once, get notified for every state change a post goes through. Pair it with the approval queue and your CMS stays in sync without polling.

Events

Approval events fire today. Publish/fail events ship as the worker delivery pipeline lands — subscribe now and you'll receive them as soon as they go live.

X-Solnk-Signature: sha256=<hex>

By design

What we deliberately keep out of the API

A few admin actions stay in the dashboard on purpose. It is the same line the rest of the industry draws — these are identity-sensitive moves, and we'd rather they leave a human paper trail than sit behind an automation token.

Pair these UI flows with the approval webhook above and your external system still sees every outcome — without holding the privileges to override a human decision.