Skip to main content
Postsiva is built for automation. Every feature available in the web app is accessible via REST with a workspace API key — no SDK required.

Integration options

MethodBest forAuth
REST APICustom apps, scripts, backendsX-API-Key: psk_live_…
cURL recipesQuick tests, CI, shell scriptsSame API key header
n8nVisual workflows, webhooks, cronCommunity nodes (n8n-nodes-postsiva) or HTTP Request
ZapierNo-code automationsWebhooks + Code steps
Make.comScenarios with HTTP modulesAPI key header
Unified MCPAI agents (Cursor, Claude)API key header or query param
Claude DesktopConversational MCPSame MCP URL + API key
GPT ActionsChatGPT Custom GPTBearer API key
Chrome extensionLinkedIn repost UIApp login (Starter+)
WhatsApp agentChat control on mobilePro WhatsApp link

Base URL

https://backend.postsiva.com
Local: http://localhost:8000

Authentication

All integrations use the same workspace API key:
-H "X-API-Key: psk_live_YOUR_KEY"
Alternative: Authorization: Bearer psk_live_YOUR_KEY
API keys require the Pro plan (api_keys_enabled). MCP requires Pro with mcp_enabled.
See Authentication.

Common workflows

WorkflowEndpoints
Connect accountPOST /unified/oauth/url
Upload mediaPOST /media/upload
Publish postPOST /unified/post/text | /image | /video
Schedule postAdd scheduled_time or POST /unified/scheduled-posts
Save draftdraft: true or POST /unified/drafts
List postsGET /unified/posts
List queueGET /unified/scheduled-posts, GET /unified/drafts
AnalyticsGET /unified/analytics
Reply to commentPOST /unified/comments/reply

Idempotency and errors

  • Multi-platform posts return per-platform results — partial success is normal
  • Check error field in response items (NOT_CONNECTED, validation errors)
  • HTTP status reflects request-level issues; platform errors are in the body
See Errors overview.

Rate limits

API keys may hit rate limits under heavy use. Response includes rate limit details when exceeded.

Choose your integration

n8n

Official community nodes (43) — posting, schedule, inbox, AI, watcher.

Zapier

Webhooks + Code steps pattern for no-code automations.

Make.com

HTTP modules + scenarios against the same REST API.

cURL

Copy-paste recipes for common operations.

Claude Desktop

Unified MCP inside Claude.

Chrome extension

LinkedIn side-panel repost + AI.

WhatsApp

Workspace agent over WhatsApp (Pro).

MCP

Connect Cursor and other MCP clients.

Webhooks (incoming)

Postsiva does not push outbound webhooks for post status today. Poll GET /unified/scheduled-posts or GET /unified/posts from your automation on a schedule, or use n8n/Zapier timers. Facebook and Instagram comment webhooks are handled server-side for inbox features — not user-configurable outbound hooks.