Skip to main content
Unified OAuth routes manage account connections for your workspace. OAuth platforms return an auth_url to open in a browser; Bluesky uses handle + app password (no redirect).

Base URL & auth

Supported platforms

Platform callbacks remain on existing routes (e.g. /linkedin/oauth/callback) after the user authorizes.

API key scope

Workspace API keys can be scoped to specific platforms. A key with scope linkedin_only or linkedin,instagram cannot connect or disconnect platforms outside that list — requests return 403.
See Authentication for creating scoped keys.

POST /unified/oauth/url

Start OAuth or complete Bluesky connect.

Request body

OAuth platforms response

Open each auth_url in a browser. After callback, verify with GET /unified/oauth/token.

Bluesky connect

No redirect URL — send credentials in the same POST:
Create a Bluesky app password in Settings → App passwords. Never use your main account password in API calls.

GET /unified/oauth/token

Check connection status per platform. Token values are never returned — only success: true/false.

Query parameters

Response

When platform is omitted, all token-supported platforms are checked in batch (filtered by key scope).

DELETE /unified/oauth/token

Disconnect one or more platforms. platform query param is required (repeat for multiple).
Successful disconnect sends an account-disconnected notification email to workspace owners when configured.

MCP equivalents

Connect at https://mcp.postsiva.com/mcpMCP tools.
  • Posting — requires connected accounts
  • Posts — lists content from connected networks
  • Authentication — API key scopes and Pro plan for keys/MCP